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 of a participant using a prototype while an observer takes notes beside a highlighted usability issue.
UX Research
Usability Testing
Paper illustration with architecture components and concrete change tasks for comparison.
Architecture
SAAM (Software Architecture Analysis Method)
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for Change Analysis.
Operations
Change Analysis
Purposedifferent
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.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.ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.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
MediumHighMediumMedium
Timedifferent
1-2 h je SessionPreparation, scenario analysis, and findings review; effort depends on scope2–4 h review as a planning range; preparation and evaluation additional45-120 min
Participantsdifferent
Based on research questionArchitecture experts and stakeholders for scenarios and weightingDesigners, developers as users, and facilitation2-6
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Usability Issues, Severity List, RecommendationsDomain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternativesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
ValidationUXPrototype
ArchitectureChangeAnalysisComparisonQuality
ArchitectureEngineeringFeedbackValidationTasks
ChangeRoot causeTroubleshootingComparison
Add more methods