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 Fault Tree Analysis |  Operations MORT 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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | 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. | 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 | High | Low |
Timedifferent | 15-45 min | 2-6 h | Mehrere Tage bis Wochen | 1-2 Tage |
Participantsdifferent | 1-3 | 3-8 | 2-6 | 1-4 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskRoot causeSafety | Root causeSafetySystemicIncident | ArchitectureDocumentationCommunication |