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
Paper illustration of a calibrated five-by-five risk matrix with response cards.
Decision Making
Risk Matrix
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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.When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List.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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
2-6 h30-60 min1-3 h1-3 h
Participantsdifferent
2-83-103-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsRisk Matrix, Top Risk ListContext Canvas, Glossary, Integration NotesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
RiskDecisionPrioritizationAssessment
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignContextBoundaries
Add more methods