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
Paper illustration for Trade-off Analysis.
Decision Making
Trade-off Analysis
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.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.With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects.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
LowLowMediumMedium
Timedifferent
1-2 Tage15-45 min45-120 min1-3 h
Participantsdifferent
1-41-32-81-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewADR File, Decision Log, RationaleTrade-off Matrix, Criteria List, Decision Rationale, Accepted DownsidesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
ArchitectureRationaleDocumentationGovernance
TradeoffsDecisionCriteriaOptions
SensemakingDecisionRationale
Add more methods