From 2637ccf1c7ed4e83ef030ffe58adff3b450face6 Mon Sep 17 00:00:00 2001
From: Cyber-Luke <75857685+Cyber-Luke@users.noreply.github.com>
Date: Fri, 22 Apr 2022 12:55:56 +0200
Subject: [PATCH] Updated 2. Software Architecture Specification (markdown)

---
 2.-Software-Architecture-Specification.md | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/2.-Software-Architecture-Specification.md b/2.-Software-Architecture-Specification.md
index 68e69a4..e1c9bd7 100644
--- a/2.-Software-Architecture-Specification.md
+++ b/2.-Software-Architecture-Specification.md
@@ -75,6 +75,8 @@ In order to achieve the quality goals, different criteria are considered.
 
 ### 2.3.1 Runtime quality attributes<a name="S4"/>
 
+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)
@@ -85,23 +87,35 @@ 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.
+
 #### 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.
+
 #### 2.3.1.5 Availability<a name="S9"/>
 
+The programme and its code will be available on GitHub on a public repository. This means that anyone can access the programme at any time.
+
 #### 2.3.1.5 Interoperability<a name="S10"/>
 
+By complying with the applicable technical standards, this feature is given, with no restrictions. No proprietary or unknown file formats are used. It is possible to open created models directly in other programs, for example the AutomationML editor. 
+
 ### 2.3.2 Non-Runtime quality attributes<a name="S11"/>
 
+These cannnot be observed at execution time of the system.
+
 #### 2.3.1.1 Modifiability<a name="S12"/>
 
-#### 2.3.1.1 Portability<a name="S13"/>
+Since the programme is open source and publicly viewable, it can be extended by anyone. This is important if any use cases arise in the future.
 
-#### 2.3.1.1 Reusability<a name="S14"/>
+#### 2.3.1.1 Portability and reusability<a name="S13"/>
 
-#### 2.3.1.1 Testability<a name="S15"/>
+Attention is paid to transferability to later projects, through the involvement and formation of libraries and the like, but the application case is very specific and difficult to transfer to other or new projects. Therefore not so important.  
 
-### 2.3.2 Bug fixing <a name="S16"/>
+#### 2.3.1.1 Testability<a name="S14"/>
+
+### 2.3.2 Bug fixing <a name="S15"/>
 
 Another milestone to keep quality high is the elimination of errors that cause undesired behaviour or even fatal errors.