View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Request for CommentsEvaporating CloudAssumption SurfacingATAM (Architecture Tradeoff Analysis Method)
| Criterion | ![]() Architecture Request for Comments | ![]() Systems Thinking Evaporating Cloud | ![]() Decision Making Assumption Surfacing | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 60-120 min | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-20 Reviewer | 2-8 | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments | Assumption List, Critical Assumptions, Learning Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | Theory of ConstraintsAssumptionsSystems thinking | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskTradeoffsStakeholders |



