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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration for Eat the Frog
Operations
Eat the Frog
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.The method protects energy and attention for the task that creates the largest progress and is often postponed.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
LowLowLowLow
Timedifferent
1-4 h1-2 Tage15-90 min daily15-45 min
Participantsdifferent
1-51-411-3
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Context Diagram, Container Diagram, Component DiagramArchitecture Document, Context View, Runtime View, Deployment ViewPriority Task, Completion Note, Daily FocusADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureCommunicationVisualization
ArchitectureDocumentationCommunication
PrioritizationProductivityFocusExecution
ArchitectureRationaleDocumentationGovernance
Add more methods