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 AnalysisATAM (Architecture Tradeoff Analysis Method)Context MapBusiness Model Stress Test
| Criterion |  Business Strategy Value Chain Analysis |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Domain Modeling Context Map |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
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. | 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. |
Complexitydifferent | High | High | Medium | High |
Timedifferent | Half day | Several meetings plus preparation and analysis; total effort depends on scope | 1-3 h | Half day |
Participantsdifferent | 3-8 | Evaluation team, architects, and relevant stakeholders | 2-8 | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Value Chain Map, Lever List | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Context Map, Integration Patterns, Boundary Notes | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | StrategyBusiness modelDiagnosisAnalysis | ArchitectureQualityRiskTradeoffsStakeholders | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelRiskDiagnosis |