methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Paper illustration of Specification by Example with a method-specific labelled workspace.
Agile
Specification by Example
Paper illustration of Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
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.Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently.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.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
3–4 h for initial assessment; preparation and deeper analysis additionalWochen bis Monate60-90 min pro Feature2-4 h
Participantsdifferent
1 or a small team; particularly suitable for 3–4 people2-83-62-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
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 checksOntology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanExample Table, Acceptance TestsCompetency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap
ArchitectureQualityRiskAssessmentLean
OntologyMethodologyAgileSemantic
AgileRequirementsExamplesBehavior-Driven Development
OntologyKnowledge graphScopeRequirementsSemantic
Add more methods