View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Scatter Diagram |  Operations Fault Tree Analysis |  Architecture C4 Model |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | 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. | 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 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. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Low | High | Low | High |
Timedifferent | 30-90 min | 2-6 h | 1-4 h | 2-6 h |
Participantsdifferent | 1-4 | 3-8 | 1-5 | 3-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Context Diagram, Container Diagram, Component Diagram | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | Root causeQualityVisualization | RiskRoot causeSafety | ArchitectureCommunicationVisualization | RiskQualityOperationsRoot cause |