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 Pareto Analysis
Decision Making
Pareto Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
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.In many problem situations, effect is distributed unequally across many causes. A Pareto Analysis separates the few drivers with high leverage from the long remainder and focuses attention on what measurably moves the needle.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.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
HighLowLowMedium
Timedifferent
Preparation, scenario analysis, and findings review; effort depends on scope30-60 min15-30 min45-120 min
Participantsdifferent
Architecture experts and stakeholders for scenarios and weighting1-62-62-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + 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 alternativesPareto Chart, Top Causes, Focus ListRoot cause notes, CountermeasuresChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ArchitectureChangeAnalysisComparisonQuality
PrioritizationQualityFocusRoot cause
Root causeIncidentLeanProblem solving
ChangeRoot causeTroubleshootingComparison
Add more methods