View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Operations Root Cause Analysis |  Operations MORT Analysis |  Operations Barrier Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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 | Low | Medium | High | Medium |
Timedifferent | 1-2 Tage | 1-4 h | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 1-4 | 3-8 | 2-6 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Barrier Inventory, Failure Analysis per Barrier, Action Backlog |
Tagsno overlap | ArchitectureDocumentationCommunication | Root causeProblem solvingQualityIncident | Root causeSafetySystemicIncident | Root causeSafetyIncident |