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)LASR (Lightweight Approach for Software Reviews)Acceptance Criteria WorkshopExample Mapping
| Criterion |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Acceptance Criteria Workshop |  Agile Example Mapping |
|---|---|---|---|---|
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. | 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 story needs clear checkpoints before implementation, it sharpens expectation and scope together. It sorts work by value, risk, and delivery ability. The result is captured as Acceptance Criteria and a Story Update. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Several meetings plus preparation and analysis; total effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 20-40 min pro Story | 30-60 min |
Participantsdifferent | Evaluation team, architects, and relevant stakeholders | 1 or a small team; particularly suitable for 3–4 people | 3-6 | 3-7 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | 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 | 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 | Acceptance Criteria, Story Update | Example Map, Acceptance Criteria, Open Questions |
Tagsno overlap | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureQualityRiskAssessmentLean | AgileRequirementsRefinementBehavior-Driven Development | Behavior-Driven DevelopmentRequirementsExamplesRefinement |