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 FrameworkSAAM (Software Architecture Analysis Method)LASR (Lightweight Approach for Software Reviews)Value Chain Analysis
| Criterion |  Business Strategy VRIO Framework |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Business Strategy Value Chain Analysis |
|---|---|---|---|---|
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. | 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. | 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. | 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. |
Complexitydifferent | Medium | High | Medium | High |
Timedifferent | 90-180 min | Preparation, scenario analysis, and findings review; effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | Half day |
Participantsdifferent | 3-6 | Architecture experts and stakeholders for scenarios and weighting | 1 or a small team; particularly suitable for 3–4 people | 3-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | VRIO Table, Strategic Actions | 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 | 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 | Value Chain Map, Lever List |
Tagsno overlap | StrategyDiagnosisBusiness modelCapability | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskAssessmentLean | StrategyBusiness modelDiagnosisAnalysis |