View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Knowledge Modeling Competency Questions |  Knowledge Modeling Linked Open Terms |  Engineering Hypothesis-Driven Troubleshooting |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-180 min | 2-4 h | Wochen bis Monate | 30-240 min |
Participantsdifferent | 1-6 | 2-8 | 2-8 | 1-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary |
Tagsno overlap | TroubleshootingDiagnosisEngineering | OntologyKnowledge graphScopeRequirementsSemantic | OntologyMethodologyAgileSemantic | TroubleshootingProblem solvingDiagnosis |