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 |  Decision Making Pre-Mortem |
|---|---|---|---|
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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. |
Complexitydifferent | High | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 Wochen vom Draft bis zur Entscheidung | 20–45 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-20 Reviewer | Small cross-functional group |
Formatdifferent | Workshop + async | Async | Workshop |
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 | Risk list, Mitigation plan, Assumption log |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureDecisionAsyncGovernance | RiskDecisionFailurePlanning |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
