Principle
Decompose around likely change, not the org chart
Useful boundaries localize likely change.
Before you use it
- Use when
- When a system is split into components that mirror teams but every business change still touches many components.
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
Identify design decisions likely to vary independently and place them behind boundaries that minimize coordinated change. Team ownership can follow later.
An example
A pricing rule and its data are isolated from transport mechanics so policy changes do not require transport rewrites.
Check your result
Common changes touch fewer modules without creating hidden duplication.
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 readingDecompose around likely change, not the org chart
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaRecheck the bottleneck after improvement
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.