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:ATAM (Architecture Tradeoff Analysis Method)arc42 Knowledge Mapping Architecture Decision Record

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

Add more methods