Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Knowledge Mapping arc42 ATAM (Architecture Tradeoff Analysis Method)Architecture Decision Record

Criterion	Knowledge Modeling Knowledge Mapping	Architecture arc42	Architecture ATAM (Architecture Tradeoff Analysis Method)	Architecture Architecture Decision Record
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.	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.	ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.	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	Medium	Low	High	Low
Timedifferent	1-3 h	1-2 Tage	Several meetings plus preparation and analysis; total effort depends on scope	15-45 min
Participantsdifferent	3-12	1-4	Evaluation team, architects, and relevant stakeholders	1-3
Formatdifferent	Workshop	Workshop + async	Workshop + async	Async
Outputdifferent	Knowledge Map, Critical Knowledge Areas, Transfer Plan	Architecture Document, Context View, Runtime View, Deployment View	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	ADR File, Decision Log, Rationale
Tagsno overlap	KnowledgeMappingRisk	ArchitectureDocumentationCommunication	ArchitectureQualityRiskTradeoffsStakeholders	ArchitectureRationaleDocumentationGovernance

Add more methods