View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Competency Questions | ![]() Operations Getting Things Done | ![]() Knowledge Modeling NeOn Methodology | ![]() Operations ALPEN Method |
|---|---|---|---|---|
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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. | With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time. |
Complexitydifferent | Medium | Medium | High | Low |
Timedifferent | 2-4 h | 1-2 h Setup, laufend | Mehrere Wochen bis Monate | 10-20 min daily |
Participantsdifferent | 2-8 | 1 | 2-10 | 1 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Action Lists, Project List, Review Routine | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Daily Plan, Time Estimates, Review Notes |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | ProductivityPlanningTasksExecution | OntologyMethodologyReuseSemanticEngineering | PlanningTime managementProductivityOperations |



