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 | ![]() Domain Modeling Bounded Context Canvas | ![]() Delivery RAID Log | ![]() Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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. | 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. | 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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-3 h | 30 min Setup, dann laufend | 60-90 min |
Participantsdifferent | 3-10 | 3-8 | 1-3 maintaining, briefing for everyone | 3-6 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop |
Outputdifferent | Domain Context Map, Boundary Notes, Ownership Map | Context Canvas, Glossary, Integration Notes | RAID Log, Status Report Source | Salience Diagram, Strategy per Class |
Tagsno overlap | Domain-Driven DesignContextBoundaries | Domain-Driven DesignBoundariesModeling | RiskTrackingStakeholdersGovernance | StakeholdersFacilitationAlignmentGovernance |



