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 Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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.
Complexitydifferent
HighMediumLowLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope1-4 h30-60 min15-30 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders3-81-62-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanPareto Chart, Top Causes, Focus ListRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
Root causeProblem solvingQualityIncident
PrioritizationQualityFocusRoot cause
Root causeIncidentLeanProblem solving
Add more methods