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 |  Architecture arc42 |  Decision Making Pareto Analysis |  Architecture Architecture Decision Record |
|---|---|---|---|---|
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. | 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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 30-90 min | 1-2 Tage | 30-60 min | 15-45 min |
Participantsdifferent | 1-4 | 1-4 | 1-6 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Architecture Document, Context View, Runtime View, Deployment View | Pareto Chart, Top Causes, Focus List | ADR File, Decision Log, Rationale |
Tagsno overlap | Root causeQualityVisualization | ArchitectureDocumentationCommunication | PrioritizationQualityFocusRoot cause | ArchitectureRationaleDocumentationGovernance |