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
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Purposedifferent
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.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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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
MediumLowLowLow
Timedifferent
1-3 h1-4 h1-2 h15-45 min
Participantsdifferent
1-81-53-101-3
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleContext Diagram, Container Diagram, Component DiagramArchitecture Canvas, Goals, Constraints, Quality AttributesADR File, Decision Log, Rationale
Tagsno overlap
SensemakingDecisionRationale
ArchitectureCommunicationVisualization
CanvasArchitectureAlignmentWorkshop
ArchitectureRationaleDocumentationGovernance
Add more methods