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 |  Architecture C4 Model |  Architecture Risk Storming |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-2 Tage | 1-4 h | 60-90 min |
Participantsdifferent | 3-8 | 1-4 | 1-5 | 4-12 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | FailureResilienceRisk | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization | RiskArchitectureWorkshopValidation |