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 ABC Analysis |  Knowledge Modeling Ontology Design Patterns |  Delivery MoSCoW |
|---|---|---|---|---|
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. | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | Ontology Design Patterns provide reusable building blocks for recurring modeling problems. The method brings structure to the search for clean concepts, relationships, and roles. | When a release carries too many demands and priorities are only ever negotiated, MoSCoW creates clear boundaries for the next cut. Must, Should, Could, and Won't make commitment, room for maneuver, and trade-off logic visible to everyone involved. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 2-4 h | 30-60 min | 1-3 h pro Pattern | 30-90 min |
Participantsdifferent | 2-8 | 1-5 | 1-6 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | ABC Classification, Focus Rules, Control List | Selected Patterns, Adapted Schema Fragments, Pattern Documentation | Prioritized Backlog, Release Scope, Tradeoff Notes |
Tagsno overlap | OntologyKnowledge graphScopeRequirementsSemantic | PrioritizationOperationsPortfolio | OntologyPatternsReuseSemanticModeling | PrioritizationScopeDecision |