OllerDenny647: 新しいページ: 'Engineering Modeling - An Iterative Approach Making the structure of the model function as the same as the structure from the engineering component modeled turns 2 problems in...'

OllerDenny647 — Tue, 26 Jun 2012 11:03:42 GMT

新しいページ: 'Engineering Modeling - An Iterative Approach Making the structure of the model function as the same as the structure from the engineering component modeled turns 2 problems in...'

新規ページ

Engineering Modeling - An Iterative Approach

Making the structure of the model function as the same as 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 process, so early stage design can start, in co-operation with life-cycle management, marketing accounts etc. To obtain full take advantage of this all staff who're 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 of the modeling tool e.g. engineers/end-user programmers. This type of 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 interface is required which makes it easier for engineers to model using such a combined UML/Doors solution

[http://www.disqo.org/organisation/model-trains-toys-models-or-miniature-pieces-art model engineering]

Despite object-oriented programming techniques being heavily influenced by the approach used by engineers for Bill of Materials/Product Data Structure modeling this link has become difficult. Much of object-oriented programming was created before graphical user interfaces became practical and customary. So objects/classes in many cases are represented mainly by text with visualization/representation being added as 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 can lead to errors because of re-use of objects that are not fully understood. So the classes/objects have to be visualized, even if the user are not committed to change their contents, therefore the user of objects has sufficient understanding of cooking techniques.

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

利用者:OllerDenny647 - 変更履歴

OllerDenny647: 新しいページ: 'Engineering Modeling - An Iterative Approach Making the structure of the model function as the same as the structure from the engineering component modeled turns 2 problems in...'