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 arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Purposedifferent
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.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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.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
LowLowHighLow
Timedifferent
1-2 Tage15-45 min1-4 Wochen1-4 h
Participantsdifferent
1-41-31-61-5
Formatdifferent
Workshop + asyncAsyncAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationaleExperiment results, Decision log, Learning summaryContext Diagram, Container Diagram, Component Diagram
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
ExperimentsGrowthAnalyticsValidation
ArchitectureCommunicationVisualization
Add more methods