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 MapSAAM (Software Architecture Analysis Method)VRIO FrameworkBusiness Model Stress Test
| Criterion |  Domain Modeling Context Map |  Architecture SAAM (Software Architecture 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. | 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. | 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 | Preparation, scenario analysis, and findings review; effort depends on scope | 90-180 min | Half day |
Participantsdifferent | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 3-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | 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 | VRIO Table, Strategic Actions | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ArchitectureChangeAnalysisComparisonQuality | StrategyDiagnosisBusiness modelCapability | StrategyBusiness modelRiskDiagnosis |