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 Change Analysis.
Operations
Change Analysis
Paper illustration of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Paper illustration for Risk Storming.
Architecture
Risk Storming
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Purposedifferent
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.When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down.Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog.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
MediumMediumLowHigh
Timedifferent
45-120 min1-2 h je Session60-90 minPreparation, scenario analysis, and findings review; effort depends on scope
Participantsdifferent
2-6Based on research question4-12Architecture experts and stakeholders for scenarios and weighting
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Change Matrix, Cause Hypotheses, Validation Questions, Action ListUsability Issues, Severity List, RecommendationsAnnotated Diagram, Prioritized Risk List, Action BacklogDomain 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
ChangeRoot causeTroubleshootingComparison
ValidationUXPrototype
RiskArchitectureWorkshopValidation
ArchitectureChangeAnalysisComparisonQuality
Add more methods