Benutzer:KassiaArchibald915
Aus Salespoint
Engineering Modeling - An Iterative Approach
Making the dwelling of a model function as the same as the structure of the engineering component modeled turns 2 problems into one. This accelerates 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 included in this process, so early stage design can begin, in co-operation with life-cycle management, marketing accounts etc. To obtain full benefit from all of this staff who are thing about this design process, manufacturing, management, and life-cycle management have to be in a position to access the models. The longer term aim would be to enable direct modeling/prototyping of this by customers of the modeling tool e.g. engineers/end-user programmers. Such a system documents itself as the structure from the engineering product and software model are displayed/visualized.
Integration of knowledge representation UML/DOORS is progress towards this. Additionally a user interface is needed that makes it easier for engineers to model using this type of combined UML/Doors solution
Despite object-oriented programming techniques being heavily relying on the approach used by engineers for Bill of Materials/Product Data Structure modeling this link has become difficult. A lot of object-oriented programming was created before graphical user interfaces became practical and common. So objects/classes are often represented largely by text with visualization/representation being added as an afterthought. This is not helpful for engineers who are used to objects being physical things, or at least diagrams. A further 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 can lead to errors because of re-use of objects that are not fully understood. Therefore the classes/objects have to be visualized, whether or not the user are not committed to change their contents, so the user of objects has sufficient understanding of cooking techniques.
The above steps would improve the link and co-operation between engineers and modelers/models.
