Was bedeutet Stable Abstractions Principle?
Das International Software Architecture Qualification Board (ISAQB) definiert den Begriff „Stable Abstractions Principle“ wie folgt:
Unter Stable Abstractions Principle versteht man „
A fundamental principle for designing the structure of software systems (also see Package Principles). It demands that the abstractness of components is proportional to their stability. The closely related SDP also explains the notion of stability in this context.
We want components that represent abstract concepts and responsibilities to require little or no modification because many conceptually more specific (concrete) components depend on them. And we want components that should or could not easily change to be at least abstract enough so we can extend them. This relates to the OCP.
The SAP can sound like a circular argument until the underlying idea shines through: Concrete things and concepts are naturally more volatile, specific, arbitrary and numerous than abstract ones. The component structure of a system simply should reflect that. General logic, the system’s physical artifacts as well as its functional and technical concepts should all be in congruence.
The SAP is closely related to the SDP. Their combination amounts to a more general and arguably more profound version of the DIP: Specific concepts naturally depend on more abstract ones because they are composed or derived from more general-purpose building blocks. And dependent concepts are naturally more specific because they are defined by more information than their dependencies (assuming there are no dependence cycles).
Category: Design-Principle
„
Wenn Sie ähnliche Fachbegriffe wie Stable Abstractions Principle nachschlagen müssen, schauen Sie doch einfach in unserm umfangreichen Glossar nach. Oder durchsuchen Sie unser Wörterbuch:
