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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.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.SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning.
Complexitydifferent
LowHighHigh
Timedifferent
15-30 minSeveral meetings plus preparation and analysis; total effort depends on scopePreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-6Evaluation team, architects, and relevant stakeholdersArchitecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Root cause notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigationsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskTradeoffsStakeholders
ArchitectureChangeAnalysisComparisonQuality
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Paper illustration for Change Analysis.
Operations
Change Analysis