View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:SAAM (Software Architecture Analysis Method)LASR (Lightweight Approach for Software Reviews)Example MappingAcceptance Criteria Workshop
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Example Mapping |  Agile Acceptance Criteria Workshop |
|---|---|---|---|---|
Purposedifferent | SAAM helps teams judge an architecture’s suitability for selected tasks and changes. It is particularly useful for examining modifiability and comparing architecture alternatives with clear reasoning. | 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 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. | 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. |
Complexitydifferent | High | Medium | Low | Low |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min | 20-40 min pro Story |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 1 or a small team; particularly suitable for 3–4 people | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Domain functions mapped to components and connections, Quality attributes and evaluation criteria, Typical tasks and their effects on the architecture, Reasoned evaluation or comparison of alternatives | 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 | Example Map, Acceptance Criteria, Open Questions | Acceptance Criteria, Story Update |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | ArchitectureQualityRiskAssessmentLean | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsRefinementBehavior-Driven Development |