Was bedeutet Package Principles?
Das International Software Architecture Qualification Board (ISAQB) definiert den Begriff „Package Principles“ wie folgt:
Unter Package Principles versteht man „
Fundamental principles for designing the structure of software systems (Martin-2003):
<ul
Reuse/Release Equivalence Principle (REP)</li
Common Reuse Principle (CRP)</li
Common Closure Principle (CCP)</li
Acyclic Dependencies Principle (ADP)</li
Stable Dependencies Principle (SDP)</li
Stable Abstractions Principle (SAP)</li
</ul<brRobert C. Martin, who coined the “SOLID” acronym, also introduced the Package Principles and frequently reiterated both in conjunction. Whereas the SOLID Principles target the level of classes, the Package Principles target the level of larger components that contain multiple classes and might get deployed independently.
Package- and SOLID Principles share the explicit goal of keeping software maintainable and avoiding the symptoms of degraded design: rigidity, fragility, immobility, and viscosity.
While Martin expressed the Package Principles in terms of large-scale components, they apply at other scales as well. Their core are universal principles like low coupling, high cohesion, single responsibility, hierarchical (acyclic) decomposition, and the insight that meaningful dependencies go from specific/unstable concepts to more abstract/stable ones (which echoes the DIP).
Category: Design-Principle
„
Wenn Sie ähnliche Fachbegriffe wie Package Principles nachschlagen müssen, schauen Sie doch einfach in unserm umfangreichen Glossar nach. Oder durchsuchen Sie unser Wörterbuch:
