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 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
Paper illustration for Change Analysis.
Operations
Change Analysis
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h15-45 min45-120 min1-2 Tage
Participantsdifferent
3-121-32-61-4
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanADR File, Decision Log, RationaleChange Matrix, Cause Hypotheses, Validation Questions, Action ListArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
KnowledgeMappingRisk
ArchitectureRationaleDocumentationGovernance
ChangeRoot causeTroubleshootingComparison
ArchitectureDocumentationCommunication
Add more methods