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
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
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 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 problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.
Complexitydifferent
MediumMediumLowHigh
Timedifferent
1-3 h1-3 h30-60 min2-6 h
Participantsdifferent
3-82-82-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Context Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary NotesFishbone Diagram, Cause Categories, Investigation BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
Root causeQualityOperations
RiskQualityOperationsRoot cause
Add more methods