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 Architecture Decision Record |  Operations MORT Analysis |  Operations Barrier Analysis |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. |
Complexitydifferent | Low | High | Medium | Low |
Timedifferent | 15-45 min | Mehrere Tage bis Wochen | 2-4 h | 1-2 Tage |
Participantsdifferent | 1-3 | 2-6 | 2-6 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Barrier Inventory, Failure Analysis per Barrier, Action Backlog | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeSafetySystemicIncident | Root causeSafetyIncident | ArchitectureDocumentationCommunication |