View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Assumption SurfacingATAM (Architecture Tradeoff Analysis Method)Software Architecture Canvas
| Criterion |  Decision Making Assumption Surfacing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | 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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Low | High | Low |
Timedifferent | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | 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 | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskTradeoffsStakeholders | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
