Updated 2. Software Architecture Specification (markdown)

Cyber-Luke 2022-04-23 20:26:43 +02:00
parent 58e7a0b7f9
commit 5397acb3b1

@ -213,7 +213,7 @@ Still the MVC pattern is a small part of the whole system design. In this case t
| **<MOD.001>** | **Graphical User Interface** |
| --- | --- |
| **System requirements covered:** | /NF10/, /NF20/, /NF30/, /NF40/, /NF50/, /NF60/, /NF70/, /NF80/, /NF90/, /NF100/, /F10/, /F20/, /F60/, /F70/|
| **System&nbsp;requirements&nbsp;covered:** | /NF10/, /NF20/, /NF30/, /NF40/, /NF50/, /NF60/, /NF70/, /NF80/, /NF90/, /NF100/, /F10/, /F20/, /F60/, /F70/ nicht fertig |
| **Services:** | The graphical user interface is taking input from the user and sending it to the controller by calling event functions. |
| **Interfaces:** | --- |
| **External Data:** | --- |
@ -224,7 +224,7 @@ Still the MVC pattern is a small part of the whole system design. In this case t
| **<MOD.002>** | **Controller** |
| --- | --- |
| <p>**System requirements<br> covered:**</p> | /NF100/, /F30/, /F40/, /F50/, /F80/ |
| **System&nbsp;requirements&nbsp;covered:** | /NF100/, /F30/, /F40/, /F50/, /F80/ nicht fertig |
| **Services:** | Logic distribution is handled by the controller. It is reacting to the events triggered by the GUI and takes care of creating the respective objects. Also the input and output functions are implemented in the controller. |
| **Interfaces:** | Interface for IODD to AutomationML, Interface for GSD to AutomationML and Interface of AMLX packages. For export/import of amlx files there is another class referenced: [SOURCE/MWData.cs](https://github.com/H4CK3R-01/TINF20C_ModellingWizard_Devices/blob/app-source-code/SOURCE/Plugin/MWData.cs) |
| **External Data:** | --- |