Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improve listing of specific metrics #450

Merged
merged 1 commit into from
Jun 11, 2024
Merged

Improve listing of specific metrics #450

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 12 additions & 7 deletions docs/05-evaluation/LZ-05-02.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,23 +9,26 @@ Softwarearchitekt:innen
wie z.{nbsp}B.:
** Analyse der Ergebnisse von Akzeptanztests (R1)
** quantitative Messung von Laufzeitverhalten (R1)
** qualitative Auswertung durch Interviews, Umfragen, Pen-Tests etc. (R1)
** qualitative Auswertung durch Interviews, Umfragen, Penetrationstests etc. (R1)
** Szenarien (R1)
** Architektur-Metriken (R1)
** Architektur-Metriken für Kopplung wie der Grad eingehender und
ausgehender Abhängigkeiten (R1)
** Kosten-Nutzen-Analyse (R3)
** Architecture Trade-Off Analysis Method <<bass>> (R3)
* kennen Informationsquellen für Qualitätsanalyse:
** Anforderungsdokumentation (R1)
** Architekturdokumentation (R1)
** Architektur- und Entwurfsmodelle (R1)
** Quelltext (R1)
** Quelltext-bezogene Metriken wie Lines-of-Code, (zyklomatische)
Komplexität, ein- und ausgehende Abhängigkeiten (R1)
** Quelltext-bezogene Metriken wie z.B: Lines-of-Code, (zyklomatische)
Komplexität (R1)
** Testfälle und ihre Testresultate (R1)
** Fehler und ihre Position im Quelltext, besonders Fehlercluster (R1)
** andere Dokumentation des Systems, wie z.{nbsp}B. Betriebs- und
Testdokumentation (R1)
** Laufzeit-Logs und Metriken (R1)
** Revisionshistorie, wie z.{nbsp}B. wie Änderungsrate pro Komponente
(R3)

// end::DE[]

Expand All @@ -39,9 +42,10 @@ Software architects
might be available for a particular software system, such as
** analysis of the results of acceptance testing (R1)
** quantitative measurement of run-time behaviour (R1)
** qualitative evaluation via interviews, surveys, pen tests etc. (R1)
** qualitative evaluation via interviews, surveys, penetration tests etc. (R1)
** scenarios (R1)
** architecture metrics (R1)
** architecture metrics for coupling such as the degree of
inbound and outbound dependencies (R1)
** cost-benefit analysis (R3)
** Architecture Trade-Off Analysis Method <<bass>> (R3)

Expand All @@ -51,11 +55,12 @@ Software architects
** architecture and design models (R1)
** source code (R1)
** source-code-related metrics such as lines of code, (cyclomatic)
complexity, inbound and outbound dependencies (R1)
complexity (R1)
** test cases and test results (R1)
** errors and their locations in the source code, especially error clusters (R1)
** other documentation of the system, such as operational or test (R1)
documentation (R1)
** run-time event logs and metrics (R1)
** revision history, such as the rate of change per component (R3)

// end::EN[]
Loading