methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Purposedifferent
When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 h1-4 h2-4 h
Participantsdifferent
2-83-83-82-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesContext Canvas, Glossary, Integration NotesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanBarrier Inventory, Failure Analysis per Barrier, Action Backlog
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignBoundariesModeling
Root causeProblem solvingQualityIncident
Root causeSafetyIncident
Add more methods