Common Reuse Principle (CRP)

Clean Architecture 達人に学ぶソフトウェアの構造と設計

Amazon.co.jp で購入する

Do not force components’ users to depend on things they do not actually use.

• A principle for deciding which classes or modules should be grouped into one component.
• Classes/modules that are frequently used together should be grouped in the same component.
• Classes grouped in one component should ideally be inseparable.
• It is more important to say what should not be in the same component.
• Do not place classes that are not tightly coupled in one component.
• CRP is a generalization of the Interface Segregation Principle (ISP).
• Do not depend on components that include unused classes.

Do not depend on unnecessary things.