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 Evaporating Cloud Architecture Decision Record ATAM (Architecture Tradeoff Analysis Method)

Criterion	Knowledge Modeling Knowledge Mapping	Systems Thinking Evaporating Cloud	Architecture Architecture Decision Record	Architecture ATAM (Architecture Tradeoff Analysis Method)
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.	The method makes visible why two seemingly incompatible demands arise and which assumption must be tested to resolve the conflict.	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.	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.
Complexitydifferent	Medium	Medium	Low	High
Timedifferent	1-3 h	60-120 min	15-45 min	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	3-12	2-8	1-3	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Workshop	Workshop	Async	Workshop + async
Outputdifferent	Knowledge Map, Critical Knowledge Areas, Transfer Plan	Conflict Cloud, Assumption List, Breakthrough Ideas, Next Experiments	ADR File, Decision Log, Rationale	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap	KnowledgeMappingRisk	Theory of ConstraintsAssumptionsSystems thinking	ArchitectureRationaleDocumentationGovernance	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods