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 IBIS |  Knowledge Modeling Competency Questions |  Delivery MoSCoW |  Knowledge Modeling Linked Open Terms |
|---|---|---|---|---|
Purposedifferent | IBIS structures thinking about complex questions as a sequence of issues, ideas, and arguments. The method keeps discussions open without forcing them into premature consensus. | 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. | 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. | Linked Open Terms connects terminology work with linked-data thinking and makes terminology technically connectable. Vocabulary, meanings, and references can thereby be maintained consistently. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 2-4 h | 30-90 min | Wochen bis Monate |
Participantsdifferent | 2-8 | 2-8 | 3-12 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Issue Map, Positions, Argument Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Prioritized Backlog, Release Scope, Tradeoff Notes | Ontology Requirements, Conceptual Model, Published Ontology, Documentation, Maintenance Plan |
Tagsno overlap | RationaleKnowledgeDecision | OntologyKnowledge graphScopeRequirementsSemantic | PrioritizationScopeDecision | OntologyMethodologyAgileSemantic |