View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)Fault IsolationHypothesis-Driven TroubleshootingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Engineering Fault Isolation |  Engineering Hypothesis-Driven Troubleshooting |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 | Medium | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-180 min | 30-240 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1-6 | 1-6 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | 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 | ArchitectureQualityRiskTradeoffsStakeholders | TroubleshootingDiagnosisEngineering | TroubleshootingProblem solvingDiagnosis | ArchitectureQualityRiskAssessmentLean |