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 ATAM (Architecture Tradeoff Analysis Method) |  Architecture Request for Comments |  Architecture Views and Beyond |
|---|---|---|---|
Purposedifferent | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | 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. |
Complexitydifferent | High | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung | 1-3 Tage |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-20 Reviewer | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Views, Cross-view Notes, Rationale |
Tags1 shared | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDecisionAsyncGovernance | DocumentationStakeholdersArchitecture |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
