Skip to main content

Ontology Requirements Specification

  • Chapter
  • First Online:

Abstract

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.

This is a preview of subscription content, log in via an institution.

Buying options

Chapter
USD   29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD   39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD   54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info
Hardcover Book
USD   54.99
Price excludes VAT (USA)
  • Durable hardcover edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Learn about institutional subscriptions

Notes

  1. 1.

    http://www.ontogrid.net

  2. 2.

    http://esperonto.net/fundfinder

  3. 3.

    http://www.neon-project.org/nw/Ontology-driven_fish_stock_depletion_assessment_system

  4. 4.

    http://www.isoco.com/ontologies/mio/index.html

  5. 5.

    http://www.seemp.org

  6. 6.

    http://www.w3.org/TR/rdf-schema/

  7. 7.

    http://www.wsmo.org/wsml/wsml-syntax

  8. 8.

    In software engineering, functional requirements refer to the required behavior of the system, that is, the functionalities that the software system should have, while non-functional requirements refer to implicit expectations about how well the software system should work. That is, these requirements can be seen as aspects about the system or as “non-behavioral” requirements (Sommerville 2007).

  9. 9.

    http://cicero.uni-koblenz.de/wiki/index.php/Main_Page

  10. 10.

    http://www.whocc.no/atc_ddd_index/

References

  • Buzan T (1974) Use your head. Ariel Books, British Broadcasting Corporation (BBC), London

    Google Scholar 

  • Davis A (1993) Software requirements: objects, functions and states. Prentice Hall, Upper Saddle River

    MATH  Google Scholar 

  • 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 requirements

    Google Scholar 

  • 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 studies

    Google Scholar 

  • 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.10

    Google Scholar 

  • IEEE (1993) IEEE Recommended practice for software requirements specifications. IEEE Std. 830

    Google Scholar 

  • Noy NF, McGuinness DL (2001) Ontology development 101: a guide to creating your first ontology. Technical report KSL-01-05, Stanford Knowledge Systems Laboratory, Stanford

    Google Scholar 

  • Sommerville I (2007) Software engineering, 8th edn. Addison-Wesley, London. ISBN 0-321-31379-8

    MATH  Google Scholar 

  • Staab S, Schnurr HP, Studer R, Sure Y (2001) Knowledge processes and ontologies. IEEE Intell Syst 16(1):26–34

    Article  Google Scholar 

  • 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, UK

    Google Scholar 

  • 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–13624

    Google Scholar 

  • 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-8

    Google Scholar 

  • Wieringa R (1996) Requirements engineering: frameworks for understanding. Wiley, New York

    Google Scholar 

Download references

Author information

Authors and Affiliations

Authors

Corresponding author

Correspondence to Mari Carmen Suárez-Figueroa .

Editor information

Editors and Affiliations

Rights and permissions

Reprints and permissions

Copyright information

© 2012 Springer-Verlag Berlin Heidelberg

About this chapter

Cite this chapter

Suárez-Figueroa, M.C., Gómez-Pérez, A. (2012). Ontology Requirements Specification. In: Suárez-Figueroa, M., Gómez-Pérez, A., Motta, E., Gangemi, A. (eds) Ontology Engineering in a Networked World. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-24794-1_5

Download citation

  • DOI: https://doi.org/10.1007/978-3-642-24794-1_5

  • Published:

  • Publisher Name: Springer, Berlin, Heidelberg

  • Print ISBN: 978-3-642-24793-4

  • Online ISBN: 978-3-642-24794-1

  • eBook Packages: Computer ScienceComputer Science (R0)

Publish with us

Policies and ethics