Protocol
Test whether modularity actually localizes change
Modularity should be observable in change history.
Before you use it
- Use when
- When an architecture is called modular but there is no evidence that changes stay local.
Keep this limit in mind
- Modularity trades coordination inside a boundary for coordination across interfaces. Do not split systems simply to make diagrams or org charts look cleaner.
An idea to explore.
Try this idea.
Inspect the example, try the idea in your situation, then check your next move.
Why it matters
Sample representative recent changes and count modules, teams and interfaces touched. Compare with the intended boundary rationale and redesign where change repeatedly leaks.
Steps
- Choose several representative changes.
- Count components and teams touched.
- Identify why each cross-boundary change was required.
- Update boundaries or contracts if leakage is systematic.
An example
Five policy changes all require edits in four services, showing that the supposed policy boundary is not localizing volatility.
Check your result
Change history supports or falsifies the modularity claim.
Save and practise this idea
My learning
Read. Recall. Repeat.
Save this idea and return to it on any device.
Keep exploring
Connected ideas
You are readingTest whether modularity actually localizes change
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaCount coordination edges before adding a component
Evidence and sources
Parnas showed that modularization outcomes depend on decomposition criteria and argued for boundaries that hide changeable design decisions to improve flexibility and comprehensibility.
This is foundational software-design reasoning; organizational adaptations require separate validation.
On the Criteria To Be Used in Decomposing Systems into Modules · Abstract and design comparison
Edition and review
Version 0.1.0
No review details are supplied for this edition.