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.

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

#578-add-DRY-to-LG-03-04 #598

Merged
merged 2 commits into from
Oct 13, 2024
Merged
Changes from 1 commit
Commits
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
20 changes: 11 additions & 9 deletions docs/03-design/LG-03-04.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -24,14 +24,14 @@ Softwarearchitekt:innen sind in der Lage:

**Modularisierung** (R1)

* Geheimnisprinzip ({glossary_url}information-hiding[Information Hiding]) und {glossary_url}encapsulation[Kapselung] (R1)
* Trennung von Verantwortlichkeiten ({glossary_url}separation-of-concern[Separation of Concerns] - SoC) (R1)
* Lose, aber funktionell ausreichende Kopplung (R1) von Bausteinen, siehe <<LG-03-06>>
* Hohe {glossary_url}cohesion[Kohäsion] (R1)
* {glossary_url}open-close-principle[Offen/geschlossen-Prinzip] (R1)
* {glossary_url}dependency-inversion[Dependency-Inversion-Prinzip] (R1) - Umkehrung von Abhängigkeiten durch Schnittstellen oder ähnlichen Abstraktionen
* Geheimnisprinzip ({glossary_url}information-hiding[Information Hiding]) und {glossary_url}encapsulation[Kapselung]
* Trennung von Verantwortlichkeiten ({glossary_url}separation-of-concern[Separation of Concerns] - SoC)
* Lose, aber funktionell ausreichende Kopplung von Bausteinen, siehe <<LG-03-06>>
* Hohe {glossary_url}cohesion[Kohäsion]
* {glossary_url}open-close-principle[Offen/geschlossen-Prinzip]
* {glossary_url}dependency-inversion[Dependency-Inversion-Prinzip] - Umkehrung von Abhängigkeiten durch Schnittstellen oder ähnlichen Abstraktionen

**Konzeptionelle Integrität** (R2)
**Konzeptionelle Integrität** (R2-R3)

* bedeutet Einheitlichkeit (Homogenität, Konsistenz) von Lösungen für ähnliche Probleme zu erreichen (R2)
* als ein Mittel, um das Prinzip der geringsten Überraschung zu erreichen (principle of least surprise) (R3)
Expand All @@ -40,6 +40,7 @@ Softwarearchitekt:innen sind in der Lage:
**Reduktion von Komplexität** (R3)

* als Motiv der Prinzipien KISS, YAGNI und CUPID <<north-cupid>>
* DRY (Don't Repeat Yourself) als eine Möglichkeit, Wiederholungen zu vermeiden

**Erwarte Fehler** (R2-R3)

Expand All @@ -50,7 +51,7 @@ Softwarearchitekt:innen sind in der Lage:
// tag::EN[]

[[LG-03-04]]
==== LG 03-04 [previously LG 2-06]: Explain and Use Design Principles (R1-R3)
==== LG 03-04 [previously LG 2-06]: Explain and Use Design Principles (R2)

Software architects are able to explain what design principles are.
They can outline their general objectives and applications with regard to software architecture. (R2)
Expand Down Expand Up @@ -78,7 +79,7 @@ Software architects are able to:
* {glossary_url}open-close-principle[Open/closed principle] (R1)
* {glossary_url}dependency-inversion[Dependency inversion principle] (R1) by means of interfaces or similar abstractions

**Conceptual integrity** (R2)
**Conceptual integrity** (R2-R3)

* meaning uniformity (homogeneity, consistency) of solutions for similar problems (R2)
* as a means to achieve the principle of least surprise (R3)
Expand All @@ -87,6 +88,7 @@ Software architects are able to:
**Complexity reduction** (R3)

* as the driving factor behind KISS, YAGNI, and CUPID <<north-cupid>>
* DRY (Don't Repeat Yourself) as one option to avoid repetitions

**Expect errors** (R2-R3)

Expand Down