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 Fault Tree Analysis |  Architecture arc42 |  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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 | High | Low | Low |
Timedifferent | 2-4 h | 2-6 h | 1-2 Tage | 15-30 min |
Participantsdifferent | 2-6 | 3-8 | 1-4 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures |
Tagsno overlap | Root causeSafetyIncident | RiskRoot causeSafety | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving |