View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Knowledge Modeling Competency Questions |  Domain Modeling Domain Context Map |  Knowledge Modeling NeOn Methodology |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole. | The NeOn Methodology structures ontology work as a controlled process with reuse, scenarios, and reviews. It is useful when ontologies should not emerge ad hoc but modularly and reusably. |
Complexitydifferent | Medium | Medium | Medium | High |
Timedifferent | 1-3 h | 2-4 h | 1-3 h | Mehrere Wochen bis Monate |
Participantsdifferent | 2-8 | 2-8 | 3-10 | 2-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Competency Question Set, Required Concepts, Test Queries, Coverage Matrix | Domain Context Map, Boundary Notes, Ownership Map | Ontology Requirements Specification, Reuse Plan, Ontology Modules, Evaluation Report |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | OntologyKnowledge graphScopeRequirementsSemantic | Domain-Driven DesignContextBoundaries | OntologyMethodologyReuseSemanticEngineering |