View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Barrier Analysis |  Operations Root Cause Tree Analysis |  Architecture SAAM (Software Architecture Analysis Method) |  Operations 5 Whys |
|---|---|---|---|---|
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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 2-4 h | 1-3 h | Preparation, scenario analysis, and findings review; effort depends on scope | 15-30 min |
Participantsdifferent | 2-6 | 2-8 | Architecture experts and stakeholders for scenarios and weighting | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Cause Tree, Evidence Notes, Countermeasures | 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 | Root cause notes, Countermeasures |
Tagsno overlap | Root causeSafetyIncident | Root causeTreeIncidentQuality | ArchitectureChangeAnalysisComparisonQuality | Root causeIncidentLeanProblem solving |