FreddyWhittington991

Aus DCPedia
Wechseln zu: Navigation, Suche

Engineering Modeling - An Iterative Approach

Making the structure of a model be the same as the dwelling from the engineering component modeled turns 2 problems into one. This speeds up co-operation in prototyping of both software model and the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated. Requirements emerge gradually as part of this method, so initial phase design can begin, in co-operation with life-cycle management, marketing accounts etc. To obtain full take advantage of this all staff who're part of this design process, manufacturing, management, and life-cycle management need to be able to access the models. The longer term aim would be to enable direct modeling/prototyping of the by customers from the modeling tool e.g. engineers/end-user programmers. This type of system documents itself because the structure of the engineering product and software model are displayed/visualized.

Integration of knowledge representation UML/DOORS is progress towards this. Additionally a interface is needed which makes it easier for engineers to model using this type of combined UML/Doors solution

model engineering

Despite object-oriented programming techniques being heavily influenced by the approach utilized by engineers for Bill of Materials/Product Data Structure modeling this link has become difficult. Much of object-oriented programming was created before graphical user interfaces became practical and customary. So objects/classes in many cases are represented mainly by text with visualization/representation being added being an afterthought. This is not useful for engineers who are accustomed to objects being physical things, or at least diagrams. An additional problem has been an over-emphasis on encapsulation (hiding an objects' details, while creating an interface for its use), and re-use. This can lead to errors due to re-use of objects that aren't fully understood. Therefore the classes/objects need to be visualized, even if the user are not committed to alter their contents, therefore the user of objects has sufficient knowledge of cooking techniques.

The above steps would improve the link and co-operation between engineers and modelers/models.