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 AnalysisRisk StormingSAAM (Software Architecture Analysis Method)ATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Business Strategy Value Chain Analysis |  Architecture Risk Storming |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture ATAM (Architecture Tradeoff 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. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | High | Low | High | High |
Timedifferent | Half day | 60-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 | 4-12 | Architecture experts and stakeholders for scenarios and weighting | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Value Chain Map, Lever List | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 | StrategyBusiness modelDiagnosisAnalysis | RiskArchitectureWorkshopValidation | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskTradeoffsStakeholders |