View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Context MapATAM (Architecture Tradeoff Analysis Method)VRIO FrameworkBusiness Model Stress Test
| Criterion |  Domain Modeling Context Map |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Business Strategy VRIO Framework |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | 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. | The VRIO Framework rates resources and capabilities on whether they are Valuable, Rare, Inimitable, and Organized. It compares strengths, risks, market logic, and courses of action. The result is captured as a VRIO table and strategic actions. | 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 | Medium | High | Medium | High |
Timedifferent | 1-3 h | Several meetings plus preparation and analysis; total effort depends on scope | 90-180 min | Half day |
Participantsdifferent | 2-8 | Evaluation team, architects, and relevant stakeholders | 3-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | 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 | VRIO Table, Strategic Actions | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureQualityRiskTradeoffsStakeholders | StrategyDiagnosisBusiness modelCapability | StrategyBusiness modelRiskDiagnosis |