View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Decision Making Radar |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Request for Comments |
|---|---|---|---|
Purposedifferent | When capabilities, maturity levels, or market positions need to be compared across several dimensions, overview is easily lost. Radar brings different characteristics into a shared picture and shows patterns faster than tables do. | 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. |
Complexitydifferent | Medium | High | Medium |
Timedifferent | 1-2 h | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 2-10 | Evaluation team, architects, and relevant stakeholders | 3-20 Reviewer |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Radar Map, Capability Scores, Action Areas | 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 |
Tagsno overlap | AssessmentPortfolioCapability | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDecisionAsyncGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
