SusiPersaud821
Aus Salespoint
Engineering Modeling - An Iterative Approach
Making the dwelling of a model be the just like the structure from the engineering component modeled turns 2 problems into one. This accelerates 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 as part of this method, so initial phase design can start, in co-operation with life-cycle management, marketing accounts etc. To get full benefit from this all staff who are thing about this design process, manufacturing, management, and life-cycle management have to be able to access the models. The long run aim would be to enable direct modeling/prototyping of the by customers of the modeling tool e.g. engineers/end-user programmers. Such a system documents itself as the structure of the engineering product and software model are displayed/visualized.
Integration of information representation UML/DOORS is progress towards this. Additionally a user interface is needed which makes it easier for engineers to model using such a combined UML/Doors solution
Despite object-oriented programming techniques being heavily relying on the approach utilized by engineers for Bill of Materials/Product Data Structure modeling this link is becoming 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 is not helpful for engineers who're 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 because of its use), and re-use. This may lead to errors because of re-use of objects that are not fully understood. Therefore the classes/objects need to be visualized, even if the user does not intend to alter their contents, therefore the user of objects has sufficient knowledge of how to use them.
The above steps would improve the link and co-operation between engineers and modelers/models.
