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 |  Operations Fault Tree Analysis |  Architecture Architecture Communication Canvas |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | High | Medium | Low |
Timedifferent | 1-3 h | 2-6 h | 60-120 min | 1-2 Tage |
Participantsdifferent | 3-8 | 3-8 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FailureResilienceRisk | RiskRoot causeSafety | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |