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)Quality Attribute WorkshopSpecification by ExampleRisk Storming
| Criterion | ![]() Architecture LASR (Lightweight Approach for Software Reviews) | ![]() Architecture Quality Attribute Workshop | ![]() Agile Specification by Example | ![]() Architecture Risk Storming |
|---|---|---|---|---|
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. | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | When business rules need to become precise, it ties language, example, and test together. It sorts work by value, risk, and delivery ability. The result is captured as an Example Table and Acceptance Tests. | 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. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-4 h | 60-90 min pro Feature | 60-90 min |
Participantsdifferent | 1 or a small team; particularly suitable for 3–4 people | 5-15 | 3-6 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | 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 | Quality Scenarios, Priority List, Architecture Concerns | Example Table, Acceptance Tests | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureQualityRiskAssessmentLean | RequirementsArchitectureWorkshop | AgileRequirementsExamplesBehavior-Driven Development | RiskArchitectureWorkshopValidation |



