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 | ![]() Decision Making Delphi Method | ![]() Architecture Architecture Decision Record | ![]() 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 knowledge is distributed and direct dominance should be avoided, groups quickly fall under the sway of their opinion leaders. The Delphi Method gathers assessments iteratively and gradually brings expert judgments closer together. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 | High | Low | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 15-45 min | 1-3 h |
Participantsdifferent | 3-8 | 6-30 Experten | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Context Canvas, Glossary, Integration Notes | Expert Forecast, Consensus Range, Assumption Notes | ADR File, Decision Log, Rationale | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | Domain-Driven DesignBoundariesModeling | ForecastingExpertsDecisionStrategy | ArchitectureRationaleDocumentationGovernance | Domain-Driven DesignBoundariesStrategy |



