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)Dot VotingLASR (Lightweight Approach for Software Reviews)Nominal Group Technique
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Facilitation Dot Voting |  Architecture LASR (Lightweight Approach for Software Reviews) |  Facilitation Nominal Group Technique |
|---|---|---|---|---|
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 a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection. | 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. | When loud voices could dominate a round, Nominal Group Technique protects individual thinking time from group effects. It collects ideas separately first and only then enables shared weighting. |
Complexitydifferent | High | Low | Medium | Medium |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 5-15 min | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-120 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 3-20 | 1 or a small team; particularly suitable for 3–4 people | 5-12 |
Formatdifferent | Workshop + async | Workshop | 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 | Ranked list, Consensus signal, Shortlist | 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 | Ranked Ideas, Clarified Options, Group Priority |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | FacilitationVotingConsensusPrioritization | ArchitectureQualityRiskAssessmentLean | FacilitationPrioritizationVotingInclusion |