Principle
Separate policy from implementation mechanism
Stable mechanisms should not hard-code volatile policy where avoidable.
Before you use it
- Use when
- When a rule change repeatedly requires low-level rewrites across the system.
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
Express business policy in one explicit layer or configuration boundary and let implementation consume it through a stable contract, subject to security and performance constraints.
An example
Order-block policy changes from ZM to another rule without rewriting the underlying persistence and integration mechanics.
Check your result
A policy change can be reviewed and deployed without unnecessary changes to unrelated mechanism code or process.
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 readingSeparate policy from implementation mechanism
Ideas that link here
These ideas link to this one. Check their conditions and limits before use.
Useful with this ideaKeep reversible experiments behind a boundary
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.