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)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration for Change Analysis.
Operations
Change Analysis
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.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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitydifferent
HighLowMediumMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope15-30 min1-3 h45-120 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting2-62-82-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
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 alternativesRoot cause notes, CountermeasuresGap Matrix, Action Plan, Risk NotesChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
Root causeIncidentLeanProblem solving
StrategyAnalysisPlanning
ChangeRoot causeTroubleshootingComparison
Add more methods