Was bedeutet Common Closure Principle?
Das International Software Architecture Qualification Board (ISAQB) definiert den Begriff „Common Closure Principle“ wie folgt:
Unter Common Closure Principle versteht man „
A fundamental principle for designing the structure of software systems (also see Package Principles). It directly and explicitly restates the Single Responsibility Principle for larger components.
The subcomponents of a component should ideally have the exact same reasons to change. A change request that effects one of them should effect all of them, but it should not effect anything else outside their enclosing component.
Thereby, each expected change request would effect a minimal number of components. Or put another way: Each component would be closed to a maximum number of expected change requests. The term expected here signifies a few important implications:
<ol class="numeric"
The inherent concepts/responsibilities of a system run deeper than a surface-level description of its behaviour. </li
The deeper concepts/responsibilities of a system are not entirely objective but can be modeled in different ways.</li
Determining the concepts/responsibilities of a system is not just passive describing but also active strategizing.</li
</ol<brThis principle leads to highly cohesive components. It also implies loosely coupled components because related concepts that do change together do get bundled up in the same component. When each single concept is expressed by a single component, there are no unnecessary couplings between components.
Category: Design-Principle
„
Wenn Sie ähnliche Fachbegriffe wie Common Closure Principle nachschlagen müssen, schauen Sie doch einfach in unserm umfangreichen Glossar nach. Oder durchsuchen Sie unser Wörterbuch:
