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)Barrier AnalysisFault Tree AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Operations Barrier Analysis |  Operations Fault Tree Analysis |  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 risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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 | High | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 2-4 h | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 2-6 | 3-8 | 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 | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | 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 | Root causeSafetyIncident | RiskRoot causeSafety | ArchitectureQualityRiskAssessmentLean |