View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Impact MappingForce Field AnalysisSAAM (Software Architecture Analysis Method)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Product Strategy Impact Mapping |  Decision Making Force Field Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |
|---|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. | 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. | 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 | Low | High | High |
Timedifferent | 45-90 min | 45-90 min | Preparation, scenario analysis, and findings review; effort depends on scope | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | 3-12 | Architecture experts and stakeholders for scenarios and weighting | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | Force Field Map, Change Levers, Risk Notes | 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 | 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 | OutcomesStrategyBehaviorPlanning | ChangeDecisionStrategy | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskTradeoffsStakeholders |