View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Usability TestingLASR (Lightweight Approach for Software Reviews)ATAM (Architecture Tradeoff Analysis Method)Risk Storming
| Criterion |  UX Research Usability Testing |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture Risk Storming |
|---|---|---|---|---|
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. | LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 1-2 h je Session | 3–4 h for initial assessment; preparation and deeper analysis additional | Several meetings plus preparation and analysis; total effort depends on scope | 60-90 min |
Participantsdifferent | Based on research question | 1 or a small team; particularly suitable for 3–4 people | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Usability Issues, Severity List, Recommendations | Lean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ValidationUXPrototype | ArchitectureQualityRiskAssessmentLean | ArchitectureQualityRiskTradeoffsStakeholders | RiskArchitectureWorkshopValidation |