Software design means beneficially relating elements: identifying elements, understanding their relationships, and considering the benefits those relationships provide. section 4.10.1
Design becomes more useful when relationships are described precisely. Calling two services “coupled” is incomplete unless the relevant changes and dependencies are identified. section 4.10.1
Useful relationship distinctions include:
- Control coupling, where one component controls another component’s behavior. section 4.10.1
- Temporal coupling, where components need to be active at the same time. section 4.10.1





