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 Context Map |  Architecture Request for Comments |  Decision Making Delphi Method |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-3 h | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 Wochen | 15-45 min |
Participantsdifferent | 2-8 | 3-20 Reviewer | 6-30 Experten | 1-3 |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Expert Forecast, Consensus Range, Assumption Notes | ADR File, Decision Log, Rationale |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureDecisionAsyncGovernance | ForecastingExpertsDecisionStrategy | ArchitectureRationaleDocumentationGovernance |