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 Fault Tree Analysis |  Architecture arc42 |  Operations Barrier Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
Purposedifferent | 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 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 safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. |
Complexitydifferent | High | Low | Medium | High |
Timedifferent | 2-6 h | 1-2 Tage | 2-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 3-8 | 1-4 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Architecture Document, Context View, Runtime View, Deployment View | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | RiskRoot causeSafety | ArchitectureDocumentationCommunication | Root causeSafetyIncident | Root causeSafetySystemicIncident |