View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Specification by ExampleLASR (Lightweight Approach for Software Reviews)Competency QuestionsLinked Open Terms
| Criterion |  Agile Specification by Example |  Architecture LASR (Lightweight Approach for Software Reviews) |  Knowledge Modeling Competency Questions |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | 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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 60-90 min pro Feature | 3–4 h for initial assessment; preparation and deeper analysis additional | 2-4 h | Wochen bis Monate |
Participantsdifferent | 3-6 | 1 or a small team; particularly suitable for 3–4 people | 2-8 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Example Table, Acceptance Tests | 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 | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | AgileRequirementsExamplesBehavior-Driven Development | ArchitectureQualityRiskAssessmentLean | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic |