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 C4 Model |  Operations MORT Analysis |  Operations Barrier 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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 | High | Low | High | Medium |
Timedifferent | 2-6 h | 1-4 h | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 3-8 | 1-5 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Context Diagram, Container Diagram, Component Diagram | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | RiskRoot causeSafety | ArchitectureCommunicationVisualization | Root causeSafetySystemicIncident | Root causeSafetyIncident |