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)Assumption MappingRisk StormingLASR (Lightweight Approach for Software Reviews)
| Criterion |  Architecture SAAM (Software Architecture Analysis Method) |  Product Discovery Assumption Mapping |  Architecture Risk Storming |  Architecture LASR (Lightweight Approach for Software Reviews) |
|---|---|---|---|---|
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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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. | 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. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Preparation, scenario analysis, and findings review; effort depends on scope | 45-60 min | 60-90 min | 3–4 h for initial assessment; preparation and deeper analysis additional |
Participantsdifferent | Architecture experts and stakeholders for scenarios and weighting | 2-8 | 4-12 | 1 or a small team; particularly suitable for 3–4 people |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
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 | Assumption map, Test backlog, Risk ranking | Annotated Diagram, Prioritized Risk List, Action Backlog | 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 |
Tagsno overlap | ArchitectureChangeAnalysisComparisonQuality | AssumptionsRiskExperimentsValidation | RiskArchitectureWorkshopValidation | ArchitectureQualityRiskAssessmentLean |