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 Fault Tree Analysis |  Operations Family Tree Analysis |  Knowledge Modeling Ontology Design Patterns |
|---|---|---|---|---|
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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 2-4 h | 2-6 h | 2-4 h | 1-3 h pro Pattern |
Participantsdifferent | 2-8 | 3-8 | 2-6 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions | Family Tree Diagram, Pattern Notes, Systemic Measures | Selected Patterns, Adapted Schema Fragments, Pattern Documentation |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | RiskRoot causeSafety | Root causePatternsIncidentSystemic | OntologyPatternsReuseSemanticModeling |