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 AnalysisSAAM (Software Architecture Analysis Method)Context MapATAM (Architecture Tradeoff Analysis Method)
| Criterion |  Business Strategy Value Chain Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Domain Modeling Context Map |  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. | 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. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | High | Medium | High |
Timedifferent | Half day | Preparation, scenario analysis, and findings review; effort depends on scope | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope |
Participantsdifferent | 3-8 | Architecture experts and stakeholders for scenarios and weighting | 2-8 | Evaluation team, architects, and relevant stakeholders |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Value Chain Map, Lever List | 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 | Context Map, Integration Patterns, Boundary Notes | 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 | ArchitectureChangeAnalysisComparisonQuality | Domain-Driven DesignBoundariesStrategy | ArchitectureQualityRiskTradeoffsStakeholders |