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
A paper-based illustration representing Kano Model with its core stages and visible working result.
Product Discovery
Kano Model
Paper illustration for Change Analysis.
Operations
Change Analysis
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
When features need to be distinguished by their effect on satisfaction, it makes expectations and surprises comparable. It separates basic needs, performance contribution, and delight.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.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 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.
Complexitydifferent
MediumMediumHighHigh
Timedifferent
1-2 Tage45-120 minPreparation, scenario analysis, and findings review; effort depends on scope2-6 h
Participantsdifferent
10-502-6Architecture experts and stakeholders for scenarios and weighting3-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Kano Matrix, Feature Classes, Priority ThemesChange Matrix, Cause Hypotheses, Validation Questions, Action 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 alternativesFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
SatisfactionPrioritizationCustomer
ChangeRoot causeTroubleshootingComparison
ArchitectureChangeAnalysisComparisonQuality
RiskQualityOperationsRoot cause
Add more methods