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 with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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.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.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 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
HighMediumHighLow
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope1-4 h2-6 h15-30 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting3-83-102-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanFMEA Table, Risk Priority, Mitigation ActionsRoot cause notes, Countermeasures
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Root causeProblem solvingQualityIncident
RiskQualityOperationsRoot cause
Root causeIncidentLeanProblem solving
Add more methods