View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Request for Comments | ![]() Domain Modeling Bounded Context Canvas | ![]() Decision Making Delphi Method | ![]() Domain Modeling Context Map |
|---|---|---|---|---|
Purposedifferent | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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 | High | Medium |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 h | 1-4 Wochen | 1-3 h |
Participantsdifferent | 3-20 Reviewer | 3-8 | 6-30 Experten | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Canvas, Glossary, Integration Notes | Expert Forecast, Consensus Range, Assumption Notes | Context Map, Integration Patterns, Boundary Notes |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Domain-Driven DesignBoundariesModeling | ForecastingExpertsDecisionStrategy | Domain-Driven DesignBoundariesStrategy |



