Protocol

Test whether modularity actually localizes change

Modularity should be observable in change history.

About 1 min read

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.

Keep reading

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

  1. Choose several representative changes.
  2. Count components and teams touched.
  3. Identify why each cross-boundary change was required.
  4. 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.

Use email
Keep exploring

Connected ideas

You are readingTest whether modularity actually localizes change

Evidence and sources
Supports

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

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details