View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Value Chain AnalysisAssumption SurfacingATAM (Architecture Tradeoff Analysis Method)SAAM (Software Architecture Analysis Method)
| Criterion |  Business Strategy Value Chain Analysis |  Decision Making Assumption Surfacing |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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. | 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. |
Complexitydifferent | High | Low | High | High |
Timedifferent | Half day | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 3-8 | 2-8 | Evaluation team, architects, and relevant stakeholders | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Value Chain Map, Lever List | 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 | 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 |
Tagsno overlap | StrategyBusiness modelDiagnosisAnalysis | AssumptionsRiskDecisionDiscovery | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureChangeAnalysisComparisonQuality |