Ontology for Information Systems (O4IS) Design Methodology Conceptualizing, Designing and Representing Domain Ontologies
Total Page:16
File Type:pdf, Size:1020Kb
Ontology for Information Systems (O4IS) Design Methodology Conceptualizing, Designing and Representing Domain Ontologies Vandana Kabilan October 2007. A Dissertation submitted to The Royal Institute of Technology in partial fullfillment of the requirements for the degree of Doctor of Technology . The Royal Institute of Technology School of Information and Communication Technology Department of Computer and Systems Sciences IV DSV Report Series No. 07–013 ISBN 978–91–7178–752–1 ISSN 1101–8526 ISRN SU–KTH/DSV/R– –07/13– –SE V All knowledge that the world has ever received comes from the mind; the infinite library of the universe is in our own mind. – Swami Vivekananda. (1863 – 1902) Indian spiritual philosopher. The whole of science is nothing more than a refinement of everyday thinking. – Albert Einstein (1879 – 1955) German-Swiss-U.S. scientist. Science is a mechanism, a way of trying to improve your knowledge of na- ture. It’s a system for testing your thoughts against the universe, and seeing whether they match. – Isaac Asimov. (1920 – 1992) Russian-U.S. science-fiction author. VII Dedicated to the three KAs of my life: Kabilan, Rithika and Kavin. IX Abstract. Globalization has opened new frontiers for business enterprises and human com- munication. There is an information explosion that necessitates huge amounts of informa- tion to be speedily processed and acted upon. Information Systems aim to facilitate human decision-making by retrieving context-sensitive information, making implicit knowledge ex- plicit and to reuse the knowledge that has already been discovered. A possible answer to meet these goals is the use of Ontology. Ontology has been studied for a long time in the fields of AI, Logic and Linguistics. Cur- rent state-of-the art research in Information Systems has focused on the use of ontologies. However, there remain many obstacles for the practical and commercial use of ontologies for Information Systems. One such obstacle is that current Information System designers lack the know-how to successfully design an ontology. Current ontology design methodologies are difficult to use by Information Systems designers having little theoretical knowledge of ontol- ogy modeling. Another issue is that business enterprises mostly function in the social domain where there are complex underlying semantics and pragmatics involved. This research tries to solve some of these issues by proposing the Ontology for Information Systems (O4IS) Design Methodology for the design of ontologies for Information Systems. The research also proposes a Unified Semantic Procedural Pragmatic Design for explicit conceptu- alization of the semantics and pragmatics of a domain. We further propose a set of Semantic Analysis Representations as conceptual analysis patterns for semantic relationship identifica- tion. We also put forward the Dual Conceptual Representation so that the designed ontology is understandable by both humans and machines. Finally, a logical architecture for domain ontology design called the Multi-Tier Domain Ontology Architecture is proposed. We follow the design science in Information Systems research methodology. The proposed solutions are demonstrated through two case studies carried out in different domains. The first case study is that of business contract knowledge management, which focuses on the analysis of contractual obligations, their fulfillment via the performance of business actions, and the deduction of a contract compliant workflow model. The second case study relates to military operations simulations and modeling. The emphasis in this case study is to analyze, model and represent the domain knowledge as a re-usable resource to be used in a number of modeling and simulation applications. XI Acknowledgement. It has been an enlightening journey into unknown frontiers, learning to solve new challenges, and finding more pieces of knowledge scattered along the way. But it would not have been possible, if not for the gentle steering and supportive guidance of my supervisor, Prof. Paul Johannesson. I thank – Paul; For being an quintessential supervisor who like a compass activates the magnets of curiosity, knowledge and wisdom. I thank all my colleagues at DSV – Maria, Jelena, Birger, Hercules and everyone else at SYSLAB; For being such excellent listeners, contributors and critics of my theories. I also acknowledge my colleagues at the Swedish Defence Research Agency – Vahid, Mar- ianela and Pernilla; For giving me the opportunity to be a part of their team and for the countless hours of brainstorming. I acknowledge all the wonderful researchers with whom I have had the opportunity to meet and exchange ideas. I specially thank Hans Weigand for his collaboration and construc- tive criticisms. Last, but not the least, this research would never have become a reality, without the sup- port and motivation provided by my family – Mama and Athai; For your constant inspiration and motivation. Mom and Dad; For providing me with the best possible start to life that I could have ever wished for. Priya; For the being the perfect sister and professional proof-reader. Special thanks to my children Rithika and Kavin whose innocent smiles wipe away all exhaustion at the end of each tiring day. Finally, I owe this PhD to the one person who has believed in me always, pushed me harder, to reach higher – my best friend, my love and husband, Kabilan. Thank you for truly shining like the North Star, eternally constant without a flicker. Contents 1 Introduction ::::::::::::::::::::::::::::::::::::::::::::::::::::: 1 1.1 Research Fields . .1 1.1.1 Information Systems . .2 1.1.2 Ontologies for Information Systems . .3 1.1.3 Conceptual Modeling and Ontology . .5 1.2 Research Domain . .7 1.3 Research Motivation: Information systems need ontology . .7 1.4 Research Problems . .9 1.5 Research Questions . 12 1.6 Goal........................................................ 13 1.7 Purpose . 15 1.8 Scope . 15 1.9 Research Methodology . 15 1.10 Research Evaluation Criteria . 18 1.11 Case Studies . 19 1.12 Results . 20 1.13 Disposition . 24 1.14 Publications . 26 2 Knowledge Management and Information Systems :::::::::::::::::: 31 2.1 The Data-Information-Knowledge-Wisdom Model . 31 2.2 Information Systems . 33 2.2.1 Knowledge Base Versus Database Information Systems. 34 2.2.2 Knowledge Bases and Knowledge Base Systems . 35 2.3 Knowledge Management . 36 2.3.1 Knowledge Representation . 38 2.3.2 Different Roles of Knowledge Representation . 38 2.4 Relevance of Chapter . 40 XIV Contents 3 Ontology and Information Systems :::::::::::::::::::::::::::::::: 41 3.1 Ontology . 41 3.2 Uses of Ontologies . 44 3.3 Ontology – A Historical Background . 45 3.3.1 From Philosophy, AI and Logic . 45 3.3.2 From Linguistics to Information Systems . 47 3.3.3 From Knowledge Management to Information Systems . 48 3.3.4 What Information Systems can learn from Philosophical Ontology . 50 3.4 Ontology Types. 52 3.5 Ontology Architectures . 53 3.6 Ontology Design Principles . 54 3.7 Ontology Development Approaches . 54 3.8 Ontology Design Methodologies . 56 3.8.1 Uschold and Gruninger’s Skeletal Method . 57 3.8.2 Gruninger and Fox Method . 57 3.8.3 Noy and McGuinness Method . 59 3.8.4 UPON. 61 3.8.5 METHONTOLOGY . 62 3.8.6 Conceptualization in Methontology . 64 3.9 Relevance of Chapter . 65 4 Conceptual Modeling ::::::::::::::::::::::::::::::::::::::::::::: 67 4.1 Conceptual Model . 68 4.2 Conceptual Modeling Methods . 69 4.2.1 ER Modeling Revisited . 71 4.2.2 Conceptual Graphs . 73 4.3 Intensional and Extensional Conceptual Modeling . 74 4.3.1 Conceptual Modeling Languages. 75 4.4 Using Conceptual Modeling for Ontology Modeling. 75 4.5 Conceptual Modeling Patterns . 77 4.5.1 Design Patterns . 78 4.6 Procedural and Behavior Representation Languages . 82 4.7 Relevance of Chapter . 86 5 Ontology for Information Systems Design Methodology ::::::::::::: 89 5.1 Requirements on O4IS Design Methodology . 92 5.2 Introducing the O4IS Design Methodology . 93 5.2.1 Template for describing the O4IS Design Methodology . 95 5.2.2 G1: Establish the scope of the domain . 95 Contents XV 5.2.3 G2: Establish the targeted users, applications, and functional requirements . 96 5.2.4 G3: Choose ontology architecture: physical and logical . 98 5.2.5 G4: Choose ontology development approach . 99 5.2.6 G5: Choose level of ontology representation . 100 5.2.7 G6: Choose knowledge acquisition methods and tools . 101 5.2.8 G7: Knowledge analysis - conceptualize the domain ontology . 102 5.2.9 G8: Knowledge representation - implement the domain ontology . 102 5.2.10 G9: Evaluate, assess and verify the domain ontology . 103 5.2.11 G10: Use, maintain and manage the domain ontology . 104 5.3 Multi-tiered Domain Ontology Architecture . 105 5.3.1 Advantages of the Multi-tier Domain Ontology Architecture . 107 5.4 Dual Conceptual Representation . 108 5.4.1 UML for Conceptual Modeling and Ontology Representation . 110 6 Unified Semantic Procedural Pragmatic Design ::::::::::::::::::::: 113 6.1 Semantics, Procedures and Pragmatics . 115 6.2 Introducing the USP2 Design . 117 6.3 Verb Phrase Ontology . 119 6.4 Performative Verb Ontology . 122 6.5 Semantic Analysis Representations: Discovering Semantic Relationships . ..