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 |  Operations Change Analysis |  Architecture C4 Model |
|---|---|---|---|---|
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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | 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. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 30-90 min | 1-2 Tage | 45-120 min | 1-4 h |
Participantsdifferent | 1-4 | 1-4 | 2-6 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Scatter Plot, Korrelationsnotiz, Hypothesenliste | Architecture Document, Context View, Runtime View, Deployment View | Change Matrix, Cause Hypotheses, Validation Questions, Action List | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Root causeQualityVisualization | ArchitectureDocumentationCommunication | ChangeRoot causeTroubleshootingComparison | ArchitectureCommunicationVisualization |