View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Competency QuestionsLASR (Lightweight Approach for Software Reviews)Example MappingSpecification by Example
| Criterion |  Knowledge Modeling Competency Questions |  Architecture LASR (Lightweight Approach for Software Reviews) |  Agile Example Mapping |  Agile Specification by Example |
|---|---|---|---|---|
Purposedifferent | Competency Questions translate a domain model into concrete questions that it must be able to answer. The method keeps the model's scope clean and prevents pretty but useless structures. | 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 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 | Medium | Medium | Low | Medium |
Timedifferent | 2-4 h | 3–4 h for initial assessment; preparation and deeper analysis additional | 30-60 min | 60-90 min pro Feature |
Participantsdifferent | 2-8 | 1 or a small team; particularly suitable for 3–4 people | 3-7 | 3-6 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | 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 | Example Table, Acceptance Tests |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ArchitectureQualityRiskAssessmentLean | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AgileRequirementsExamplesBehavior-Driven Development |