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 Risk Storming.
Architecture
Risk Storming
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree 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.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.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
HighLowMediumLow
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope60-90 min1-3 h15-30 min
Participantsdifferent
Evaluation team, architects, and relevant stakeholders4-122-82-6
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsAnnotated Diagram, Prioritized Risk List, Action BacklogCause Tree, Evidence Notes, CountermeasuresRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
RiskArchitectureWorkshopValidation
Root causeTreeIncidentQuality
Root causeIncidentLeanProblem solving
Add more methods