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)Failure Mode and Effects Analysis ABC Analysis Fishbone Diagram

Criterion	Architecture ATAM (Architecture Tradeoff Analysis Method)	Operations Failure Mode and Effects Analysis	Operations ABC Analysis	Operations Fishbone Diagram
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.	For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.	With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.	When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent	High	High	Low	Low
Timedifferent	Several meetings plus preparation and analysis; total effort depends on scope	2-6 h	30-60 min	30-60 min
Participantsdifferent	Evaluation team, architects, and relevant stakeholders	3-10	1-5	2-8
Formatdifferent	Workshop + async	Workshop	Async	Workshop
Outputdifferent	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	FMEA Table, Risk Priority, Mitigation Actions	ABC Classification, Focus Rules, Control List	Fishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap	ArchitectureQualityRiskTradeoffsStakeholders	RiskQualityOperationsRoot cause	PrioritizationOperationsPortfolio	Root causeQualityOperations

Add more methods