View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Bounded Context Canvas |  UX Research Diary Study |  Delivery RAID Log |  Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | 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 experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 30 min Setup, dann laufend | 1-3 h |
Participantsdifferent | 3-8 | 5-20 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | Domain-Driven DesignBoundariesStrategy |