Coupling is the degree to which two components depend on each other. A component might be a function, class, module, or application. With tight coupling, a change to one is likely to affect the other. Loose coupling limits that impact by reducing the assumptions components make about each other. section 4.9
A change that spreads
If one class directly modifies another class’s internal data, it relies on that data keeping the same structure. Changing the second class can then force changes to the first. Household plumbing offers the same intuition: flushing a toilet that makes the shower run cold reveals a stronger dependency than a brief pressure drop that leaves the temperature stable. section 4.9
When assessing coupling, ask what a dependency costs:
- Maintenance: Will changing one component require changes elsewhere? section 4.9
- Understanding and debugging: Do interconnected components make behavior harder to reason about? section 4.9
- Testing: Can a component be tested in isolation, or do changes require updates to other components’ tests? section 4.9
Calling two components “coupled” is only a starting point. Name the dependency and the change that would expose it. Control coupling concerns one component controlling another’s behavior; temporal coupling concerns components needing to be active at the same time. This makes coupling a useful structural question alongside cohesion, rather than a label for every interaction. section 4.10.1 section 4.7





















