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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
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 Argument Mapping
Decision Making
Argument Mapping
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 Tage30-90 min15-45 min1-3 h
Participantsdifferent
1-41-61-31-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewDecision Tree, Option Map, Assumption ListADR File, Decision Log, RationaleArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
DecisionTreeOptions
ArchitectureRationaleDocumentationGovernance
SensemakingDecisionRationale
Add more methods