SOLID

1. Single Responsibility Principle

1.1. There should never be more than one reason for a class to change

1.2. NEU: "A module should be responsible to one, and only one, actor"

1.3. Durch die Anforderungen eines Akteurs definierte Funktionalitäten und Datenstrukturen

2. Interface Segregation Principle

2.1. Clients shall be not confused with details which they do not need

3. Dependency Inversion Principle

3.1. High-level classes must not depend on low-level classes, but both on interfaces

3.2. Interfaces must not depend on details, but details on interfaces

3.3. Schalter/Lampe Besipiel

4. Open Closed Principle

4.1. A class is open for enhancements but closed against modifications

5. Liskov Substitution Principle

5.1. A subtype behaves same as its base type