LorileeGarza371

מתוך The Phnomenologic Cage
קפיצה אל: ניווט, חיפוש

Engineering Modeling - An Iterative Approach

Making the dwelling of a model function as the just like the structure of 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 early stage design can begin, in co-operation with life-cycle management, marketing accounts etc. To get full benefit from this all staff who're part of this design process, manufacturing, management, and life-cycle management have to be able to access the models. The longer term 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 as the structure of the engineering product and software model are displayed/visualized.

Integration of knowledge representation UML/DOORS is progress towards this. Also a user interface is required 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 is becoming difficult. Much of object-oriented programming was created before graphical user interfaces became practical and customary. So objects/classes are often represented largely by text with visualization/representation being added as an afterthought. This is not helpful for engineers who're used 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 can lead to errors because of re-use of objects that aren't fully understood. Therefore the classes/objects have to be visualized, even if the user does not intend to alter their contents, so the user of objects has sufficient understanding of cooking techniques.

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

כלים אישיים
גרסאות שפה
מרחבי שם
פעולות
ניווט
תיבת כלים