http://kb.linux-vs.org/api.php?action=feedcontributions&feedformat=atom&user=CalvilloHousley893 2026-04-07T20:12:36Z User contributions MediaWiki 1.26.2 http://kb.linux-vs.org/wiki?title=User:CalvilloHousley893&diff=41261 2012-06-26T11:03:24Z

<p>CalvilloHousley893: New page: Engineering Modeling - An Iterative Approach Making the structure of a model be the just like the dwelling from the engineering component modeled turns 2 problems into one. This speeds up...</p> <hr /> <div>Engineering Modeling - An Iterative Approach<br /> <br /> Making the structure of a model be 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 also 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 begin, in co-operation with life-cycle management, marketing accounts etc. To get full take advantage of all of this staff who are 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 from 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.<br /> <br /> Integration of knowledge representation UML/DOORS is progress towards this. Also a interface is needed that makes it easier for engineers to model using this type of combined UML/Doors solution<br /> <br /> [http://brooklynturner07.dmusic.net/journal/1018514 model engineering]<br /> <br /> 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. A lot of object-oriented programming was developed before graphical user interfaces became practical and customary. So objects/classes are often represented mainly by text with visualization/representation being added as an afterthought. This is not useful for engineers who are accustomed 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 because of its use), and re-use. This may lead to errors because of re-use of objects that aren't 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 understanding of how to use them.<br /> <br /> The above mentioned steps would improve the link and co-operation between engineers and modelers/models.</div>

CalvilloHousley893 http://kb.linux-vs.org/wiki?title=CalvilloHousley893&diff=41260 2012-06-26T11:03:10Z

<p>CalvilloHousley893: New page: Engineering Modeling - An Iterative Approach Making the structure of a model be the just like the dwelling from the engineering component modeled turns 2 problems into one. This speeds up...</p> <hr /> <div>Engineering Modeling - An Iterative Approach<br /> <br /> Making the structure of a model be 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 also 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 begin, in co-operation with life-cycle management, marketing accounts etc. To get full take advantage of all of this staff who are 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 from 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.<br /> <br /> Integration of knowledge representation UML/DOORS is progress towards this. Also a interface is needed that makes it easier for engineers to model using this type of combined UML/Doors solution<br /> <br /> [http://brooklynturner07.dmusic.net/journal/1018514 model engineering]<br /> <br /> 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. A lot of object-oriented programming was developed before graphical user interfaces became practical and customary. So objects/classes are often represented mainly by text with visualization/representation being added as an afterthought. This is not useful for engineers who are accustomed 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 because of its use), and re-use. This may lead to errors because of re-use of objects that aren't 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 understanding of how to use them.<br /> <br /> The above mentioned steps would improve the link and co-operation between engineers and modelers/models.</div>

CalvilloHousley893