Principle

Make dependencies directional where possible

Mutual dependency amplifies coordination.

About 1 min read

Before you use it

Use when
  • When two components or teams repeatedly block each other because each requires internal knowledge of the other.

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

Choose a stable abstraction or ownership direction so one side depends on a contract rather than both sides depending on internals. Keep truly reciprocal work explicit.

An example

A reporting layer depends on a published canonical model; the core model no longer depends on report-specific transformations.

Check your result

A routine change on one side no longer automatically creates a reverse change request.

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 readingMake dependencies directional where possible

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