Integration strength describes how much one software component knows about or depends on another. More information creates stronger coupling, increases cascading-change risk, and makes modifications less safe. section 12.1
Assess integration strength by asking what component A can learn about component B from A’s code:
- Does A know only B’s public interface, or also its database persistence format, private methods, persisted state, or shared code? section 12.1
- Treat intrusive coupling as the strongest form: changes in B can make A break because A may know potentially everything about B. section 12.1
Intrusive coupling in practice
Reflection-based access to private methods, direct access to persisted state, and shared code such as a god class expose internal details and make changes riskier. section 12.1
