Advertisement

Using KCPM for Defining and Integrating Domain Ontologies

  • Christian Kop
  • Heinrich C. Mayr
  • Tatjana Zavinska
Part of the Lecture Notes in Computer Science book series (LNCS, volume 3307)

Abstract

The paper discusses the representation and integration of domain ontologies using the Conceptual Predesign Model KCPM. This model initially was developed as a means to bridge, within the information system design cycle, the ‘impedance mismatch’ between natural language requirements specifications and abstract conceptual models (schemas) by an user centered interlingua: Requirements are represented in a formalized fashion by focusing the structural, functional and behavioral terminology of an application domain. Methods and tools have been developed so far, to derive KCPM schemas out of natural language specifications by natural language processing and interpretation techniques, and, to map these schemas, after validation, to any conceptual representation. We introduce the main KCPM modeling concepts and demonstrate, how these may be used to define domain ontologies. Based here-on, aspects of reuse, extension and integration are discussed.

Keywords

Natural Language Processing Domain Expert Business Owner Domain Ontology Book Publishing 
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.

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Batini, C., Ceri, S., Navathe, S.B.: Conceptual Database Design an Entity Relationship Approach, vol. 2. Benjamin Cummings Publ. Company, Redwood (1992)zbMATHGoogle Scholar
  2. 2.
    Bellizona, R., Fugini, M.G., de Mey, V.: Reuse of Specifications and Designs in a Development Information System. In: Prakash, N., et al. (eds.) Proc. IFIP WG8.1 Working Conf. on Information System Development Process, pp. 79–98. North Holland, Amsterdam (1993)Google Scholar
  3. 3.
    Ceri, S. (ed.): Methodology and Tools for Database Design. North Holland, Amsterdam (1983)Google Scholar
  4. 4.
    Cristani, M., Cuel, R.: A Comprehensive Guideline for Building a Domain Ontology from Scratch. In: Proc. 4th International Conference on Knowledge Management I-Know 2004 (2004)Google Scholar
  5. 5.
    Corcho, O., Asuncion, G.P.: A Road Map to Ontology Specification Languages. In: Dieng, R., Corby, O. (eds.) EKAW 2000. LNCS (LNAI), vol. 1937, pp. 80–96. Springer, Heidelberg (2000)CrossRefGoogle Scholar
  6. 6.
    Fensel, D.: Ontologies: A Silver Bullet for Knowledge Management and Electronic Commerce. Springer, Heidelberg (2000)Google Scholar
  7. 7.
    Halpin, T.: Business Rule Verbalization. In: Doroshenko, A., et al. (eds.) Proc. 3rd Int. Conf. on Information Systems Technology and its Applications ISTA 2004, Salt Lake City. GI-edn., Lecture Notes in Informatics (LNI)-p48, pp. 39–52 (2004)Google Scholar
  8. 8.
    Kop, C., Mayr, H.C.: Reusing Domain Knowledge in Requirement Analysis. In: Györkös, J., et al. (eds.) Proc. 3rd Conf. on Re-engineering, Reverse engineering and Reuse of Information Systems, ReTIS 1994, pp. 144–147 (1994)Google Scholar
  9. 9.
    Kop, C., Mayr, H.C.: Conceptual Predesign – Bridging the Gap between Requirements and Conceptual Design. In: Proc. 3rd International Conference on Requirements Engineering ICRE 1998 (April 1998)Google Scholar
  10. 10.
    Mayr, H.C., Kop, C.: A User Centered Approach to Requirements Modeling. In: Glinz, M., Müller-Luschnat, G. (eds.) Proc. Modellierung 2002, GI-edn. Lecture Notes in Informatics, P-12 (LNI), pp. 75–86 (2002)Google Scholar
  11. 11.
    Nijssen, G., Halpin, T.A.: Conceptual Scheme and Relational Database Design - A fact oriented approach. Prentice Hall Publ. Comp., Englewood Cliffs (1989)Google Scholar
  12. 12.
    Noy, N.F., McGuiness, D.L.: Ontology Development 101: a guide to creating your first ontology, http://reliant.teknowledge.com/RKF/publication/Stanford/Ontology%20Tutorial.htm
  13. 13.
    Schreiber, G., et al.: Knowledge Engineering and Management: The Common KADS Methodology. MIT Press, Cambridge (1999)Google Scholar
  14. 14.
    Sutcliffe, A.G., Maiden, N.A.M.: Use of Domain Knowledge for Requirements Validation. In: Prakash, N., et al. (eds.) Proc. IFIP WG8.1 Working Conf. on Information System Development Process, pp. 99–115. North Holland, Amsterdam (1993)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2004

Authors and Affiliations

  • Christian Kop
    • 1
  • Heinrich C. Mayr
    • 1
  • Tatjana Zavinska
    • 1
  1. 1.Institut für Wirtschaftsinformatik und AnwendungssystemeIWAS University of Klagenfurt 

Personalised recommendations