Chapter 3: Requirements and Use Cases - KGConf/BookClub-OntologyEngineering GitHub Wiki

Questions

The unanswered question from the last session:

  • Are there models for transforming Natural Language grammar diagramming (Phrase brackets) to concept maps?
  • I am interested to know if techniques exist for the transformation of English grammar diagrams, such as Phrase Bracketing converted to concept maps. I understand concept mapping but I can't find a source that explains diagramming conventions used by linguists to be able to relate the two approaches. thanks

Matthias

  • "The user stories should come from stakeholders in the project rather than from developers (or ontologists)" (3.1, page 28). It makes sense, though in practice stakeholders are not necessarily aware of this kind of use case approach and even less in the context of an ontology development project. Do you have some tips concerning how to get the stakeholders involved and extract the requirements from them?

Ann Clark

  • Do use cases and requirements gathering processes differ when you are working with top-level vs mid-level ontologies? If so, how?

Meeting Minutes

  • (Best) Paper concerning competency questions: https://link.springer.com/chapter/10.1007/978-0-387-34847-6_3
  • Be careful about when and to stop modelling. Use cases force to stick to the business needs.
  • Try getting people involved by making propositions that can then be corrected by the clients.
  • A top-level ontology should not drive the use cases and competency questions. It should be the opposite. You should choose to use an existing ontology based on the use cases and competency questions.
  • Be very careful about the restriction you put on your classes, in particular the disjointness ones.
  • There is no one best practice.