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 Architecture Decision Record |  Decision Making Trade-off Analysis |  Architecture Request for Comments |  Decision Making Constraint Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. | 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 45-120 min | 1-3 Wochen vom Draft bis zur Entscheidung | 30-90 min |
Participantsdifferent | 1-3 | 2-8 | 3-20 Reviewer | 2-8 |
Formatdifferent | Async | Workshop + async | Async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TradeoffsDecisionCriteriaOptions | ArchitectureDecisionAsyncGovernance | ConstraintsDecisionPlanningOptions |