GriffithsBriceno444

Aus Salespoint

Wechseln zu: Navigation, Suche

Engineering Modeling - An Iterative Approach

Making the dwelling of a model be the just like 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 initial phase design can start, in co-operation with life-cycle management, marketing accounts etc. To get full take advantage of all of this 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 would be to enable direct modeling/prototyping of the 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 information representation UML/DOORS is progress towards this. Also a user interface is needed 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. A lot 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 useful for engineers who're used to objects being physical things, or at best diagrams. A further problem has been an over-emphasis on encapsulation (hiding an objects' details, while creating an interface for its use), and re-use. This can lead to errors due to re-use of objects that aren't fully understood. So the classes/objects need to be visualized, whether or not the user does not intend to alter 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.

Persönliche Werkzeuge