Ontology Requirements Specification



The goal of the ontology requirements specification activity is to state why the ontology is being built, what its intended uses are, who the end users are, and which requirements the ontology should fulfill. This chapter presents detailed methodological guidelines for specifying ontology requirements efficiently. These guidelines will help ontology engineers to capture ontology requirements and produce the ontology requirements specification document (ORSD). The ORSD will play a key role during the ontology development process because it facilitates, among other activities, (1) the search and reuse of existing knowledge resources with the aim of reengineering them into ontologies, (2) the search and reuse of ontological resources (ontologies, ontology modules, ontology statements as well as ontology design patterns), and (3) the verification of the ontology along the ontology development.


Domain Expert Functional Requirement Ontology Development Pharmaceutical Sector Methodological Guideline 
These keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.


  1. Buzan T (1974) Use your head. Ariel Books, British Broadcasting Corporation (BBC), LondonGoogle Scholar
  2. Davis A (1993) Software requirements: objects, functions and states. Prentice Hall, Upper Saddle RiverzbMATHGoogle Scholar
  3. Gómez-Pérez JM, Daviaud C, Morera B, Benjamins R, Pariente Lobo T, Herrero Cárcel G, Tort G (2006) NeOn deliverable D8.1.1. Analysis of the pharma domain and requirementsGoogle Scholar
  4. Gómez-Pérez JM, Buil-Aranda C, Pariente Lobo T, Herrero Cárcel G, Baena A (2007) NeOn deliverable D8.3.1. Ontologies for the pharmaceutical case studiesGoogle Scholar
  5. Grüninger M, Fox MS (1995) Methodology for the design and evaluation of ontologies. In: Skuce D (ed) IJCAI95 workshop on basic ontological issues in knowledge sharing, Montreal, pp 6.1–6.10Google Scholar
  6. IEEE (1993) IEEE Recommended practice for software requirements specifications. IEEE Std. 830Google Scholar
  7. Noy NF, McGuinness DL (2001) Ontology development 101: a guide to creating your first ontology. Technical report KSL-01-05, Stanford Knowledge Systems Laboratory, StanfordGoogle Scholar
  8. Sommerville I (2007) Software engineering, 8th edn. Addison-Wesley, London. ISBN 0-321-31379-8zbMATHGoogle Scholar
  9. Staab S, Schnurr HP, Studer R, Sure Y (2001) Knowledge processes and ontologies. IEEE Intell Syst 16(1):26–34CrossRefGoogle Scholar
  10. Uschold M (1996) Building ontologies: towards a unified methodology. In: Watson I (ed) 16th Annual conference of the British Computer Society Specialist Group on Expert Systems, Cambridge, UKGoogle Scholar
  11. Villazón-Terrazas B, Ramírez J, Suárez-Figueroa MC, Gómez-Pérez A (2011) A network of ontology networks for building e-employment advanced systems. Expert Syst Appl 38(11):13612–13624Google Scholar
  12. Wiegers E (2003) Software requirements 2: practical techniques for gathering and managing requirements throughout the product development cycle, 2nd edn. Microsoft Press, Redmond. ISBN 0-7356-1879-8Google Scholar
  13. Wieringa R (1996) Requirements engineering: frameworks for understanding. Wiley, New YorkGoogle Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2012

Authors and Affiliations

  1. 1.Ontology Engineering Group, Facultad de InformáticaUniversidad Politécnica de MadridMadridSpain

Personalised recommendations