View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ATAM (Architecture Tradeoff Analysis Method)User InterviewsPersonasLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  UX Research User Interviews |  UX Research Personas |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
Purposedifferent | 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. | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions. | 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. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30–60 min per interview | 1-3 Tage | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1 participant per interview | Internes Team | 1 or a small team; particularly suitable for 3–4 people |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Interview Notes, Themes, Insight Summary | Persona Profiles, Needs Summary, Scenario Notes | 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 |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | QualitativeResearchCustomerDiscovery | ResearchCustomerSynthesis | ArchitectureQualityRiskAssessmentLean |