methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for Change Analysis.
Operations
Change Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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.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.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.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.
Complexitydifferent
LowLowMediumLow
Timedifferent
1-4 h15-45 min45-120 min1-2 Tage
Participantsdifferent
1-51-32-61-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Diagram, Container Diagram, Component DiagramADR File, Decision Log, RationaleChange Matrix, Cause Hypotheses, Validation Questions, Action ListArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ArchitectureCommunicationVisualization
ArchitectureRationaleDocumentationGovernance
ChangeRoot causeTroubleshootingComparison
ArchitectureDocumentationCommunication
Add more methods