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 for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Communication Plan
Delivery
Communication Plan
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
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.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.When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
1-2 Tage1-3 h45-90 min15-45 min
Participantsdifferent
1-41-82-61-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewArgument Map, Evidence Gaps, Decision RationaleCommunication Plan, Channel Matrix, Message CadenceADR File, Decision Log, Rationale
Tagsno overlap
ArchitectureDocumentationCommunication
SensemakingDecisionRationale
CommunicationStakeholdersDeliveryPlanning
ArchitectureRationaleDocumentationGovernance
Add more methods