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)Problem InterviewLASR (Lightweight Approach for Software Reviews)Risk Storming
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Product Discovery Problem Interview |  Architecture LASR (Lightweight Approach for Software Reviews) |  Architecture Risk Storming |
|---|---|---|---|---|
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 the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. | 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 | High | Medium | Medium | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 30-60 min je Interview | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 5-12 Interviews | 1 or a small team; particularly suitable for 3–4 people | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Problem Evidence, Risk Notes, Customer Segments | 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 | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | DiscoveryInterviewsValidation | ArchitectureQualityRiskAssessmentLean | RiskArchitectureWorkshopValidation |