View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Barrier AnalysisSAAM (Software Architecture Analysis Method)Fault Tree AnalysisLASR (Lightweight Approach for Software Reviews)
| Criterion |  Operations Barrier Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations Fault Tree Analysis |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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 | Medium | High | High | Medium |
Timedifferent | 2-4 h | Preparation, scenario analysis, and findings review; effort depends on scope | 2-6 h | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | 2-6 | Architecture experts and stakeholders for scenarios and weighting | 3-8 | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | 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 | 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 | Root causeSafetyIncident | ArchitectureChangeAnalysisComparisonQuality | RiskRoot causeSafety | ArchitectureQualityRiskAssessmentLean |