RobyKahn678: 新しいページ: 'Engineering Modeling - An Iterative Approach Making the dwelling of a model function as the same as the dwelling of the engineering component modeled turns 2 problems into one...'

RobyKahn678 — Tue, 26 Jun 2012 10:55:29 GMT

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

新規ページ

Engineering Modeling - An Iterative Approach

Making the dwelling of a model function as the same as the dwelling of the engineering component modeled turns 2 problems into one. This speeds up co-operation in prototyping of both the software model and also the component. Both rapid prototyping and rapid application design/development involve iterative fast development with prototypes communicated. Requirements emerge gradually included in this method, so initial phase design can begin, in co-operation with life-cycle management, marketing accounts etc. To obtain full take advantage of this all staff who are thing about this design process, manufacturing, management, and life-cycle management need to be able to access the models. The longer term aim is to enable direct modeling/prototyping of this 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 information representation UML/DOORS is progress towards this. Additionally a interface is needed that makes it easier for engineers to model using such a combined UML/Doors solution

[http://olivershain958.posterous.com/model-trains-toys-models-or-miniature-pieces 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 has become difficult. Much of object-oriented programming was developed 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 isn't helpful for engineers who are 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 due to 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 change their contents, so the user of objects has sufficient knowledge of cooking techniques.

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

RobyKahn678 - 変更履歴

RobyKahn678: 新しいページ: 'Engineering Modeling - An Iterative Approach Making the dwelling of a model function as the same as the dwelling of the engineering component modeled turns 2 problems into one...'