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 Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
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 systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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 disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.
Complexitydifferent
HighMediumHighHigh
Timedifferent
Several meetings plus preparation and analysis; total effort depends on scope30-240 min2-6 h2-8 h
Participantsdifferent
Evaluation team, architects, and relevant stakeholders1-63-102-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 investigationsHypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryFMEA Table, Risk Priority, Mitigation ActionsProblem Analysis, Decision Analysis, Risk Plan
Tagsno overlap
ArchitectureQualityRiskTradeoffsStakeholders
TroubleshootingProblem solvingDiagnosis
RiskQualityOperationsRoot cause
Problem solvingRoot causeDecisionOperations
Add more methods