View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Knowledge Modeling Event Modeling |  Domain Modeling Context Map |  Business Strategy Value Chain Analysis |
|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 2-6 h | 1-3 h | Half day |
Participantsdifferent | 2-8 | 2-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Event Model, UI Flow, Commands, Read Models | Context Map, Integration Patterns, Boundary Notes | Value Chain Map, Lever List |
Tagsno overlap | EventsBlueprintDomain-Driven DesignBehavior | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
