View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Failure Scenario Analysis |  Architecture arc42 |  Operations Fault Tree Analysis |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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. | 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. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 h | 1-2 Tage | 2-6 h | 15-45 min |
Participantsdifferent | 3-8 | 1-4 | 3-8 | 1-3 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Architecture Document, Context View, Runtime View, Deployment View | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | ADR File, Decision Log, Rationale |
Tagsno overlap | FailureResilienceRisk | ArchitectureDocumentationCommunication | RiskRoot causeSafety | ArchitectureRationaleDocumentationGovernance |