Updated 2. Software Architecture Specification (markdown)

2.-Software-Architecture-Specification.md

@@ -57,13 +57,15 @@ The aim of this project is to program a standalone application for Windows based
 
 **.NET** The .NET Framework is a software development and runtime environment developed by Microsoft for Microsoft Windows.
 
+**IODD** 
+
+**GSD**
+
 # 2. System Overview <a name="S"/>
 
 ## 2.1 System Environment <a name="S1"/>
 
-The standalone application can only be accessed via Windows, as this operating system is used as the platform. The application can be installed and the graphical user interface can be used via this platform. In contrast to old programme orthe plug-in, the editor no longer needs to be used.
+The standalone application can only be accessed via Windows, as this operating system is used as the platform. The application can be installed and the graphical user interface can be used via this platform. In contrast to old programme orthe plug-in, the editor and the "IODD" and the "GSD" converter no longer needs to be used.
-
-Among others the IODD and GSD converter are used as neighbouring systems.
 
 ## 2.2 Software Environment <a name="S2"/>
 
@@ -79,7 +81,7 @@ These can be observed at execution time of the system.
 
 #### 2.3.1.1 Usability<a name="S5"/>
 
-Usability is the most important aspect of the project besides the standalone application. To this end, a graphical user interface was created that allows the user to use it as easily as possible. Intuitive operation is very important, but an appealing design is also necessary to create the best possible user experience. This is the only way the application can successfully simplify work processes. (More information in the usability concept)
+Usability is the most important aspect of the project besides the standalone application. To this end, a graphical user interface was created that allows the user to use it as easily as possible. Intuitive operation is very important, but an appealing design is also necessary to create the best possible user experience. This is the only way the application can successfully simplify work processes (More information in the [Usability Concept](#QC1)).
 
 #### 2.3.1.2 Functionality<a name="S6"/>
 
@@ -87,11 +89,11 @@ As the targets have been set relatively precisely, attention should be paid to t
 
 #### 2.3.1.3 Performance<a name="S7"/>
 
-The problem with programmes that have been developed many times and then by different teams is that they often have poor code quality and therefore a high RAM and memory load. On technically older systems, this can lead to problems such as crashes or slow feedback. You can find more information about this in the section "Code Quality".
+The problem with programmes that have been developed many times and then by different teams is that they often have poor code quality and therefore a high RAM and memory load. On technically older systems, this can lead to problems such as crashes or slow feedback. This is also a problem of the plugin, there are single files with several thousand lines of code. So we should at least try not to make this worse. If we have enough time, we should adapt the code in general. You can find more information about this in the section [Code Quality](#QC2).
 
 #### 2.3.1.4 Security<a name="S8"/>
 
-It must be ensured that it is recognisable where and from whom the programme originated. It will not be possible to access the Internet with the programme, so confidentiality is automatic. But it should be downloaded from an official source.
+It must be ensured that it is recognisable where and from whom the programme originated. It will not be possible to access the Internet with the programme, so confidentiality is automatic. But it should be downloaded from an official source, the releases can be found [here](https://github.com/H4CK3R-01/TINF20C_ModellingWizard_Devices/tags).
 
 #### 2.3.1.5 Availability<a name="S9"/>