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: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
HighHighLowMedium
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope2-6 h15-30 min1-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-102-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsFMEA Table, Risk Priority, Mitigation ActionsRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
RiskQualityOperationsRoot cause
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods