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 Shape-First Modeling |  Operations Failure Mode and Effects Analysis |  Operations Fishbone Diagram |  Knowledge Modeling Competency Questions |
|---|---|---|---|---|
Purposedifferent | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. | 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 | Low | Medium |
Timedifferent | Halber Tag pro Domain Slice | 2-6 h | 30-60 min | 2-4 h |
Participantsdifferent | 1-4 | 3-10 | 2-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix |
Tagsno overlap | Knowledge graphValidationSemantic | RiskQualityOperationsRoot cause | Root causeQualityOperations | OntologyKnowledge graphScopeRequirementsSemantic |