View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Value Chain AnalysisBusiness Model Stress TestSAAM (Software Architecture Analysis Method)LASR (Lightweight Approach for Software Reviews)
| Criterion |  Business Strategy Value Chain Analysis |  Business Strategy Business Model Stress Test |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | High | High | High | Medium |
Timedifferent | Half day | Half day | Preparation, scenario analysis, and findings review; effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 3-8 | 3-8 | Architecture experts and stakeholders for scenarios and weighting | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Value Chain Map, Lever List | Stress Test Report, Action Plan per Scenario | 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 |
Tagsno overlap | StrategyBusiness modelDiagnosisAnalysis | StrategyBusiness modelRiskDiagnosis | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskAssessmentLean |