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 Competency Questions with its method-specific working model.
Knowledge Modeling
Competency Questions
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 Acceptance Criteria Workshop with a method-specific labelled workspace.
Agile
Acceptance Criteria Workshop
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.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 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.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
Wochen bis Monate2-4 h3–4 h for initial assessment; preparation and deeper analysis additional20-40 min pro Story
Participantsdifferent
2-82-81 or a small team; particularly suitable for 3–4 people3-6
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance PlanCompetency Question Set, Required Concepts, Test Queries, Coverage MatrixLean 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 checksAcceptance Criteria, Story Update
Tagsno overlap
OntologyMethodologyAgileSemantic
OntologyKnowledge graphScopeRequirementsSemantic
ArchitectureQualityRiskAssessmentLean
AgileRequirementsRefinementBehavior-Driven Development
Add more methods