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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Paper scorecard with four perspectives, connected objective cards and columns for measures, targets and initiatives.
Business Strategy
Balanced Scorecard
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 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.Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures.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
MediumMediumHighMedium
Timedifferent
2-6 h1-3 hHalber Tag bis mehrere Wochen1-3 h
Participantsdifferent
2-82-84-123-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Event Model, UI Flow, Commands, Read ModelsContext Map, Integration Patterns, Boundary NotesBalanced Scorecard, Strategic Measures, Initiative MapDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesStrategy
StrategyMetricsExecution
Domain-Driven DesignContextBoundaries
Add more methods