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 |  Architecture Software Architecture Canvas |  Operations Root Cause Analysis |  Operations MORT Analysis |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. |
Complexitydifferent | Medium | Low | Medium | High |
Timedifferent | 2-4 h | 1-2 h | 1-4 h | Mehrere Tage bis Wochen |
Participantsdifferent | 2-6 | 3-10 | 3-8 | 2-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Architecture Canvas, Goals, Constraints, Quality Attributes | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations |
Tagsno overlap | Root causeSafetyIncident | CanvasArchitectureAlignmentWorkshop | Root causeProblem solvingQualityIncident | Root causeSafetySystemicIncident |