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 Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration for Pareto Analysis
Decision Making
Pareto Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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 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.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.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.
Complexitydifferent
HighMediumLowHigh
Timedifferent
2-6 h45-120 min30-60 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
3-102-61-6Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
FMEA Table, Risk Priority, Mitigation ActionsChange Matrix, Cause Hypotheses, Validation Questions, Action ListPareto Chart, Top Causes, Focus ListDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives
Tagsno overlap
RiskQualityOperationsRoot cause
ChangeRoot causeTroubleshootingComparison
PrioritizationQualityFocusRoot cause
ArchitectureChangeAnalysisComparisonQuality
Add more methods