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
Paper illustration of Linked Open Terms with its method-specific working model.
Knowledge Modeling
Linked Open Terms
Paper illustration of a yellow story card, blue rule cards, green example cards and a red question card on a light workspace.
Agile
Example Mapping
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 Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
Purposedifferent
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 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.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
Wochen bis Monate30-60 min3–4 h for initial assessment; preparation and deeper analysis additional2-4 h
Participantsdifferent
2-83-71 or a small team; particularly suitable for 3–4 people2-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanExample Map, Acceptance Criteria, Open QuestionsLean 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 checksCompetency Question Set, Required Concepts, Test Queries, Coverage Matrix
Tagsno overlap
OntologyMethodologyAgileSemantic
Behavior-Driven DevelopmentRequirementsExamplesRefinement
ArchitectureQualityRiskAssessmentLean
OntologyKnowledge graphScopeRequirementsSemantic
Add more methods