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 Kepner-Tregoe
Operations
Kepner-Tregoe
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.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.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-8 h30-60 min1-4 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders2-82-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsProblem Analysis, Decision Analysis, Risk PlanFishbone Diagram, Cause Categories, Investigation BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Problem solvingRoot causeDecisionOperations
Root causeQualityOperations
Root causeProblem solvingQualityIncident
Add more methods