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 for Option Framing.
Decision Making
Option Framing
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.In early decisions, alternatives are often still vague, incomplete, or blended together. Option Framing brings every possibility into a comparable form and makes visible which variant actually fits the question.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 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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
2-6 h45-120 min1-3 h1-3 h
Participantsdifferent
2-83-82-83-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsOption Frames, Assumption Notes, Comparable Shortlist, Decision InputsContext Map, Integration Patterns, Boundary NotesDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
OptionsDecision framingStrategyComparison
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignContextBoundaries
Add more methods