LASR according to Toth/Zörner
Details
- Full Name
-
LASR – Lightweight Approach for Software Reviews (Stefan Toth & Stefan Zörner)
- Also known as
-
LASR Reviews
Core Concepts:
- A review method
-
LASR is a structured method for efficient software reviews — it uncovers weaknesses in software solutions and challenges technical and architectural ideas. More streamlined than ATAM, but still focused on key quality aspects
- Lean Mission Statement
-
Condense the system’s vision into a short, shared statement as the review’s reference point
- Evaluation Criteria
-
Identify the system’s top quality attributes — the quantified objectives form the review benchmark
- Risk-based Review
-
Identify the most significant risks against those objectives
- Quality-focused Analysis
-
Analyze the controversial gaps (or their absence) in depth
- LASR Result Diagram
-
Quantifies the review: the objectives form a benchmark line, the system assessment a second line — the gaps between them drive the deeper analysis
- Workshop format
-
A moderated, game-like team event (LASR-Cards, templates and checklists as Print & Play material); works with few people, on site or remote, first results within hours
- Community-driven and free
-
Open license, free to use in commercial contexts; supported by embarc
- Key Proponents
-
Stefan Toth & Stefan Zörner ("Reviewing Software Systems", Leanpub, 2023; German edition "Software-Systeme reviewen"); canonical site lasr-reviews.org
When to Use:
-
Reviewing a software system or solution idea when ATAM is too heavyweight
-
Validating an architecture against its most important quality attributes
-
Uncovering and prioritising technical risks with the whole team in a short workshop
-
Establishing a recurring, lightweight review practice
Related Anchors:
-
ATAM — the heavyweight scenario-based evaluation method LASR streamlines
-
arc42 Architecture Documentation — the documentation counterpart; LASR reviews what arc42 documents
-
Quality Attribute Scenario — a rigorous form the evaluation criteria can take
Current Status:
-
The canonical sources are lasr-reviews.org and the book "Reviewing Software Systems" (Toth & Zörner, Leanpub, 2023)
-
The prior is thin — a 2023 self-published method from two German consultants with essentially one community site. LLMs reliably know the name at best, not the method: supply the steps from lasr-reviews.org in the prompt rather than trusting the anchor alone
-
A cautionary tale from this catalog itself: an earlier version of this entry confidently described LASR as a "lightweight architecture documentation template" with an invented acronym expansion — silent substitution on a thin prior, exactly the Use-Case-3.0 failure mode. Corrected against the verified sources in June 2026