View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Diary Study | ![]() Delivery RAID Log | ![]() Knowledge Modeling NeOn Methodology | ![]() Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Medium | Low | High | Medium |
Timedifferent | 1-4 Wochen | 30 min Setup, dann laufend | Mehrere Wochen bis Monate | 2-4 h |
Participantsdifferent | 5-20 | 1-3 maintaining, briefing for everyone | 2-10 | 2-8 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | RAID Log, Status Report Source | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | UX researchTrackingBehavior | RiskTrackingStakeholdersGovernance | OntologyMethodologyReuseSemanticEngineering | OntologyKnowledge graphScopeRequirementsSemantic |



