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 Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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
Purposedifferent
Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-6 h30-90 min1-3 h1-3 h
Participantsdifferent
2-81-62-83-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsDecision Tree, Option Map, Assumption ListContext Map, Integration Patterns, Boundary NotesContext Canvas, Glossary, Integration Notes
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
DecisionTreeOptions
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignBoundariesModeling
Add more methods