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 Linked Open Terms | ![]() Engineering Hypothesis-Driven Troubleshooting | ![]() 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 systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 | Medium | Medium | Medium |
Timedifferent | Wochen bis Monate | 30-240 min | 2-4 h |
Participantsdifferent | 2-8 | 1-6 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | OntologyMethodologyAgileSemantic | TroubleshootingProblem solvingDiagnosis | OntologyKnowledge graphScopeRequirementsSemantic |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






