View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture C4 Model |  Decision Making Pareto Analysis |  Operations Failure Mode and Effects Analysis |  Operations Scatter Diagram |
|---|---|---|---|---|
Purposedifferent | 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. | In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle. | 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. | 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 | Low | Low | High | Low |
Timedifferent | 1-4 h | 30-60 min | 2-6 h | 30-90 min |
Participantsdifferent | 1-5 | 1-6 | 3-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Pareto Chart, Top Causes, Focus List | FMEA Table, Risk Priority, Mitigation Actions | Scatter Plot, Korrelationsnotiz, Hypothesenliste |
Tagsno overlap | ArchitectureCommunicationVisualization | PrioritizationQualityFocusRoot cause | RiskQualityOperationsRoot cause | Root causeQualityVisualization |