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 C4 Model |  Operations Fishbone Diagram |  Operations Scatter Diagram |
|---|---|---|---|---|
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. | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 1-4 h | 30-60 min | 30-90 min |
Participantsdifferent | 3-8 | 1-5 | 2-8 | 1-4 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Context Diagram, Container Diagram, Component Diagram | Fishbone Diagram, Cause Categories, Investigation Backlog | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | FailureResilienceRisk | ArchitectureCommunicationVisualization | Root causeQualityOperations | Root causeQualityVisualization |