View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:GAP AnalysisLASR (Lightweight Approach for Software Reviews)VRIO FrameworkSAAM (Software Architecture Analysis Method)
| Criterion | ![]() Business Strategy GAP Analysis | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Business Strategy VRIO Framework | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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. | 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. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 90-180 min | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 3-6 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Gap Matrix, Action Plan, Risk Notes | 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 | 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 |
Tagsno overlap | StrategyAnalysisPlanning | ArchitectureQualityRiskAssessmentLean | StrategyDiagnosisBusiness modelCapability | ArchitectureChangeAnalysisComparisonQuality |



