Материал из База данных ДЮО "Остров Сокровищ"
|
|
| Строка 1: |
Строка 1: |
| − | Engineering Modeling - An Iterative Approach
| |
| | | | |
| − | Making the dwelling of a model function as 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 as part of this process, so early stage design can begin, in co-operation with life-cycle management, marketing accounts etc. To obtain full take advantage of all of this staff who're thing about this design process, manufacturing, management, and life-cycle management need to be in a position to access the models. The long run aim would be 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 because 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 needed which makes it easier for engineers to model using this type of combined UML/Doors solution
| |
| − |
| |
| − | [http://jakeburgess001.pnn.com/25942-the-front-page model engineering]
| |
| − |
| |
| − | Despite object-oriented programming techniques being heavily relying on the approach used 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 common. So objects/classes in many cases are represented mainly by text with visualization/representation being added being an afterthought. This is not useful for engineers who are accustomed to objects being physical things, or at least diagrams. An additional problem continues to be 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 aren't fully understood. So the classes/objects need to be visualized, whether or not the user are not committed to alter their contents, therefore the user of objects has sufficient knowledge of how to use them.
| |
| − |
| |
| − | The above steps would enhance the link and co-operation between engineers and modelers/models.
| |
Текущая версия на 12:21, 7 сентября 2014
История файла
Нажмите на дату/время, чтобы просмотреть, как тогда выглядел файл.
| Дата/время | Миниатюра | Размеры | Участник | Примечание |
|---|
| текущий | 12:21, 7 сентября 2014 |  | 799 × 533 (192 КБ) | Mannin (обсуждение | вклад) | |
- Вы не можете перезаписать этот файл.
Использование файла
Следующая 1 страница ссылается на данный файл:
Файл содержит дополнительные данные, обычно добавляемые цифровыми камерами или сканерами. Если файл после создания редактировался, то некоторые параметры могут не соответствовать текущему изображению.
