View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Architecture arc42 |  Operations Fault Tree Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most 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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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. |
Complexitydifferent | Medium | Low | High | Medium |
Timedifferent | 1-3 h | 1-2 Tage | 2-6 h | 2-4 h |
Participantsdifferent | 3-8 | 1-4 | 3-8 | 2-6 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Architecture Document, Context View, Runtime View, Deployment View | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | FailureResilienceRisk | ArchitectureDocumentationCommunication | RiskRoot causeSafety | Root causeSafetyIncident |