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 | ![]() DevOps Game Day | ![]() DevOps Incident Command | ![]() 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. | In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic. | During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once. | 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 | High | Medium | Medium |
Timedifferent | Wochen bis Monate | Halber Tag | As needed | 2-4 h |
Participantsdifferent | 2-8 | 5-20 | 4-15 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Simulation Notes, Gaps List, Updated Runbooks | Incident Log, Action Tracker, Stakeholder Updates | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | OntologyMethodologyAgileSemantic | ResilienceOperationsIncident | IncidentOperationsReliability | OntologyKnowledge graphScopeRequirementsSemantic |



