View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:arc42Acceptance Criteria WorkshopLASR (Lightweight Approach for Software Reviews)Specification by Example
| Criterion |  Architecture arc42 |  Agile Acceptance Criteria Workshop |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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. | 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 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. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 1-2 Tage | 20-40 min pro Story | 3–4 h for initial assessment; preparation and deeper analysis additional | 60-90 min pro Feature |
Participantsdifferent | 1-4 | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Acceptance Criteria, Story Update | 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 Table, Acceptance Tests |
Tagsno overlap | ArchitectureDocumentationCommunication | AgileRequirementsRefinementBehavior-Driven Development | ArchitectureQualityRiskAssessmentLean | AgileRequirementsExamplesBehavior-Driven Development |