View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)RAID LogAssumption SurfacingRequest for Comments
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Delivery RAID Log |  Decision Making Assumption Surfacing |  Architecture Request for Comments |
|---|---|---|---|---|
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. | 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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 | High | Low | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30 min Setup, dann laufend | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-3 maintaining, briefing for everyone | 2-8 | 3-20 Reviewer |
Formatdifferent | Workshop + async | Async | Workshop + async | 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 | RAID Log, Status Report Source | Assumption List, Critical Assumptions, Learning Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | RiskTrackingStakeholdersGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureDecisionAsyncGovernance |