View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Delivery RAID Log | ![]() Decision Making Trade-off Analysis | ![]() Architecture Views and Beyond | ![]() Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 30 min Setup, dann laufend | 45-120 min | 1-3 Tage | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 1-4 | 3-20 Reviewer |
Formatdifferent | Async | Workshop + async | Workshop + async | Async |
Outputdifferent | RAID Log, Status Report Source | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides | Architecture Views, Cross-view Notes, Rationale | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RiskTrackingStakeholdersGovernance | TradeoffsDecisionCriteriaOptions | DocumentationStakeholdersArchitecture | ArchitectureDecisionAsyncGovernance |



