View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:VRIO FrameworkLASR (Lightweight Approach for Software Reviews)SAAM (Software Architecture Analysis Method)Business Model Stress Test
| Criterion |  Business Strategy VRIO Framework |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture SAAM (Software Architecture Analysis Method) |  Business Strategy Business Model Stress Test |
|---|---|---|---|---|
Purposedifferent | 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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | 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. | 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 | Medium | High | High |
Timedifferent | 90-180 min | 3–4 h for initial assessment; preparation and deeper analysis additional | Preparation, scenario analysis, and findings review; effort depends on scope | Half day |
Participantsdifferent | 3-6 | 1 or a small team; particularly suitable for 3–4 people | Architecture experts and stakeholders for scenarios and weighting | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | VRIO Table, Strategic Actions | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | 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 | Stress Test Report, Action Plan per Scenario |
Tagsno overlap | StrategyDiagnosisBusiness modelCapability | ArchitectureQualityRiskAssessmentLean | ArchitectureChangeAnalysisComparisonQuality | StrategyBusiness modelRiskDiagnosis |