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 Domain Context Map |  Delivery RAID Log |  Domain Modeling Context Map |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 1-3 h | 30 min Setup, dann laufend | 1-3 h | Half day |
Participantsdifferent | 3-10 | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | RAID Log, Status Report Source | Context Map, Integration Patterns, Boundary Notes | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | Domain-Driven DesignContextBoundaries | RiskTrackingStakeholdersGovernance | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelRiskDiagnosis |