View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingATAM (Architecture Tradeoff Analysis Method)Value Chain AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Business Strategy Value Chain Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | 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 | Medium | High | High | Medium |
Timedifferent | 30-240 min | Several meetings plus preparation and analysis; total effort depends on scope | Half day | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 1-6 | Evaluation team, architects, and relevant stakeholders | 3-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Value Chain Map, Lever List | 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 | TroubleshootingProblem solvingDiagnosis | ArchitectureQualityRiskTradeoffsStakeholders | StrategyBusiness modelDiagnosisAnalysis | ArchitectureQualityRiskAssessmentLean |