PedroColeman200
Z WikiSennik
Engineering Modeling - An Iterative Approach
Making the structure of the model be the same as the structure of the engineering component modeled turns 2 problems into one. This speeds up co-operation in prototyping of both the software model and the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated. Requirements emerge gradually included in this process, so initial phase design can start, in co-operation with life-cycle management, marketing accounts etc. To get full benefit from all of this staff who're thing about this design process, manufacturing, management, and life-cycle management need to be able to access the models. The long run aim is to enable direct modeling/prototyping of this 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 information representation UML/DOORS is progress towards this. Also a user interface is needed that makes it easier for engineers to model using such a combined UML/Doors solution
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 developed before graphical user interfaces became practical and customary. So objects/classes are often represented largely by text with visualization/representation being added being an afterthought. This isn't helpful for engineers who are accustomed to objects being physical things, or at least diagrams. An additional problem continues to be an over-emphasis on encapsulation (hiding an objects' details, while creating an interface because of its use), and re-use. This may lead to errors due to re-use of objects that aren't fully understood. So the classes/objects need to be visualized, even if the user are not committed to alter their contents, so the user of objects has sufficient knowledge of cooking techniques.
The above mentioned steps would improve the link and co-operation between engineers and modelers/models.
