User:LeithBurcham811
Engineering Modeling - An Iterative Approach
Making the structure of a model function as the just like 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 included in this process, so early stage design can start, in co-operation with life-cycle management, marketing accounts etc. To get full take advantage of this all 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 long run aim is 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 from the engineering product and software model are displayed/visualized.
Integration of knowledge 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 used by engineers for Bill of Materials/Product Data Structure modeling this link is becoming difficult. A lot of object-oriented programming was created before graphical user interfaces became practical and customary. So objects/classes are often represented mainly by text with visualization/representation being added being an afterthought. This isn't useful for engineers who're 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 for its use), and re-use. This may lead to errors because of re-use of objects that aren't fully understood. So the classes/objects have to be visualized, whether or not the user are not committed to alter their contents, so the user of objects has sufficient understanding of how to use them.
The above mentioned steps would enhance the link and co-operation between engineers and modelers/models.
