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)A3 Problem Solving5 WhysLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations A3 Problem Solving |  Operations 5 Whys |  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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 45-90 min | 15-30 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-5 | 2-6 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | A3 Report, Action Plan, Root Cause Analysis | Root cause notes, Countermeasures | 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 | LeanProblem solvingCoachingOperations | Root causeIncidentLeanProblem solving | ArchitectureQualityRiskAssessmentLean |