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 arc42 |  Architecture Architecture Decision Record |  Decision Making Force Field Analysis |  Architecture Request for Comments |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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 | Low | Low | Medium |
Timedifferent | 1-2 Tage | 15-45 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 1-4 | 1-3 | 3-12 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | ADR File, Decision Log, Rationale | Force Field Map, Change Levers, Risk Notes | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureDocumentationCommunication | ArchitectureRationaleDocumentationGovernance | ChangeDecisionStrategy | ArchitectureDecisionAsyncGovernance |