View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Decision Framing WorkshopATAM (Architecture Tradeoff Analysis Method)SAAM (Software Architecture Analysis Method)Trade-off Analysis
| Criterion | ![]() Decision Making Decision Framing Workshop | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Architecture SAAM (Software Architecture Analysis Method) | ![]() Decision Making Trade-off Analysis |
|---|---|---|---|---|
Purposedifferent | When a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins. | 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. | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. |
Complexitydifferent | Medium | High | High | Medium |
Timedifferent | 60-120 min | Several meetings plus preparation and analysis; total effort depends on scope | Preparation, scenario analysis, and findings review; effort depends on scope | 45-120 min |
Participantsdifferent | 4-10 | Evaluation team, architects, and relevant stakeholders | Architecture experts and stakeholders for scenarios and weighting | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Decision Frame, Decision Question, Criteria List, Evidence Plan | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides |
Tagsno overlap | Decision framingAlignmentCriteriaOptions | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureChangeAnalysisComparisonQuality | TradeoffsDecisionCriteriaOptions |



