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 for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.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.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.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.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
30-240 min1-4 hPreparation, scenario analysis, and findings review; effort depends on scope1-3 h
Participantsdifferent
1-63-8Architecture experts and stakeholders for scenarios and weighting2-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
Root causeProblem solvingQualityIncident
ArchitectureChangeAnalysisComparisonQuality
Root causeTreeIncidentQuality
Add more methods