Updated 2. Software Architecture Specification (markdown)
parent
2637ccf1c7
commit
6f61fdf7eb
@ -115,9 +115,7 @@ Attention is paid to transferability to later projects, through the involvement
|
|||||||
|
|
||||||
#### 2.3.1.1 Testability<a name="S14"/>
|
#### 2.3.1.1 Testability<a name="S14"/>
|
||||||
|
|
||||||
### 2.3.2 Bug fixing <a name="S15"/>
|
This is probably the second most important point after usability, care must be taken to ensure that the code is testable. On the one hand directly in the code, but also testing the binary is important. For this purpose, various test cases are described and worked through on another page. Thereby, to keep quality high, errors that cause undesirable behavior or even fatal errors must be eliminated.
|
||||||
|
|
||||||
Another milestone to keep quality high is the elimination of errors that cause undesired behaviour or even fatal errors.
|
|
||||||
|
|
||||||
# 3. Quality Concept <a name="QC"/>
|
# 3. Quality Concept <a name="QC"/>
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user