Was bedeutet Common Reuse Principle?
Das International Software Architecture Qualification Board (ISAQB) definiert den Begriff „Common Reuse Principle“ wie folgt:
Unter Common Reuse Principle versteht man „
A fundamental principle for designing the structure of software systems (also see Package Principles). The subcomponents (classes) of a component should be exactly the ones that are being (re)used together. Or the other way around: Components that are being (re)used together should be packaged into a larger component. This also implies that subcomponents that are not frequently used in conjunction with the other subcomponents should not be in the respective component.
This perspective helps in deciding what belongs into a component and what doesn’t. It aims at a system decomposition of loosely coupled and highly cohesive components.
This obviously echoes the Single Responsibility Principle. It also echoes the Interface Segregation Principle, as it ensures that clients aren’t forced to depend on concepts they don’t care about.
Category: Design-Principle
„
Wenn Sie ähnliche Fachbegriffe wie Common Reuse Principle nachschlagen müssen, schauen Sie doch einfach in unserm umfangreichen Glossar nach. Oder durchsuchen Sie unser Wörterbuch:
