Система автоматизованого проектування CAD/CAE додатків
Вантажиться...
Файли
Дата
2018
Автори
Білий, Д.І.
Скрипник, Т.К.
Bilyi, D.I.
Skrypnyk, T.K.
Назва журналу
Номер ISSN
Назва тому
Видавець
Хмельницький національний університет
Анотація
У роботі було проведено дослідження розробки програмних продуктів для CAD/CAE систем. На основі
існуючого архітектурного шаблону Model-View-Operator (MVO) було розроблено новий архітектурний шаблон
Model-Creator-ViewOperator (MCVO), що дозволяє, не змінюючи архітектуру системи, масштабувати її, вносити
зміни та доповнення до елементів системи.
Computer Aided Design systems have become an integral part of the machine-building enterprise. Therefore, the creation and upgrading of existing CAD/CAE systems is an actual task that requires constant attention of software developers. The process of improving computer aided design systems constantly continues, so during the construction phase, it is particularly important to select the CAD/CAE architecture of the system, which would allow it to scale, to make changes and additions to the elements of the system without changing the architecture. The architectural patterns are used as one of the most popular approach in creating software. The most well-known architectural pattern is MVC (model-view-controller), which is used when writing server applications. When it comes to create CAD/CAE system the most common pattern is MVO (model-view-operator). The 3D graphical system HOOPS (HOOPS/3dGS) was built based on the MVO architectural pattern based on that it becomes possible to analyze the main components of the pattern and its features. HOOPS/MVO has a model-view-operator architecture that encapsulates various data structures and concepts of HOOPS/3dGS. HOOPS/MVO makes the key capabilities of HOOPS/3dGS more accessible, offering a range of common application-level logic, facilitating efficient development and rapid prototyping of full-featured, high-performance CAD/CAM/CAE applications. The Model-View-Operator (MVO) architecture decouples graphical information from its presentation and manipulation. The model represents the data while the view corresponds to the presentation of this information. An operator can be a set of actions involving querying, creation, editing and manipulation of data. The architecture is implementing via the following three main classes: HBaseModel (model), HBaseView (view) and HBaseOperator (operator). In MVO, the HBaseModel class encapsulates the models found in the Include Library. When application logic needs to build a scene, it would first create a new instance under a Driver segment, which corresponds to an instance of the driver. The MVO class HBaseView stores an information for a given driver instance and managing data such as lights, overlay drawing, selection sets, and camera positioning. The HBaseOperator class and its derived classes designed for rotate the camera, select objects or delete various items after the 3D scene is displayed. When building an application using the MVO pattern, a single instance of the HDB class must be created and initialized during application's initialization phase. MVO supports multiple models as well as multiple views. In the HDB class, 3D graphics information is stored. To load information into the database, you can use HBaseModel. This class includes support for loading a variety of file formats. Once the information is in the database, you can continue to use HBaseModel to manage your 3D objects. When you are ready to save your object information, HBaseModel also includes support for exporting to a variety of formats. The HBaseView class manages the presentation of your models. Although an HBaseModel object can have multiple HBaseView instances, every HBaseView is associated with exactly one HBaseModel instance. In the database, HBaseView encapsulates an instance of a driver segment. The driver instance defines a connection with help of OpenGL or DX9. When HBaseView is initialized, it creates a default segment structure under the driver instance segment, which is used to manage interaction with HBaseModel. The HBaseOperator is the abstract base class that defines the interface for handling user input and operating on the model or view. The methods defined in this class provide the basis for mapping user input to interaction logic. In this context, an object derives from HBaseOperator and then implements methods to handle events such as mouse movements or key presses.
Computer Aided Design systems have become an integral part of the machine-building enterprise. Therefore, the creation and upgrading of existing CAD/CAE systems is an actual task that requires constant attention of software developers. The process of improving computer aided design systems constantly continues, so during the construction phase, it is particularly important to select the CAD/CAE architecture of the system, which would allow it to scale, to make changes and additions to the elements of the system without changing the architecture. The architectural patterns are used as one of the most popular approach in creating software. The most well-known architectural pattern is MVC (model-view-controller), which is used when writing server applications. When it comes to create CAD/CAE system the most common pattern is MVO (model-view-operator). The 3D graphical system HOOPS (HOOPS/3dGS) was built based on the MVO architectural pattern based on that it becomes possible to analyze the main components of the pattern and its features. HOOPS/MVO has a model-view-operator architecture that encapsulates various data structures and concepts of HOOPS/3dGS. HOOPS/MVO makes the key capabilities of HOOPS/3dGS more accessible, offering a range of common application-level logic, facilitating efficient development and rapid prototyping of full-featured, high-performance CAD/CAM/CAE applications. The Model-View-Operator (MVO) architecture decouples graphical information from its presentation and manipulation. The model represents the data while the view corresponds to the presentation of this information. An operator can be a set of actions involving querying, creation, editing and manipulation of data. The architecture is implementing via the following three main classes: HBaseModel (model), HBaseView (view) and HBaseOperator (operator). In MVO, the HBaseModel class encapsulates the models found in the Include Library. When application logic needs to build a scene, it would first create a new instance under a Driver segment, which corresponds to an instance of the driver. The MVO class HBaseView stores an information for a given driver instance and managing data such as lights, overlay drawing, selection sets, and camera positioning. The HBaseOperator class and its derived classes designed for rotate the camera, select objects or delete various items after the 3D scene is displayed. When building an application using the MVO pattern, a single instance of the HDB class must be created and initialized during application's initialization phase. MVO supports multiple models as well as multiple views. In the HDB class, 3D graphics information is stored. To load information into the database, you can use HBaseModel. This class includes support for loading a variety of file formats. Once the information is in the database, you can continue to use HBaseModel to manage your 3D objects. When you are ready to save your object information, HBaseModel also includes support for exporting to a variety of formats. The HBaseView class manages the presentation of your models. Although an HBaseModel object can have multiple HBaseView instances, every HBaseView is associated with exactly one HBaseModel instance. In the database, HBaseView encapsulates an instance of a driver segment. The driver instance defines a connection with help of OpenGL or DX9. When HBaseView is initialized, it creates a default segment structure under the driver instance segment, which is used to manage interaction with HBaseModel. The HBaseOperator is the abstract base class that defines the interface for handling user input and operating on the model or view. The methods defined in this class provide the basis for mapping user input to interaction logic. In this context, an object derives from HBaseOperator and then implements methods to handle events such as mouse movements or key presses.
Опис
Ключові слова
система автоматизованого проектування, архітектурний шаблон, MVO, MCVO, computer-aided design, architectural pattern
Бібліографічний опис
Білий, Д.І. Система автоматизованого проектування CAD/CAE додатків [Текст] / Д. І. Білий, Т. К. Скрипник // Вісник Хмельницького національного університету. Технічні науки. – 2018. – № 6, т. 2. – С. 141-145