DHBW/TINF20C_ModellingWizard_Devices
1
0
Fork 0
Code Issues 4 Pull Requests Packages Projects Releases 7 Wiki Activity

Updated 2. Software Architecture Specification (markdown)

Cyber-Luke 2022-04-24 15:46:03 +02:00
parent b92042f6f3
commit 1ce3361073
1 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
2.-Software-Architecture-Specification.md

@ -38,10 +38,19 @@
| Version | Date | Author | Comment | | Version | Date | Author | Comment |
| ------------- |-------------|-------------|-------------| | ------------- |-------------|-------------|-------------|
| V0.1 | 26.10.2020 | Lukas Ernst / Florian Kellermann | created | | V0.1 | 04.11.2021 | Lukas Ernst / Florian Kellermann | created |
| V0.2 | 05.11.2021 | Florian Kellermann | edited | | V0.2 | 05.11.2021 | Lukas Ernst | Add introduction and glossary details |
| V0.3 | 22.04.2022 | Lukas Ernst | edited | | V0.4 | 07.11.2021 | Lukas Ernst | Add runtime and non-runtime quality goals |
| V0.5 | 10.11.2021 | Lukas Ernst | Update quality concept and technical concept |
| V0.6 | 12.11.2021 | Lukas Ernst | Update usability concept |
| V0.7 | 16.11.2021 | Lukas Ernst | Add architectural concept |
| V0.8 | 26.03.2022 | Lukas Ernst | spicify architectural concept |
| V0.9 | 10.04.2022 | Lukas Ernst | Add system design |
| V1.0 | 13.04.2022 | Lukas Ernst | Update system design |
| V1.1 | 14.04.2022 | Lukas Ernst | Update subsystem specification |
| V1.2 | 20.04.2022 | Lukas Ernst | Correct descriptions and add links |
| V1.3 | 24.04.2022 | Lukas Ernst | Latest changes |
| V1.4 | 06.05.2022 | ? | Checked for correctness |
*** ***
# 1. Introduction <a name="I"/> # 1. Introduction <a name="I"/>
@ -172,7 +181,7 @@ The application was designed and developed according to a Model-View-Control (MV
Almost all the logic is contained in the controller, which thus forms the centre of the entire system architecture and contains the functionalities. There is basically only one layer that is accessible to the user, the GUI. Almost all the logic is contained in the controller, which thus forms the centre of the entire system architecture and contains the functionalities. There is basically only one layer that is accessible to the user, the GUI.
The controller is the main control unit. It is responsible for communicating with the user interface and the external systems that are added for conversions. This interface is the heart of the entire application and is responsible for the functionalities, but also for the integration of additional functions such as saving or loading AMLX packages from the AutomationML Engine. Thus, the concept builds on that of the plug-in, making it easier to adapt functions and ideas. The change is that it will be a standalone application. This is ensured by integrating the AutomationML engine and the plug-in into a new programme via an import. The plugin is then started in its own view, so that the old code of the plugin is retained. The controller is the main control unit from the plug-in. It is responsible for communicating with the user interface and the external systems that are added for conversions. This interface is the heart of the entire application and is responsible for the functionalities, but also for the integration of additional functions such as saving or loading AMLX packages from the AutomationML Engine. Thus, the concept builds on that of the plug-in, making it easier to adapt functions and ideas. The change is that it will be a standalone application. This is ensured by integrating the AutomationML engine and the plug-in into a new programme via an import. The plugin is then started in its own view, so that the old code of the plugin is retained.
<p align="center"> <p align="center">
<img src="https://user-images.githubusercontent.com/76038781/140762427-8fb4c097-2c53-4c80-a07f-ed3f3d8c90d3.png" /><br> <img src="https://user-images.githubusercontent.com/76038781/140762427-8fb4c097-2c53-4c80-a07f-ed3f3d8c90d3.png" /><br>