View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:LASR (Lightweight Approach for Software Reviews)Fishbowl DiscussionATAM (Architecture Tradeoff Analysis Method)Alignment Mapping
| Criterion | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Facilitation Fishbowl Discussion | ![]() Architecture ATAM (Architecture Tradeoff Analysis Method) | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | 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 a controversial topic needs depth and discipline at the same time, Fishbowl Discussion makes the structure of the conversation transparent. The format keeps the core small enough for real dialogue and open enough for controlled turnover. | 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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 45-90 min | Several meetings plus preparation and analysis; total effort depends on scope | 1-2 h |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 8-80 | Evaluation team, architects, and relevant stakeholders | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | 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 | Discussion Insights, Observed Tensions, Follow-up Questions | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | FacilitationDialogueLarge group | ArchitectureQualityRiskTradeoffsStakeholders | AlignmentStakeholdersStrategyFacilitation |



