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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
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.Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
LowMediumLowMedium
Timedifferent
1-2 Tage1-3 h15-45 min60-120 min
Participantsdifferent
1-43-121-32-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewKnowledge Map, Critical Knowledge Areas, Transfer PlanADR File, Decision Log, RationaleCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
ArchitectureDocumentationCommunication
KnowledgeMappingRisk
ArchitectureRationaleDocumentationGovernance
ArchitectureCommunicationStakeholdersCanvas
Add more methods