View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:LASR (Lightweight Approach for Software Reviews)Fault IsolationValue Chain AnalysisSAAM (Software Architecture Analysis Method)
| Criterion | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Engineering Fault Isolation | ![]() Business Strategy Value Chain Analysis | ![]() Architecture SAAM (Software Architecture Analysis Method) |
|---|---|---|---|---|
Purposedifferent | 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. | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | 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 | High | High |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-180 min | Half day | Preparation, scenario analysis, and findings review; effort depends on scope |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 1-6 | 3-8 | Architecture experts and stakeholders for scenarios and weighting |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | 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 | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Value Chain Map, Lever List | 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 | ArchitectureQualityRiskAssessmentLean | TroubleshootingDiagnosisEngineering | StrategyBusiness modelDiagnosisAnalysis | ArchitectureChangeAnalysisComparisonQuality |



