Stefania Montani and Lakhmi C. Jain (Eds.) Successful Case-Based Reasoning Applications - 1
Studies in Computational Intelligence, Volume 305 Editor-in-Chief Prof. Janusz Kacprzyk Systems Research Institute Polish Academy of Sciences ul. Newelska 6 01-447 Warsaw Poland E-mail:
[email protected] Further volumes of this series can be found on our homepage: springer.com Vol. 283. Ngoc Thanh Nguyen, Radoslaw Katarzyniak, and Shyi-Ming Chen (Eds.) Advances in Intelligent Information and Database Systems, 2010 ISBN 978-3-642-12089-3 Vol. 284. Juan R. Gonz´alez, David Alejandro Pelta, Carlos Cruz, Germ´an Terrazas, and Natalio Krasnogor (Eds.) Nature Inspired Cooperative Strategies for Optimization (NICSO 2010), 2010 ISBN 978-3-642-12537-9 Vol. 285. Roberto Cipolla, Sebastiano Battiato, and Giovanni Maria Farinella (Eds.) Computer Vision, 2010 ISBN 978-3-642-12847-9
Vol. 294. Manuel F.M. Barros, Jorge M.C. Guilherme, and Nuno C.G. Horta Analog Circuits and Systems Optimization based on Evolutionary Computation Techniques, 2010 ISBN 978-3-642-12345-0 Vol. 295. Roger Lee (Ed.) Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing, 2010 ISBN 978-3-642-13264-3 Vol. 296. Roger Lee (Ed.) Software Engineering Research, Management and Applications, 2010 ISBN 978-3-642-13272-8 Vol. 297. Tania Tronco (Ed.) New Network Architectures, 2010 ISBN 978-3-642-13246-9
Vol. 286. Zeev Volkovich, Alexander Bolshoy, Valery Kirzhner, and Zeev Barzily Genome Clustering, 2010 ISBN 978-3-642-12951-3
Vol. 298. Adam Wierzbicki Trust and Fairness in Open, Distributed Systems, 2010 ISBN 978-3-642-13450-0
Vol. 287. Dan Schonfeld, Caifeng Shan, Dacheng Tao, and Liang Wang (Eds.) Video Search and Mining, 2010 ISBN 978-3-642-12899-8
Vol. 299. Vassil Sgurev, Mincho Hadjiski, and Janusz Kacprzyk (Eds.) Intelligent Systems: From Theory to Practice, 2010 ISBN 978-3-642-13427-2
Vol. 288. I-Hsien Ting, Hui-Ju Wu, Tien-Hwa Ho (Eds.) Mining and Analyzing Social Networks, 2010 ISBN 978-3-642-13421-0
Vol. 300. Baoding Liu (Ed.) Uncertainty Theory, 2010 ISBN 978-3-642-13958-1
Vol. 289. Anne H˚akansson, Ronald Hartung, and Ngoc Thanh Nguyen (Eds.) Agent and Multi-agent Technology for Internet and Enterprise Systems, 2010 ISBN 978-3-642-13525-5
Vol. 301. Giuliano Armano, Marco de Gemmis, Giovanni Semeraro, and Eloisa Vargiu (Eds.) Intelligent Information Access, 2010 ISBN 978-3-642-13999-4
Vol. 290. Weiliang Xu and John Bronlund Mastication Robots, 2010 ISBN 978-3-540-93902-3
Vol. 302. Bijaya Ketan Panigrahi, Ajith Abraham, and Swagatam Das (Eds.) Computational Intelligence in Power Engineering, 2010 ISBN 978-3-642-14012-9
Vol. 291. Shimon Whiteson Adaptive Representations for Reinforcement Learning, 2010 ISBN 978-3-642-13931-4 Vol. 292. Fabrice Guillet, Gilbert Ritschard, Henri Briand, Djamel A. Zighed (Eds.) Advances in Knowledge Discovery and Management, 2010 ISBN 978-3-642-00579-4 Vol. 293. Anthony Brabazon, Michael O’Neill, and Dietmar Maringer (Eds.) Natural Computing in Computational Finance, 2010 ISBN 978-3-642-13949-9
Vol. 303. Joachim Diederich, Cengiz Gunay, and James M. Hogan Recruitment Learning, 2010 ISBN 978-3-642-14027-3 Vol. 304. Anthony Finn and Lakhmi C. Jain (Eds.) Innovations in Defence Support Systems - 1, 2010 ISBN 978-3-642-14083-9 Vol. 305. Stefania Montani and Lakhmi C. Jain (Eds.) Successful Case-Based Reasoning Applications - 1, 2010 ISBN 978-3-642-14077-8
Stefania Montani and Lakhmi C. Jain (Eds.)
Successful Case-Based Reasoning Applications - 1
123
Prof. Stefania Montani Dipartimento di Informatica Universita’ del Piemonte Orientale Viale Michel 11 15100 Alessandria Italy E-mail:
[email protected]
Prof. Lakhmi C. Jain Professor of Knowledge-Based Engineering Founding Director of the KES Centre School of Electrical and Information Engineering University of South Australia Adelaide Mawson Lakes Campus South Australia SA 5095 Australia E-mail:
[email protected]
ISBN 978-3-642-14077-8
e-ISBN 978-3-642-14078-5
DOI 10.1007/978-3-642-14078-5 Studies in Computational Intelligence
ISSN 1860-949X
Library of Congress Control Number: 2010929748 c 2010 Springer-Verlag Berlin Heidelberg This work is subject to copyright. All rights are reserved, whether the whole or part of the material is concerned, specifically the rights of translation, reprinting, reuse of illustrations, recitation, broadcasting, reproduction on microfilm or in any other way, and storage in data banks. Duplication of this publication or parts thereof is permitted only under the provisions of the German Copyright Law of September 9, 1965, in its current version, and permission for use must always be obtained from Springer. Violations are liable to prosecution under the German Copyright Law. The use of general descriptive names, registered names, trademarks, etc. in this publication does not imply, even in the absence of a specific statement, that such names are exempt from the relevant protective laws and regulations and therefore free for general use. Typeset & Cover Design: Scientific Publishing Services Pvt. Ltd., Chennai, India. Printed on acid-free paper 987654321 springer.com
Preface
Case-based reasoning (CBR) is an Artificial Intelligence (AI) technique to support the capability of reasoning and learning in advanced decision support systems. CBR exploits the specific knowledge collected on previously encountered and solved situations, which are known as cases. Thus, by using CBR, the difficulties of knowledge acquisition and of knowledge representation are often lessened. CBR research is now mature and very active, as testified by the large number of theoretical and applicative works that can be found in the literature. In this book, we have collected a selection of papers on very recent CBR applications. These, after an in-depth analysis of their specific application domain needs, propose proper methodological solutions and give encouraging evaluation results, which have in some cases led to the commercialization step. The collected contributions demonstrate the capability of CBR to solve or handle issues which would be too difficult to manage with other classical AI methods and techniques, such as rules or models. The heterogeneity of the involved application domains indicates the flexibility of CBR, and its applicability in all those fields where experiential knowledge is (readily) available. The book is directed to the application engineers, scientists, professors and students. We are grateful to the authors and reviewers for their vision and contribution. Thanks are due to the publisher for assistance during the preparation of the manuscript.
Stefania Montani Italy Lakhmi C. Jain Australia
Editors
Stefania Montani (PhD in Bioengineering and Medical Informatics 2001, University of Pavia, Italy) is an Assistant Professor in Computer Science, at the Computer Science Department of the University of Piemonte Orientale, Alessandria, Italy. Her research interests include Case-Based Reasoning, Decision Support Systems, Temporal Databases, Temporal Reasoning, and Dependability Analysis. She is author of more than 100 publications, all in international journals, books, or international refereed conferences. She is member of more than 10 program committees of international conferences in 2009/2010, and belongs to the reviewing boards of 3 international journals. In 2010 she will be the program chair of the International Conference on Case-Based Reasoning, further testifying her very active role in the Case-Based Reasoning research community.
Professor Lakhmi C. Jain is a Director/Founder of the Knowledge-Based Intelligent Engineering Systems (KES) Centre, located in the University of South Australia. He is a fellow of the Institution of Engineers Australia. His interests focus on the artificial intelligence paradigms and their applications in complex systems, art-science fusion, virtual systems, e-education, e-healthcare, unmanned air vehicles and intelligent agents.
Table of Contents
Chapter 1 Innovations in Case-Based Reasoning Applications . . . . . . . . . . . . . . . . Stefania Montani, Lakhmi C. Jain
1
Chapter 2 Case-Based Reasoning for Medical and Industrial Decision Support Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mobyen Uddin Ahmed, Shahina Begum, Erik Olsson, Ning Xiong, Peter Funk
7
Chapter 3 Development of Industrial Knowledge Management Applications with Case-Based Reasoning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mehmet H. G¨ oker, Catherine Baudin, Michel Manago Chapter 4 Case Based Reasoning for Supporting Strategy Decision Making in Small and Medium Enterprises . . . . . . . . . . . . . . . . . . . . . . . . Jerzy Surma Chapter 5 Heterogeneity in Ontological CBR Systems . . . . . . . . . . . . . . . . . . . . . . . Amjad Abou Assali, Dominique Lenne, Bruno Debray Chapter 6 The Adaptation Problem in Medical Case–Based Reasoning Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Rainer Schmidt and Olga Vorobieva Chapter 7 Prototype–Based Classification in Unbalanced Biomedical Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sara Colantonio, Suzanne Little, Ovidio Salvetti, Petra Perner
53
83
97
117
143
Chapter 8 Case–Based Ranking for Environmental Risk Assessment . . . . . . . . . . Paolo Avesani, Angelo Susi
165
Chapter 9 CookIIS – A Successful Recipe Advisor and Menu Creator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Alexandre Hanft, R´egis Newo, Kerstin Bach, Norman Ihle, Klaus-Dieter Althoff
187
Author Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
223
Chapter 1
Innovations in Case-Based Reasoning Applications Stefania Montani1 and Lakhmi C. Jain2 1 Dipartimento di Informatica Universita' del Piemonte Orientale Viale Michel 11 15100 Alessandria, Italy 2 University of South Australia Adelaide South Australia, SA 5095 Australia
Abstract. In this book, we have colleted a selection of papers on very recent Case-based reasoning (CBR) applications. Most of these propose interesting and unique methodological choices. The heterogeneity of the involved application domains indicates the flexibility of CBR, and its applicability in all those fields where experiential knowledge is (readily) available. The present chapter provides a brief introduction to CBR, for readers unfamiliar with the topic. It then summarizes the main research hints that will be analyzed in depth in the following chapters of this book.
1 Introduction Case-based reasoning (CBR) [Kolodner 1993, Aamodt 1994] is an Artificial Intelligence (AI) technique to support the capability of reasoning and learning in advanced decision support systems. Specifically it is a reasoning paradigm that exploits the specific knowledge collected on previously encountered and solved situations, which are known as cases. The reasoning process can be summarized using the following four basic steps. These are known as the CBR cycle (figure 1), or as the four ‘‘res’’ [Aamodt 1994]. The procedure is to: (1) retrieve the most similar case(s), with respect to the current input situation, contained in the case repository, which is known as the case base; (2) reuse them, or more precisely their solutions, in order to solve the new problem; (3) revise the proposed new solution (if it is considered necessary); (4) retain the current case for possible future problem solving. S. Montani & L.C. Jain (Eds.): Successful Case-Based Reasoning Appl., SCI 305, pp. 1–5. © Springer-Verlag Berlin Heidelberg 2010 springerlink.com
2
S. Montani and L.C. Jain
In many application domains it is also common to find CBR tools which are able to extract relevant knowledge, but leave the user the responsibility of providing an interpretation and of producing the final decision: steps Reuse and Revise are not implemented. In fact even retrieval alone may be able to significantly support the human decision making process [Watson 1997].
Fig. 1. The Case-based Reasoning Cycle (the picture is taken from [Aamodt 1994])
CBR is quite different from any other AI problem solving methodology - for example Bayesian Networks, Neural Networks, or Rule-Based Systems. That is because it does not aim to generalize from the examples. It keeps and exploits the specific instances of problems which have been collected in the past (almost) “as they are”. Cases represent an implicit form of knowledge, i.e. an unstructured, operative knowledge type, which is intended to be a store of past problem/solution patterns. In classical CBR no effort is made to extract more abstract information, that is there is no attempt to elicit rules or models from cases. By using CBR, the difficulties of knowledge acquisition and of knowledge representation are therefore often lessened. The new implicit knowledge generated by an organization/company can be automatically learnt, and stored in the case base by means of the Retain step, each day the organization operates. The case library then grows, and more and more representative examples can be retrieved. This makes it easier to find an appropriate solution to the present problem using this
Innovations in Case-Based Reasoning Applications
3
paradigm. This however implies that proper case base maintenance policies have to be defined. CBR basics are also considered in Chapter 2. The first publications on CBR appeared in the 80s. It is therefore a relatively “young” methodology. Nevertheless, CBR research has soon become very active, as testified by the large number of theoretical and applicative works. Theoretical works have ranged from the design of a similarity measures and of fast retrieval strategies by the use of memory organization [Wilson 1997, Bichindaritz 2008], to adaptation and revision techniques [Patterson 2002], and to case base maintenance [Leake 2001]. Applications have been proposed for use in several domains. These include legal reasoning [Elhadi 2001], health sciences [Jurisica 2004, Montani 2008], web services [Lorenzi 2005] and Ambient Intelligence [Deutsch 2008], citing only a few examples. We have selected 8 significant works on CBR applications, which testify to the flexibility and the practical advantages of this reasoning methodology. Details of the collected contributions are given in the next section.
2 Chapters Included in the Book In the following chapters, we present a selection of some very interesting CBR approaches, which are applied to a variety of application domains. In general, medical and industrial applications play a central role in the collected chapters. The rapidly growing amount of experience, and possible difficulties in generalizing of the available data in a strong domain theory, make CBR a very suitable methodology for aiding decision making in these areas. CBR resembles human reasoning, and allows to easily store experienced colleagues’ “know-how”, even in exceptional situations (e.g. [Surma 1995]). Moreover, proper methodological choices, such as the integration of CBR and other (AI) techniques, can enhance the performance of the resulting decision support system [Montani 2008]. These points are explored in Chapter 2, entitled “Case-Based Reasoning for Medical and Industrial Decision Support Systems” (Mobyen Uddin Ahmed, Shahina Begum, Erik Olsson, Ning Xiong and Peter Funk). In the chapter, the authors discuss the main features of medical and industrial CBR applications. Some specific tools and their development in these domains are also presented. The next three chapters broaden the issue of designing and implementing CBR systems in an industrial context. Chapter 3, entitled “Development of Industrial Knowledge Management Applications with Case-Based Reasoning” (Mehmet H. Göker, Catherine Baudin and Michel Manago), illustrates the main software engineering steps necessary for designing a CBR-based knowledge management industrial tool. The main potential problems and peculiarities of this application field are highlighted. Suggestions for solutions based on the authors’ own experience in business organizations are considered. Chapter 4, entitled “Case based Reasoning for Supporting Strategy Decision Making in Small and Medium Enterprises” (Jerzy Surma) deals with the definition of a CBR tool for use in an enterprise. In particular, it focuses on STRATEGOS, a tool which provides a CBR approach for supporting strategic management in areas of great decision complexity and uncertainty.
4
S. Montani and L.C. Jain
Chapter 5, entitled “Heterogeneity in Ontological CBR Systems” (Amjad Abou Assali, Dominique Lenne, and Bruno Debray) is more specifically related to a single industrial domain. It presents a knowledge-intensive CBR system used for diagnosing failures of gas sensors. From the methodological viewpoint, the system relies on ontological knowledge. This is also used for case retrieval, and takes into account the heterogeneity of case description. The focus then returns to healthcare applications, a domain in which CBR research is extremely active [Marling 2009]. In particular, Chapter 6, entitled “The Adaptation Problem in Medical Case-Based Reasoning Systems” (Rainer Schmidt and Olga Vorobieva) analyses different approaches of medical CBR systems to the adaptation and revision tasks. It exploits the great experience the authors have in the field to properly exemplify specific features and results. Chapter 7, entitled “A Prototype-Based Classification in Unbalanced Biomedical Problems” (Sara Colantonio, Suzanne Little, Ovidio Salvetti and Petra Perner) presents the evaluation results of a case-based classifier used on three data sets – one of which is medical data - compared with other classical approaches. The case-based classifier exploits feature selection and feature weighting to improve its performance. Finally, the last two chapters testify to the flexibility of CBR and to its suitability for use on a wide range of application domains. In particular Chapter 8, entitled “Case-Based Ranking for Environmental Risk Assessment” (Paolo Avesani and Angelo Susi), presents the use of a CBR approach to environmental surveillance. It introduces a case-based ranking methodology, and provides very encouraging experimental results in two different environmental risk assessment evaluations. On the other hand Chapter 9, entitled “CookIIS - a successful Recipe Advisor and Menu Creator” (Alexandre Hanft, Regis Newo, Kerstin Bach, Norman Ihle and Klaus-Dieter Althoff), reports on very interesting research issues, mainly dealing with adaptation and revision, afforded in a tool for suggesting cooking recipes as well as complete menus.
3 Conclusion This book collects a set of successful CBR approaches. These, after an in-depth analysis of their specific application domain needs, propose proper methodological solutions and give encouraging evaluation results, which have sometimes led to the commercialization step. The collected chapters exemplify how to build industry-focused and healthcare tools, which testifies how the CBR technology is not solely confined to academic research. They also demonstrate the capability of CBR to solve or handle issues which would be too difficult to manage with other classical AI methods and techniques, such as rules or models. This capability emerges very clearly in the health sciences. In conclusion, the heterogeneity of the involved application domains demonstrates the flexibility of CBR, and demonstrates its applicability as a decision support methodology in those fields where experiential knowledge can be easily (and possibly automatically) collected and reused.
Innovations in Case-Based Reasoning Applications
5
References [Aamodt 1994] Aamodt, A., Plaza, E.: Case-based reasoning: foundational issues, methodological variations and systems approaches. AI Commun. 7, 39–59 (1994) [Bichindaritz 2008] Bichindaritz, I.: Memory Structures and Organization in Case-Based Reasoning. Studies in Computational Intelligence, vol. 73, pp. 175–194. Springer, Heidelberg (2008) [Deutsch 2008] Deutsch, J., Manz, J., Schwarz, S., Cassens, J.: Third workshop on Case Based Reasoning and Context Awareness, European Conference on Case Based Reasoning (ECCBR), Trier (2008) [Elhadi 2001] Elhadi, M.T.: Using statutes-based IR drive legal CBR. Applied Artificial Intelligence 15(6), 587–600 (2001) [Jurisica 2004] Jurisica, I., Glasgow, J.: Applications of Case-Based Reasoning in Molecular Biology. AI Magazine 25(1), 85–95 (2004) [Kolodner 1993] Kolodner, J.L.: Case-based reasoning. Morgan Kaufmann, San Mateo (1993) [Leake 2001] Leake, D.B., Smyth, B., Wilson, D.C., Yang, Q. (eds): Special issue on maintaining case based reasoning systems. Comput. Intell. 17(2), 193–398 (2001) [Lorenzi 2005] Lorenzi, F., Ricci, F.: Case-based recommender systems: a unifying view. In: Mobasher, B., Anand, S. (eds.) ITWP 2003. LNCS (LNAI), vol. 3169, pp. 89–113. Springer, Heidelberg (2005) [Marling 2009] Marling, C., Montani, S.: Seventh workshop on Case Based Reasoning in the Health Sciences, International Conference on Case Based Reasoning (ICCBR), Seattle (2009) [Montani 2008] Montani, S.: Exploring new roles for case-based reasoning in heterogeneous AI systems for medical decision support. Applied Intelligence 28(3), 275–285 (2008) [Patterson 2002] Patterson, D., Rooney, N., Galushka, M.: A regression based adaptation strategy for case-based reasoning. In: Dechter, R., Kearns, M., Sutton, R. (eds.) Eighteenth National Conference on Artificial intelligence, Edmonton, Alberta, Canada, July 28 - August 01. American Association for Artificial Intelligence, pp. 87–92. Menlo Park, CA (2002) [Surma 1995] Surma, J., Vanhoof, K.: Integration rules and cases for the classification task. In: Veloso, M., Aamodt, A. (eds.) ICCBR 1995. LNCS, vol. 1010, pp. 325–334. Springer, Heidelberg (1995) [Watson 1997] Watson, I.: Applying case-based reasoning: techniques for enterprise systems. Morgan Kaufmann, San Mateo (1997) [Wilson 1997] Wilson, D.R., Martinez, T.R.: Improved heterogeneous distance functions. J. Artif. Intell. Res. 6, 1–34 (1997)
Chapter 2
Case-Based Reasoning for Medical and Industrial Decision Support Systems Mobyen Uddin Ahmed, Shahina Begum, Erik Olsson, Ning Xiong, and Peter Funk School of Innovation, Design and Engineering, Mälardalen University, P.O. Box 883 SE-721 23, Västerås, Sweden Tel.: +46 21 10 14 53, Fax: +46 21 10 14 60
[email protected] Abstract. The amount of medical and industrial experience and knowledge is rapidly growing and it is increasingly difficult to be up to date leading to less informed decisions, mistakes and serious accidents. The demand for decision support system (DSS) is especially important in domains where experience and knowledge grow rapidly. However, traditional approaches to DSS are not always easy to adapt to a flow of new experience and knowledge and may also show a limitation in areas with a weak domain theory. This chapter explores the functionalities of Case-Based Reasoning (CBR) to facilitate experience reuse both in clinical and in industrial decision making tasks. Examples from the field of stress medicine and condition monitoring in industrial robots are presented here to demonstrate that the same approach assists both clinical applications as well as decision support for engineers. In both domains, DSS deals with sensor signal data and integrate other artificial intelligence techniques into the CBR system to enhance performance in a number of different aspects. Textual information retrieval, Rule-Based Reasoning (RBR), and fuzzy logic are combined together with CBR to offer decision support to clinicians for a more reliable and efficient management of stress. Agent technology and wavelet transformations are applied with CBR to diagnose audible faults on industrial robots and to package such a system. The performance of the CBR systems have been validated and have shown to be useful in solving such problems in both of these domains.
1 Introduction Case-based reasoning (CBR) presents an emerging innovative technique to support the capability of learning and self-improvement in an advanced decision support system. The basic idea of CBR is to solve new problems by identifying and reusing previous similar cases based on the heuristic principle that similar problems have a high likelihood of having similar solutions. As specific cases are reused directly as reference for decision making under a query problem, CBR eases the knowledge acquisition bottleneck and facilitates learning from experiences without requiring extensive and detailed e and formalized domain. S. Montani & L.C. Jain (Eds.): Successful Case-Based Reasoning Appl., SCI 305, pp. 7–52. © Springer-Verlag Berlin Heidelberg 2010 springerlink.com
8
M.U. Ahmed et al.
Early case-based decision support systems were mainly related to situations depicted by a low number of symbolic attributes with discrete values. Nowadays, with the evolution of sensor and internet technologies, much richer data and information from heterogeneous sources are becoming available for utilization. Yet the data received are frequently continuous and subject to more complex properties such as being dynamic, sequential, unstructured, uncertain and imprecise. Proper treatment and interpretation of such large amounts of complex data are a key issue for the success of CBR systems in many practical scenarios in medical and industrial applications. This chapter is devoted to presenting our research efforts in developing CBR systems with complex data structure in technical domains (medicine and industry). One of our targets lies in time series case data generated from sensor signals. Unlike static case bases where objects are described by attributes which are time independent, a dynamic case may contain time series and time-varying variables in which pieces of data are associated with timestamp and are meaningful only for a specific segment in the case duration. Feature extraction is crucial to capture significant characteristics of the original signal for a concise case index usable in similarity matching and case retrieval. We discuss two different approaches (wavelet, statistical) to feature extraction in the following in combination with the industrial and medical application examples respectively. The second type of case data we tackle is unstructured textual format. We deem textual information an extra dimension in describing a subject of investigation in addition to the time series sensor readings. Recalling relevant textual cases from case base could provide valuable general knowledge which supplements specific case information in decision making. However, identifying relevant cases requires somehow different similarity metrics from those used in numerical CBR systems. For this purpose we will introduce a vector space model with cosine similarity in this chapter in association with medical decision support in stress management. Moreover, this chapter will also handle the issue of uncertain, imprecise data, as well as insufficient quantities of confirmed cases, which present common hindrances in many technical scenarios. We use the fuzzy technique as promising tool to alleviate such difficulty. Fuzzy similarity matching algorithm is presented to enable more robust matching results against impression of sensor readings. We also suggest employing fuzzy-rule based systems for creation of artificial cases to be injected into the case library if the real cases do not suffice. The organization of the chapter is as follows. Section 2 presents an overview of CBR as the core methodology used throughout the article. Then, in sections 3 and 4, we discuss the applications of CBR for decision support in medical and industrial domains respectively. Finally, concluding remarks and discussions are made in section 5.
2 Case-Based Reasoning (CBR) CBR is a problem solving method that gives priority to the past experiences for solving current problems (solutions for current problems can be found by reusing or adaptating the solutions to problems which had been solved in the past). Riesbeck & Schank presented CBR as, “A case-based reasoner solves new problems by adapting
Case-Based Reasoning for Medical and Industrial Decision Support Systems
9
solutions that were used to solve old problems” [26]. The CBR method in a problem solving context can be described as follows: 1) given a particular problem case, the similarity of a particular problem with the stored problems in a case library (or memory) is calculated 2) retrieve one or more most similar matching cases according to their similarity values 3) attempt to reuse the solution of one of the retrieved problems by doing revision or possible adaptation (if needed i.e. due to differences in problem descriptions) 4) finally, the current problem case and its corresponding solution can be retained as a new solved case for further use [25]. CBR is not only a powerful method for computer reasoning, but also a common human problem solving behavior in everyday life; that is reasoning is based on the past personally experienced cases. CBR is inspired by a cognitive model on a way how humans solves certain class of problems e.g. solve a new problem by applying previous experience adapted to the current situation. Watson and Marir have reported in [32] that CBR is attracting attention because: -
It does not require explicit domain knowledge but gathering of cases.
-
Simple and easy implementation because significant features describe a case.
-
Database management system or DBMS could help to handle a large volume of information.
-
Systems can easily learn by obtaining new knowledge as cases.
The roots of CBR can be traced from the work of Schank and his student at Yale University in the early 1980s but Watson presented in [32] that the origin of CBR is found in 1977. CYRUS [15], [16] developed by Janet Colodner, is the basic and earliest CBR system. She employed knowledge as cases and used an indexed memory structure. Other early CBR systems such as CASEY [18] and MEDIATOR [30] have implemented based on CYRUS. In the medical domain around 1980s, early CBR systems take place by Konton[18], and Braeiss[3],[4]. The medical domain is suitable and at the same time challenging for a CBR application. Doctors often recall similar cases that he/she has learned and adapt them to the current situation. A clinician may start his/her practice with some initial past experiences (own or learned solved cases), and attempt to utilize this past experience to solve a new problem which simultaneously increase his/her experience. One main reason that CBR is suitable for the medical domain is its adequate cognitive model and cases may be extracted from the patient’s records [11]. Several research works i.e. in [11], [8], and [23] have investigated the key advantages of CBR in the domain of health sciences. The motivations to apply CBR method in the medical domain are listed below: 1. The CBR [1], [36] method can solve a problem in a way similar to the normal behavior of human problem solving e.g. it solves a problem using experience. 2. Such a CBR system could be valuable for a less experienced person because the case library can be used as knowledge.
10
M.U. Ahmed et al.
3. A CBR system can start working with few reference cases in its case library and then learn day by day by adding new cases into the library. Similarly, a doctor or an engineer could start his/her practice with a few cases and gradually increase the experiences. 4. A CBR system can provide more than one alternative for a similar problem which is beneficial for the clinician. 5. CBR can help to reduce the recurrence of a wrong decision because the case library could contain both success and failure of cases. 6. Knowledge elicitation is most of the time a bottleneck in the health science domain since human behavior is not always predictable. The CBR method can overcome this because prediction is based on the experience or old cases. 7. It is useful if the domain is not clear enough i.e. CBR does not depend on any rules or any models [13]. 8. Systems using CBR can learn new knowledge by adding new solved cases into the case library, so domain knowledge is also updating in time. However, medical applications offer a number of challenges for CBR researchers and drive research advances in the area. Important research issues are: 1. A limited number of reference cases – even though a CBR system can work with a few number of reference cases, the performance might be reduced due to a limited number of available cases. 2. Feature extraction – cases are formulated with number of features or a feature vector, so the big issue is to dig out features from the complex data format (i.e. images, sensor signals etc). 3. Adaptation – the medical domain is often subject to complex knowledge and recommendation evolving with time, cases often consists of large number of features, and therefore it is a real challenge to apply knowledge discovery and automatic adaptation strategies in this area [10, 76]. 2.1 The CBR Cycle According to Kolodner in [17] a case is a “contextualized piece of knowledge representing experience that teaches a lesson fundamental to achieving the goals of the reasoner”. The most common and well known way is to present a case only with a problem and a solution description. The problem part describes the condition of a case and the solution part presents advice or recommendation to solve a problem. Some systems could also add an outcome besides the solution to evaluate a new state. The outcome describes the state after the case had been taken place [32]. A comprehensive case structure has been proposed by Kolodner in [17] as follows: 1) a state with goal, 2) the solution 3) the outcome 4) explanations of results and 5) lessons learned. Further ahead, Bergmann et al classified case
Case-Based Reasoning for Medical and Industrial Decision Support Systems
11
representation in the following three categories: a) feature vector representations or propositional cases b) structured representations or relational cases, and c) textual representations or semi-structure cases [7]. A schematic or a life cycle that presents the key processes involved in the CBR method is shown in Fig. 1 Aamodt and Plaza [1] have introduced a four-step model of CBR in a cyclical process comprising the four REs: Retrieve, Reuse, Revise and Retain.
Fig. 1. CBR cycle. The figure is introduced by Aamodt and Plaza [1].
Fig. 1 illustrates these four steps that present the key tasks to implement such kind of cognitive model. The current situation is formulated as a new problem case and matched against all the cases in library, depending on the similarity value of the cases one or more of the most similar cases are retrieved. Matching cases are presented with their corresponding solutions and a solution is then proposed to be reused and tested for success. If the retrieved case is not close enough to the new problem case, the solution will probably be revised and/or adapted. Finally, the new solved case retained into the case library with its solution. The steps are described below with the aspect of CBR in the medical domain. The major and most common part of a CBR system is the Retrieval step. It is essential since it plays a vital role for calculating the similarity of two cases. Given a description of a current situation, the retrieval algorithm computes the similarity value for all the cases in a case library and retrieves the most similar cases against the current problem. The similarity value between cases is usually represented as 0 to 1 or 0 to 100, where “0” means no matching and “1 or 100”
12
M.U. Ahmed et al.
means perfect matching. One of the most common and well known retrieval methods is the nearest neighbour (or kNN) [36], [29] which is based on the matching of a weighted sum of the features. For a feature vector, a local similarity is computed by comparing each feature value and a global similarity value is obtained as a weighted calculation of the local similarities. A standard equation for the nearest-neighbor calculation is illustrated in Eq 1. Similarity (T , S ) =
n
∑
i =1
f (Ti , S i ) × w i
(1)
n
∑ wi
i =1
In equation 1: T is the target case S is the source case n is the number of attributes in each case i is an individual attribute from 1 to n f is a similarity function for attribute i in cases T and S w is the importance for weighing of attribute i. The weights allocated to each feature/attribute provide them a range of importance. But determining the weight for a feature value is a problem and the easy way is to calibrate this weight by an expert or user in terms of the domain knowledge. However, it may also be determined by an adaptive learning process i.e. learning or optimizing weights from the case library as information source. Looking up from the classical CBR cycle in Fig. 1, the Reuse step comes just after the retrieve. This step is reusing one of the retrieved cases from the case library and returning it as the proposed solution for a current case. But in some cases, this phase can become more difficult, especially when there are notorious differences between the current case and the closest one retrieved. An adaptation of the obtained solution is required in order to give an accurate result. It calculates the differences between the retrieved case and the current case and then applies algorithms or rules that take the differences into account to suggest a solution. This adaptation could be done by an expert/user in the domain. The expert determines if it is a reasonable solution to the problem and he/she can modify the solution before approved. After that the case is sent to the Revise step where the solution is verified and evaluated for the correctness and presented as a confirmed solution to the new problem case [36]. The term Retain becomes the final stage which is functioning as a learning process in the CBR cycle, and it incorporating the new solved case into the case library for future use. The most common way to retain a case is to simply record the information concerning the target problem specification and its final solution (assuming that the solution given was accurate and correct) [25]. If the solution retrieved is not as reliable as it should be additional information might be stored into the case library such as the changes made to the retrieved solution. So, the information to be saved has to be considered carefully [24].
Case-Based Reasoning for Medical and Industrial Decision Support Systems
13
3 Medical Decision Support System: An Application in Stress Management Computer-based decision support systems (DSS) are designed to provide assistance in decision making tasks. Little has defined the term DSS as “a model-based set of procedures for processing data and judgments to assist a manager in his decision making” [34]. According to Shortliffe a medical DSS is “any computer program designed to help health professionals make clinical decisions [33].” The early AI systems for medical decision making emerged around the 1950’s mainly built using decision trees or truth tables. After that, different methods or algorithms have been introduced to implement medical decision support systems such as, Bayesian statistics, decision-analytical models, symbolic reasoning, neuralnetworks, rule-based reasoning, fuzzy logic, case-based reasoning etc. Since the implementation of MYCIN [35] many of the early AI systems attempted to apply rule-based systems in developing computer based diagnosis systems. However, for a broad and complex medical domain the effort of applying rule-based system has encountered several problems. Some of the preliminary criteria for implementing a rule-based system are that the problem domain should be well understood, constant over time and the domain theory should be strong [36]. In psychophysiology, the diagnosis of stress is so difficult that even an experienced clinician might have difficulty in expressing his knowledge explicitly. Large individual variations and the absence of general rules make it difficult to diagnose stress and predict the risk of stress-related health problems. On the other hand, case-based reasoning (CBR) works well in such domains where the domain knowledge is not clear enough i.e. weak domain theory. Furthermore, CBR systems can learn automatically which is very important as the medical domain is evolving with time. Rule-based systems cannot learn automatically as new rules are usually inserted manually. Statistical techniques are also applied successfully in medical systems. But to apply statistical models a large amount of data is required to investigate a hypothesis which is also not available in our application domain. The contribution of this chapter is twofold: first, is to assist in the diagnosis of stress on the basis of an individual patient data and the second, is to aid in the individual treatment procedure. 3.1 Stress According to Hans Selye, stress can be defined as “the rate of wear and tear within the body” [21]. He first introduced the term ‘stress’ in the 1950s when he noticed that patients suffer physically not only as a result of a disease or medical condition. He defined stress as "non-specific response of the body to any demand" [28]. People have an inborn reaction to stressful situations called the “fight or flight” response. We can react to certain events or facts that may produce stress and as a result our body’s nervous system activates and stress hormones are released to protect us. The human nervous system is divided into two main parts, the voluntary system and autonomic system. The automatic nervous system is further divided into sympathetic and parasympathetic nervous system. Walter Cannon described in [9], that the Sympathetic Nervous System (SNS) activates the body for the “fight or
14
M.U. Ahmed et al.
flight” response to perceived threats to physical or emotional security. Thus the SNS works to protect our body against threats by stimulating the necessary glands (i.e. thyroid and adrenal glands) and organs. It decreases the blood flow to the digestive and eliminative organs (i.e. the intestine, liver, kidney etc.) and enhances the flow of blood to the brain and muscles. The thyroid and adrenal glands also supply extra energy. As a result it speeds up the heart rate, increases blood pressure, decreases digestion and constricts the blood vessels i.e. vasoconstriction which slows down the flow of blood etc. The SNS thus activates the body for the fight-or-flight response to stress. The parasympathetic nervous system counteracts the fight-or-flight response to return the body to its normal state. It stimulates digestion, the immune system and eliminative organs etc. to rebuild the body [19]. Stress Diagnosis and Treatment. The diagnosis of stress is often multi-factorial, complex and uncertain due to large variations and personalization. According to [27], there are three methods that can be used for the diagnosis of stress: questionnaires, biochemical measures and physiological measures. A face-to-face interview with questionnaires and a checklist are quit traditional way to diagnose stress. Rudolf E. Noble in [27], mentioned various biochemical parameters e.g., corticosteroid hormone which can be measured from the body fluids, blood, saliva and urine. Since the autonomic nervous system is activated with stress response various physiological parameters of the SNS can be used in the diagnosis of stress. The physiological parameters are commonly measured using skin conductance, skin temperature, respiration e.g. end-tidal carbon dioxide (ETCO2), electromyography (EMG), electrocardiography (ECG), heart rate e.g. calculating respiratory sinus arrhythmia (RSA) and heart rate variability (HRV), electroencephalography (EEG), brain imaging techniques, oculomotor and pupilometric measures etc. In this research, stress diagnosis has been conducted using the skin temperature i.e. finger temperature (FT). There are several methods to control or manage stress e.g. exercise or training. In our everyday life we need to control our stress often in many situations for instance, when we are sitting at our desk or behind the wheel getting stuck in traffic. In such a situation or in other environments, biofeedback training is an effective method for controlling stress. It is an area of growing interest in medicine and psychology and it has proven to be very efficient for a number of physical, psychological and psychophysical problems [2], [20]. Experienced clinicians often achieved good results in these areas and their success largely based on many years of experiences and often thousands of treated patients. The basis of biofeedback therapy is to support a patient in realizing their self ability to control specific psychophysiological processes [14]. The general strategy is that, patients get a feedback in a clear way (e.g. the patient observes some measurements visualizing some physical processes in their body) and behaviorally train the body and/or mind to change the biological responses to improve the condition. Sensor-based biofeedback is drawing increasing attention and one reason is the development of sensors able to measure processes in the body previously not able to be measured. An area where biofeedback has proven to give results is the area of practicing relaxation. There is a correlation between skin temperature and relaxation. The changes in skin temperature reflect the state of the peripheral blood vessels which in turn are controlled by the SNS. A biological significant decrease in the SNS
Case-Based Reasoning for Medical and Industrial Decision Support Systems
15
i.e. relaxation activity results in an increased diameter in the peripheral blood vessels. This increase in the peripheral blood vessels in turn results in an increased blood flow and skin temperature. Therefore, FT measurement is an effective biofeedback parameter [12], [22] for self regulation training and has a clinical consensus as an important parameter in stress treatment. This research also investigates biofeedback training by employing FT measurements for stress control. 3.2 CBR System for Stress Diagnosis and Treatment The system consists of a thermistor, sensing the finger temperature. . The sensor is attached to the finger of a subject and connected to an electronic circuit that is connected to the USB-port on a computer [37]. Music is played to assist the subject to relax and instructions are given on how to control breathing. A calibration phase [6] helps to establish an individual stress profile and is used as a standard protocol in the clinical environment. For calibration purposes the finger temperature is measured during different conditions in 6 steps (baseline, deep breath, verbal stress, relax, math stress, relax).
Fig. 2. User interface to measure FT through the calibration phase
Fig. 2 demonstrates the user interface to collect FT measurements during the different test conditions. A number of individual parameters are identified to establish an individual stress profile. The baseline indicates the representative level for the individual when he/she is neither under intense stress nor in a relaxed state. The clinician asks the subject to read a neutral text during this step. The clinician not only identifies an individual’s base finger temperature, but also notes fluctuations and other effects, e.g. disturbances in the environment or observes the subject’s behavior. In the step ‘Deep-breath’, the subject breaths deeply which
16
M.U. Ahmed et al.
under guidance normally causes a relaxed state. How quickly changes in temperature occur during this step is relevant and recorded together with observed fluctuations. The step ‘Verbal-stress’ is initiated by asking the subject to tell about some stressful event they experienced in life. During the second half of this step the subject thinks about some negative stressful events in their life. In the ‘Relax step’, the subject is instructed to think of something positive, either a moment in life when they were very happy or a future event they look forward to experiencing. The ‘Math-stress’ step tests the subject’s reaction to directly induced stress by the clinician where the subject is requested to count backwards. Finally, the ‘relaxation step’ tests if and how quickly the subject recovers from stress. [57]. Fig. 3 illustrates an example of the FT changes during the calibration phase.
Fig. 3. Variations of the finger temperature measurements during the six steps. It shows one person with typical response before (low temperature level) and after lunch (high temperature level).
It can be observed from the figure that in general, finger temperature decreases when a person is stressed and increases during relaxation or in a non-stressed situation. This relates to mainly sympathetic intervention of the alpha-receptor in the vascular bed. When relaxation occurs, activity of the sympathetic nervous system decreases as well as the intervention of the alpha receptors, which leads to increased dilation of the blood vessels which increases blood flow and temperature. Stress responses are different for different people and so are the coping capabilities. An individual’s capability to cope with stress is also important to identify when measuring stress levels. A patient can be classified depending on their stress reaction and recovery capacity. The proposed computer-based stress diagnosis system uses CBR to assist in the diagnostic and/or classification tasks. It works in several steps to diagnose individual sensitivity to stress as shown in Fig. 4. The proposed system takes the FT measurement as an input. Then, it identifies the essential features and
Case-Based Reasoning for Medical and Industrial Decision Support Systems
FT sensor signal measurement
Feature mining from the FT sensor signal to formulate a new case
Case-based reasoning cycle to diagnosis stress
17
Diagnosis of individual sensitivity to stress
Fig. 4. Schematic diagram of the steps in stress diagnosis
formulates a new problem case with the extracted features in a vector. This new problem case is then fed into the CBR cycle to retrieve the most similar cases. Finally, the best matched case is presented to diagnosis individual sensitivity to stress. Feature extraction from the FT signal. To determine features the system uses 15 minutes measurements (time, temperature) in 3600 samples. It was observed, neither the mean value nor the standard deviation of the FT measurement was adequate indicators of stress. For example, consider two signals: one is increasing from 20° C to 30° C, the other decreasing from 30° C to 20° C. Although both signals have the same mean/standard deviation value in the duration, however they indicate opposite stress levels. As an alternative way, we consider the mean of the slope value as a feasible feature to convey relation with stress. If the mean slope is sufficiently positive, it will be an indication of relax, otherwise an indication of stress. But if the mean slope is around zero, it shows a situation with high uncertainty for decision or weak decision. Together with clinicians we have agreed that the derivative of each step of the FT measurement (from calibration phase) is used to introduce “degree of changes” as an indication of FT changes. A low angle value, e.g. zero or close to zero indicates no change or a stable finger temperature. . A high positive angle value indicates rising temperature, while a negative angle, e.g. -20° indicates falling FT. Total signal, except the baseline, is divided into 12 parts with one minute time interval and 12 features (i.e. Step2_Part1, Step2_Part2, Step3_Part1, …, Step6_Part1, Step6_Part2) are extracted. The system thereafter formulates a new problem case combining these generated and other features namely start temperature, end temperature, minimum temperature, maximum temperature and difference between ceiling and floor. CBR to diagnose stress. CBR solves a new problem by applying previous experience adapted to the current situation [36]. Most of the CBR systems follow the reasoning cycle discussed in the earlier chapter with Retrieve, Reuse, Revise and Retain as shown in Fig. 1. A case represents a piece of knowledge and plays an important role in the reasoning process. This new problem case is then passed into the CBR cycle to retrieve the most similar cases. Here, the k-Nearest Neighbour (kNN) algorithm is applied for the retrieval of similar cases. The case (feature vector extracted for FT signal) in this system is matched using three different matching
18
M.U. Ahmed et al.
algorithms. A modified distance function uses Euclidean distance to calculate the distance between the features of two cases. Hence, all the symbolic features are converted into numeric values before calculating the distance. For example, for the feature ‘gender’, male is converted to one (1) and female is two (2). The function ‘similarity matrix’ is represented as a table where the similarity value between two features is determined by the domain expert. For example, the similarity between same genders is defined as 1 otherwise 0.5. In fuzzy similarity, a triangular membership function (mf) replaces the crisp value of the features for new and old cases with a membership grade of 1. In both cases, the width of the membership function is fuzzified by 50% on each side. Fuzzy intersection is applied between the two fuzzy sets to get a new fuzzy set which represents the overlapping area between them. Similarity between the old case and the new case is now calculated using equation 2 presented in the next sub-section (fuzzy similarity).
Fig. 5. The most similar cases are presented in a ranked list with their solutions
The system provides a matching outcome in a sorted list of best matching cases. Given a new case, it matches with all the other cases in a case base and ranked in a list as shown in Fig 5. The ranked list of the cases is presented on the basis of their similarity value and identified classes. Also the solution for a retrieved old case i.e. diagnosis and treatment recommendations, are displayed by the system. In addition, it shows the number of times each case is reviewed by an expert as well as the number of times each case solution is used to solve a new problem as a score of the case.
Case-Based Reasoning for Medical and Industrial Decision Support Systems
19
Fig. 6. Comparison between a new problem case and most similar cases
The user can see the detailed information of that case and a comparison between the new problem case and selected case. A screen shot of such information is presented in Fig 6. It provides a better visualization of the comparison of FT measurement between the new case and old case through a plotted line chart using the signals (see Fig 7). The user can apply different matching algorithms by selecting a specific method. The detailed matching information may assist the clinicians
20
M.U. Ahmed et al.
or users in determining if a solution is reusable or requires an adaptation to use it for a new situation. Examples from Fig. 5 to Fig. 7, describe the similarity matching of a current case (Case Id 43) with the previous cases (Case Id 15 and 23) in a ranked list. For the current case, the system establishes with 71.8% of reliability that the patient is under the Very stressed condition. Finally, as an output, the top matching case is displayed which provides the classification of the stress level for the diagnosis of individual sensitivity to stress.
Fig. 7. Comparison in FT measurements between a new problem case and old cases
The users can adapt the solution i.e. adjust a solution to the current problem case. This adaptation could be a combination of two solutions from the list of the retrieved and ranked cases. The clinician determines if it is a plausible solution to the problem and can modify the solution before approved. Then the case is sent to the revision step where the solution is verified manually for the correctness and presented as a confirmed solution to the new problem case. In the retention step, this new case with its verified solution is added to the case base as a new knowledge. CBR to biofeedback treatment. For the biofeedback treatment procedure a small cycle with several steps is considered [31] [55]. An illustration of this biofeedback cycle is shown in Fig. 8. Biofeedback often focused on the relaxation and how the patient can practice relaxation while observing the changes in skin temperature. The intention of the system is to enable a patient to train himself/herself without particular supervision.
Case-Based Reasoning for Medical and Industrial Decision Support Systems
Feature extraction from sensor signal to formulate new case
User
Patients instructed by the system to relax in biofeedback training
21
Case-Based reasoning cycle Evaluate the FT measurement Generate instructions Biofeedback treatment
Fig. 8. Schematic diagram of the steps in the biofeedback treatment cycle
In this cycle, a user (subject) connects a sensor with the finger and can see the changes of FT during several instructions in the relaxation training. The FT measurements are preformed in real time and every 2 minutes the system evaluates the last 2 minutes measurement and if necessary generates instructions for the patient. CBR cycle is applied for the biofeedback training in stress management; this training time is flexible, which means a patient can choose duration of the training between 6 minutes (as minimum) to 20 minutes (as maximum). Nevertheless, the system generates feedback with appropriate suggestions in every 2 minutes if necessary. Thus, for each individual, the biofeedback cases are formulated with a feature vector from the biomedical signal (i.e. with 2 minutes FT measurement) in the conditional part and suggestions for the relaxation in the solution part. A new biofeedback case is compared to previously solved cases applying the fuzzy similarity matching algorithm and displays the outcome as feedback. Here, the feedback is defined with a pair i.e. it presents evaluation of FT measurement and a recommendation for the next training. This generated feedback is then presented to the clinician as proposed solution. The clinician reviews the proposed cases and takes the final decision to suggest a treatment to a patient. Thus the system assists a clinician, as a second option, to improve patient’s physical and psychological condition. Fuzzy Logic for Similarity Matching in the CBR Retrieval. Fuzzy techniques are incorporated into our CBR system to better accommodate uncertainty in clinicians reasoning. Many crisp values from both the FT measurements and given by a clinician are known to have a possibility distribution often known by experts and used in their reasoning. We propose that this dimension and domain knowledge is represented by fuzzy similarity, a concept well received by clinical experts. Representation of a similarity value using a matrix [5] often shows a sharp distinction which may provide an unreliable solution in domains where it is known that these values are less exact. The fuzzy similarity matching reduces this sharp distinction and handles the underlying uncertainty existing in the reasoning process. Fuzzy Logic. Information can be incomplete, inconsistent, uncertain, or all of these three and it is often unsuitable for solving a problem. For example,” The motor is running really hot. Or Tom is a very tall guy.” Experts rely on common sense when they solve problems. To deal with such vague and uncertain information exact mathematical techniques are not sufficient, we need a technique that use a
22
M.U. Ahmed et al.
much closer concept of human thinking. Fuzzy logic is specifically designed to mathematically represent this uncertainty and vagueness. So, fuzzy logic is not a logic that is fuzzy, but a logic that is used to describe fuzziness. It is the theory of fuzzy sets, sets that calibrate vagueness. Moreover, it is a form of multi-valued logic with more than two truth values to deal with reasoning i.e. an approximate value rather than exact value. just opposite to the binary or crisp logic it handles the concept of ’Partially Truth’ i.e. the values between completely ’true’ and completely ’false’. The degree of truth for a statement can range between false (0) and true (1) and considers more than two truth values. Aristotle was the first to realize that logic based on “True” or “False” alone was not sufficient. Plato laid the foundation indicating that there was a third region (beyond True and False) [46]. The multi-valued logic was introduced by a Polish philosopher Jan Lukasiewicz in the 1930s. He introduced logic that extended the range of truth values to all real numbers in the interval between 0 and 1 [41], [42]. In 1965 Lotfi Zadeh a professor in the University of California at Berkley, published his famous paper “Fuzzy sets”. He extended the work on possibility theory into a formal system of mathematical logic, and introduced a new concept for applying natural language terms. This new logic for representing and manipulating the fuzzy terms is called fuzzy logic [39], [49]. The term “Fuzzy logic” derives from the fuzzy set theory or the theory of fuzzy sets. The fuzzy set theory has successfully been applied in handling uncertainties in various application domains [40] including the medical domain. The use of fuzzy logic in medical informatics has begun in the early 1970s.
Fig. 9. Binary or crisp logic representation for the season statement
Fig. 9 represents binary logic with a crisp boundary of 4 different seasons in Sweden; where the X-axis corresponds to the days according to the months of the year and the Y-axis represents a truth value zero or one. In binary logic, the function that relates to the value of a variable with the binary characteristics of a
Case-Based Reasoning for Medical and Industrial Decision Support Systems
23
judged statement is a ‘rectangular’ one. The output value for any input will always be ‘one’ i.e. only one season and ‘zero’ for the rest of the seasons. The crisp boundary of the season winter drawn at 31st March and 20th March is winter with the true value of one.
Fig. 10. Fuzzy logic representation of the season statement
In fuzzy logic the function can take any shape, as the season example illustrated with the Gaussian curve in Fig 10, here, the X-axis is the universe of discourse which shows the range of all possible days for each month in a year for an input and the Y-axis represents the degree of the membership function i.e. the fuzzy set of each season maps day values into a corresponding membership degree. In fuzzy logic, the truth of any statement becomes a matter of degree. Considering the 20th March as an input in the fuzzy system, it is winter with the degree of truth 0.78 and at the same time spring with the degree of membership 0.22. So, according to Zadeh “Fuzzy logic is determined as a set of mathematical principles for knowledge representation based on degrees of membership rather than on crisp membership of classical binary logic”. Fuzzy Similarity Matching. Different matching algorithms or measurements approaches can be applied to calculate the similarity between the feature values of a current case and the old case [71]. Fuzzy sets can be used as a similarity measurement technique in CBR systems [50], [51], [53]. A discussion about the relationship between the similarity concept and several other uncertainty formalisms including fuzzy sets can be found in [52]. Fuzzy CBR matches the cases in terms of degrees of similarities between attribute values of the previous cases and a new case instead of the traditional Boolean matching. One of the fuzzy similarity matching techniques [51] using equation 2 is described in Fig. 11 where m1, m2 and om is the area of each fuzzy set.
24
M.U. Ahmed et al.
sim(C f , S f ) = s f (m1, m2) = max(om/ m1, om/ m2)
(2)
Degrees of membership function
The similarity between the old cases and a new case is calculated using the overlapping areas between the two fuzzy values in their membership functions. Here m1 is the area of one attribute value with one membership function and m2 is associated with the second membership function and the overlapping area is denoted as om.
1
m2
m1 om 0 -16
-14
-12
-10
-8
-6
-4
-2
Feature values
Fig. 11. Fuzzy similarity using triangular membership functions
An example is shown in Fig. 11, the value of an attribute of a current and the old cases are -6.3 and -10.9 respectively. Here, the weight of the membership function (mf) is fuzzified with 50 % in each side. This fuzzification can be done by a trial and error process based on the application domain. For the current case, the input value -6.3 is represented with the mf grade of 1 and the lower and upper bounds -9.45 and -3.15 are represented with an mf of grade 0 (m2 triangle). For the old case the input -10.9 is represented with an mf grade of 1 and the lower and upper bounds -16.35 and -5.45 are represented with an mf grade of 0 (m1 triangle). From Fig. 11, the area of two triangles m1=5.45 and m2=3.15 are calculated by the equation of “area = (1/2) x base x height”. For om triangle, the area is 0.92 and the height is defined from the intersection point of the two triangles (m1 and m2). The local similarity for the attributes of the current and old cases is calculated by equation 2. Considering minimum in equation 2, the local similarity value is min (0.17, 0.29)=0.17 and for maximum the local similarity value is 0.29. If the mfs are considered as 100 % fuzzified then the minimum local similarity will be 0.34 and maximum will be 0.58. In this way a user can get an option for both the tuning of the mfs and choosing the min/max values for the similarity function depending on the requirements. When the overlapping areas become bigger, then the similarity between the two features will also increase, and for completely matched features similarity will be 1.
Case-Based Reasoning for Medical and Industrial Decision Support Systems
25
3.3 Textual Information Retrieval in Stress Management Unlike measurement-based experience, human perceptions are usually expressed in an informal and natural language format, but they are proved important information for diagnosis [75]. Furthermore, contextual awareness is essential for decision support in diagnostics and treatment plans in the medical domain which is often conveyed in relevant notes or reports. Therefore, capturing perception-based experience coming from human observations and feelings and utilizing contextual awareness in a medical CBR system can provide more reliable and effective experience reuse. In fact, when diagnosing an individual stress level, clinicians also consider other factors such as a patient feelings, behavior, social facts, working environment and lifestyle. Such information can be presented by a patient using a natural text format and a visual analogue scale. Thus, the textual data of patients capture important indications not contained in measurements and also provide useful supplementary information. Therefore, the system adds textual features in a case vector which helps to better interpret and understand the sensor readings and transfer valuable experience between clinicians [61]. To enable similarity matching on less structured cases containing text, this research contributes with a proposal which combines cosine similarity with synonyms and ontology. Textual case retrieval could be defined as matching a user query against a bunch of free-text cases. Text retrieval is a branch of information retrieval (IR) if the information is stored in the form of text. IR is a science used for searching documents and/or for information within a document or metadata about the document. In this research the knowledge of IR is applied where the term “document” is converted as a “case”. The idea of this process begins when a query is entered by a user into the system through a user interface. Then the system extracts information from the query. The extracted features may match with several objects (cases) in the collection (case library) with different degree of relevance. The degree of relevance can be computed by the system as a numerical value that shows how well each case is matched with the query. Finally, according to this numerical value, all the cases will be sorted and the top ranked cases will be presented to the user [47]. According to wiki, there are several ways to find a match between a user query and the stored cases, such as Boolean model, fuzzy retrieval, vector space model, binary retrieval etc [47]. The vector space model (VSM) [43] is the most common and well know method that has been using in information retrieval. VSM or term vector model is an algebraic model that represents textual cases in a vector of terms. It identifies similarity between a query case Q and the stored cases Ci. One of the best known schemes is the tf-idf (term frequency – inverse document frequency) [44] weighting used together with cosine similarity [45] in the vector space model [43] where the word “document” is treated as a case. The tf-idf is a traditional weighting algorithm and often used in information and/or textual retrieval. The similarity/relevancy is measured from the cosine angle between a query case Q and the stored cases Ci inside a vector i.e. a deviation of angles between the case vectors. “ cos θ = Q.C i ” is a general equation to Q Ci
26
M.U. Ahmed et al.
calculate the cosine similarity where Q.Ci is the dot product and Q C i is the magnitude of the vectors (a query and the stored case), i is the index of the cases in the case library. The value of the similarity lies in the range of -1 to +1, where 1 means no matching and +1 means exactly the same. In terms of IR, the cosine similarity of two cases will range from 0 to 1, since the tf-idf weights cannot be negative. The final result 1 is a full match and 0 means no words match between Q and Ci. To measure the similarity we need two things, the weight of each term in each case and the cosine similarity between the cases inside a vector space. The terms are words, keywords, or long phrases in a case and the dimension of the vector is the number or frequency of each term in the vocabulary of cases. If a term occurs in a case the value will be non-zero in the vector. Each word tf is the relative frequency of the word in a specific case (document represent as a case) and it presents the importance of the word inside the case. idf is the inverse proportion of the word over the whole case corpus which presents the importance of the word over the entire case pool. The weight vector for a case c is T V c = [w1,c , w 2 , c ,..., w N ,c ] and
w
t ,c
= tf
t
. log
C
where tft is the term
{t ∈ c}
frequency or the number of times a term/word t occurs in a case c and is the inverse case frequency. The symbol “ C ” is the total number C log
{t ∈ c}
of cases in the case library and { t ∈ c } is the number of the cases containing the term t i.e. case frequency. Advantages, limitations and improvements. The number of advantages of this model that attracts to use it in textual retrieval is summarized below: 1.
VSM represents both the query and the stored cases in a weight vector where weights are non-binary and terms are weighted by importance.
2.
Stored cases can be ranked according to their similarity value.
3.
Retrieval can be done with partial matching that is cases can be retrieved even if they don’t contain a query keyword.
4.
It is simple to compute
Even though VSM is an easy and well known method in text retrieval, there are a number of limitations. According to Wikipedia the limitations are as below: 1.
When the information in a document or case is very long, a similarity measure is difficult or poor because of a high dimensional vector with small dot product.
2.
Keywords from the user query must exactly be matched with the keywords from the stored documents/cases, so prefix/suffix word or parsing can affect the similarity results.
Case-Based Reasoning for Medical and Industrial Decision Support Systems
27
3.
A similar information/context can contain both in a query and the stored cases using different words (for example synonym of words) may result in poor dot product.
4.
The order of each word/term that appears in the document/case is lost in the vector during the representation.
In terms of time complexity VSM also has couple of limitations, they are as follows: 1.
From the computational point of view it requires a lot of processing time.
2.
During adding a new case or a new term into the case library or term space, all vectors need to be recalculated.
Most of the limitations discussed above have been overcome by improving the model presented in [61]. A short summary is as follows: 1.
Stored cases are formulated and retained by a human expert; only essential information is used and the cases are not very large.
2.
Extracted number of significant keywords represented a stored case, so the cases are not containing high dimensional term vectors.
3.
Removal of all the less significant and common words such as "a", “an”, “the”, "in", "of", etc named as stopwords.
4.
Stemmed necessary terms to their root or basic form i.e. suffix/prefix the words such as "stemmer", "stemming", "stemmed" as based on "stem".
5.
Added a dictionary such as “WorldNet” to get semantic relation among the words that is synonyms of the words.
6.
Altered the term vector using expert defined domain specific ontology. The domain specific ontology provides relational strength among the special words in the domain to identify similarity between cases in similar context.
7.
Used a user defined similarity threshold or select a number of retrieved cases, so that the only relevant cases can be retrieved.
8.
The implemented system uses several services to update the case library in time such as during adding a case and/or altering the ontology. All the calculations i.e. weighting and re-weighting terms are performed offline and stored into the case library. As a result less computational time is required.
3.4 Fuzzy Rule-Based Classification into CBR The composition of a case library is one of the key factors that decide the ultimate performance of a CBR system. The cases stored in the case library should be both representative and comprehensive to cover a wide spectrum of possible situations. One of the limitations in CBR is that it depends on the case library; enough cases in a case library gives better result (with the purpose of accuracy) otherwise it may reduce the performance due to the lack of knowledge. Initially, when a system starts only with a small number of cases the performance could be reduced so an algorithm
28
M.U. Ahmed et al.
that automatically classifies new cases would be valuable. A fuzzy rule-based reasoning is introduced into the CBR system to initiate the case library with artificial cases providing an improved performance in the stress diagnosis task [67]. Fuzzy Rule-Based Reasoning (FRBR). It is a combination of fuzzy logic approach with traditional rule-based reasoning (RBR) which also called as fuzzy inference system (FIS). Fuzzy inference is a computer paradigm based on fuzzy set theory, fuzzy if-then-rules and fuzzy reasoning. A traditional RBR system contains a bunch of if-then rules in crisp format. A general form of a rule is “If
then “and in term of crisp example “If speed is > 100 then stopping distance is 100 meter”. In 1973, Lotfi Zadeh outlined a new approach to analyze the complex systems, in which he suggests to capture human knowledge in fuzzy rules [48]. A fuzzy rule is a linguistic expression of causal dependencies between linguistic variables in the form of the ‘if-then’ conditional statement, considering the previous example in fuzzy format “If speed is fast then stopping distance is long”. Here the term ‘speed’ and ‘distance’ are linguistic variables, ‘fast’ and ‘long’ are linguistic values determined by the fuzzy sets, ‘speed is fast’ as antecedent and ‘stopping distance is long’ as consequent.
Crisp input
Fuzzyfication Interface
Rule evaluation
Fuzzy Rule base
Fuzzy Inference Engine
Aggrigation
Defuzzyfication
Crisp output as a result
Fig. 12. The steps in a fuzzy inference system
Fuzzy decision making or inference system can be defined as a process of mapping a given input to an output with the help of the fuzzy set theory i.e. fuzzyfication → fuzzy reasoning → defuzzification [40]. Well known inference systems are the Mamdani-style and Sugeno-style but both of them perform the 4 steps process as described in Fig 12. It illustrates the steps of a fuzzy inference system for the Mamdani-style. As can be seen from the figure, the first step is the fuzzification of an input variable i.e. crisp input is fuzzified against the appropriate fuzzy sets. Given an input in crisp format, step1 computes the membership degree with respect to its linguistic terms. Consequently, each input variable is fuzzified over all the membership functions (mfs) used by the fuzzy rules. In traditional rule-based system, if the antecedent part of a rule is true then the consequent part is also true. But in a fuzzy system, the rules fire to some extent. If the antecedent is true to some degree of membership then the consequent is also true to that degree. Step2 is the rule evaluation where it takes fuzzyfied inputs and applies them to the antecedent part of the fuzzy rules. So it compares facts with the antecedents of the fuzzy rules to find degrees of compatibility.
Case-Based Reasoning for Medical and Industrial Decision Support Systems
29
The value or firing strength is a single number from each rules represented in the result of the antecedent evaluation. This number is then applied to generate consequent mfs. Aggregation in step3 is the process that merges all the output mfs for all the rules i.e. all outputs are combined into a single fuzzy set. The last and final phase (step4) in the inference process is the defuzzification that determines a crisp value from the output membership function as a solution. The input for the defuzzification is the aggregated fuzzy set and the output is a single number.
A’
A1
B’
B1 C1 W1
X
Y
R1
Z
A’
A2
B’
B2
C2 W2
X A’
Y Z B’
X
R2
C’
Y
AND (min)
Z
Fig. 13. Graphical representation of an example of fuzzy inference
A simple example of the fuzzy inference with multiple rules and multiple antecedents is illustrated in Fig 13, the rules and inputs are as follows: Rule 1: if x is A1 and y is B1 then z is C1 and Rule 2: if x is A2 and y is B2 then z is C2; Inputs: x is A and y is B then z is C (?). First the inputted crisp values (A and B) are converted into the fuzzy sets A’ and B’. Then for the rule R1 and R2, A’ and B’ are fuzzified with the fuzzy sets A1, B1 and A2, B2. The dotted line in Fig.13 presents the clipped area of the membership functions in the antecedent part of the rules. As the rules contain multiple antecedents with AND operators, fuzzy intersection used to obtain a single number that represents the evaluation result for the antecedents. W1 and W2 are the evaluation results applied to the mfs of the consequent part of the rules. Upward and downward diagonal patterns in the fuzzy sets C1 and C2 show the firing strengths for the rules evaluation. After aggregation, the clipped fuzzy sets C1 and C2, and the new fuzzy set C’ are obtained. The defuzzification algorithm could convert these fuzzy sets into crisp values which is a single number that represents the final output.
30
M.U. Ahmed et al.
Fuzzy RBR to Create Artificial Cases. Fuzzy set theory and fuzzy logic are a highly suitable and applicable basis for developing the rule-based systems in medicine and has proven to be a powerful tool for decision support [74] for more structured domain knowledge. In this research, the rules used in the classification process limit the number of cases in the matching procedure. Furthermore, a sharp distinction in the classification of individual sensitivity to stress may lead to misclassification. The system overcomes the problem by introducing fuzzy rules in the classification scheme. Instead of sharp distinction everything in fuzzy logic appears as a matter of some degrees or degrees of truth.
FT sensor signal measurement
Feature extraction from the sensor signal and formulate generalized feature for the rules
Fuzzy Inference System (FIS) Artificial case with new classification
Inserted into the case library
Fig. 14. Steps to create artificial cases in a stress diagnosis system
Fuzzy rule-based reasoning to create artificial cases functions as follows: 1) A FT sensor signal is measured through the calibration phase presented in the earlier section, 2) Features are extracted from a sensor reading and formulated them into a generalized feature, 3) The generalized feature is then supplied into the fuzzy inference system (FIS) to classify a new case, 4) The output from the FIS is the new classification defined in a feature vector and, 5) Finally, this case is saved into the case library as an artificial case (See Fig. 14). The rules used in this classification process are defined by a domain expert and formulated with a generalized feature allowing the sensor signal abstraction. A detailed description of these steps is presented in [67].
Table 1. The rules for the fuzzy inference system
Fuzzy rules for the classification 1. 2. 3. 4. 5.
if Percentage_Negative_Slope is “VeryHigh” then Stress_Class is “VeryStress” if Percentage_Negative_Slope is “High” then Stress_Class is “Stress” if Percentage_Negative_Slope is “Medium” then Stress_Class is “Normal/Stable” if Percentage_Negative_Slope is “Low” then Stress_Class is “Relax” if Percentage_Negative_Slope is “VeryLow” then Stress_Class is “VeryRelax”
Case-Based Reasoning for Medical and Industrial Decision Support Systems
31
A single-input single-output Mamdani fuzzy model is implemented in which the percentage of a negative slope (feature) is considered as the input variable and the corresponding stress class as the output. The parameters of the IF–THEN rules (known as antecedents or premises in fuzzy modeling) define a fuzzy region of the input space, and the output parameters (known as consequent in fuzzy modeling) specify a corresponding output as shown in Table 1. The crisp rules of these fuzzy rules are available in [67]. Percentage_Negative_Slope and Stress_Condition are the linguistic variables with the universe of discourse {0, 100} and {1, 5} respectively. VeryHigh, High, Medium, Low and VeryLow are the linguistic values determined by the fuzzy sets “TriangleFuzzySet” on the universe of discourse of Percentage_Negative_slope. VeryStress, Stress, Normal/Stable, Relax and VeryRelax are the linguistic values determined by the fuzzy sets “SingletonFuzzySet” on the universe of discourse of Stress_Condition class. The basic structure of the fuzzy logic expert systems, commonly known as a fuzzy inference system (FIS) is shown in Fig. 15.
Fuzzy reasoning mechanism
Y
X Crisp values are fuzzified
Membership function (mf)
Set of If-then rules
Fuzzy set is defuzzifier Aggregator
Fig. 15. A block diagram of a fuzzy inference system [30]
A rule-based system consisting of three conceptual components: a rule base that consists of a collection of fuzzy IF–THEN rules; a database that defines the membership functions (mf) used in the fuzzy rules; and a reasoning mechanism that combines these rules into a mapping routine from the inputs to the outputs of a system to derive a reasonable conclusion as output. X is the crisp value inputted for the fuzzificaiton. The fuzzy reasoning mechanism takes the fuzzyfied inputs and applies them to the antecedent part of the fuzzy rules. The value or firing strength from each rule represents the result of the evaluation for the antecedent. Afterthat this number is applied to generate the consequent mfs. All the output mfs are combined into a single fuzzy set through the aggregator. Finally, defuzzification determines a crisp value from the output membership function as the solution which is Y. 3.5 Experimental Work The performance of the system in terms of accuracy has been compared with experts in the domain, where the main goal is to see how close the system could work compared to an expert. The initial case base comprised of 53 FT measurements as reference cases from 31 subjects. Eight (8) women and twentythree (23) men between the age ranges of 24 to 54 participated in the study. The cases, in their conditional or problem description part, contain a vector with the
32
M.U. Ahmed et al.
extracted features and the solution part comprised of expert’s defined classification as diagnosis. The levels of stress are classified by the expert into five classes ranging from 1 to 5 where 1=VeryStressed, 2=Stressed, 3=Normal/Stable, 4=Relaxed and 5=VeryRelaxed. Quantifying the diagnostic performance of the system. The goal of this experimental work is to compare the performance of the system’s diagnosis task to an expert. Here, the percentage of the correctly classified cases is calculated to investigate the accuracy of the system. In the case library, 20 cases are classified as stress-related disorder, among them 8 are classified as VeryStressed and 12 are as Stressed. For the evaluation, one case is taken out from the case library at a time and matched against the remaining cases. Then, the classification result provided by the system is evaluated by comparison to the expert’s classification. The evaluation results are presented in Table 2 and Table 3. Table 2. Comparison between the expert’s & system’s classification in VeryStressed class
CaseID
Expert’s classification
Case_001_009 VeryStressed Case_004_015 VeryStressed Case_004_023 VeryStressed Case_039_027 VeryStressed Case_039_004 VeryStressed Case_501_040 VeryStressed Case_101_042 VeryStressed Case_634_043 VeryStressed Correctly Classified Cases in VeryStressed class
System’s classification using Fuzzy Similarity VeryStressed VeryStressed VeryStressed Stressed VeryStressed VeryStressed VeryStressed VeryStressed 88%
Table 3. Comparison between the expert’s and system’s classification in Stressed class
CaseID
Expert’s classification
Case_789_017 Stressed Case_008_018 Stressed Case_007_022 Stressed Case_103_024 Stressed Case_873_028 Stressed Case_763_031 Stressed Case_876_032 Stressed Case_245_038 Stressed Case_345_046 Stressed Case_823_047 Stressed Case_780_053 Stressed Case_101_052 Stressed Correctly Classified Cases in Stressed class
System’s classification using Fuzzy Similarity Normal/Stable Stressed Stressed Stressed Relaxed Stressed VeryStressed Stressed Stressed Stressed Stressed Stressed 75%
Case-Based Reasoning for Medical and Industrial Decision Support Systems
33
In Table 2 and Table 3, the 2nd column presents the expert’s classification and the 3rd column shows the classification of the cases by the system. Here, the system uses a fuzzy similarity matching function as local similarity and kNN (k=1) is used to retrieve the similar cases i.e. the top most similar case is considered. For the group VeryStressed, the system classifies 88% correctly and for the Stressed group, the system correctly classifies cases with an average accuracy of 75% in comparison with the expert’s classification. Only one case (Case_039_027) is misclassified by the system among the 8 VeryStressed cases and three out of the twelve classes are misclassified in Stressed class. In total, 80% stress-related cases are correctly classified by the system. Table 4. The total distribution of correctly classified cases
Classification criteria
Values
Correctly classified cases in total
80%
Low false positive
5%
Low false negative
10%
Serious false negative
5%
Table 4 shows the total distribution of the classified cases, where 80% of the cases are classified correctly by the system. Among the 20% misclassified cases, 5% are ‘low false positive’ (i.e. the cases are one step over misclassified), 10% are ‘low false negative’ (i.e. the cases are one step under misclassified) and 5% are ‘serious false negative’ (i.e. the cases are two steps under misclassified). One example of a serious false negative can be seen in Table 3, case id Case_873_028, which is misclassified as Relaxed whereas the expert has classified it as Stressed. Similarly, an example of a low false positive case is id Case_876_032 which is misclassified as VeryStressed and the expert has classified the case as Stressed. System Performance vs. Trainee Clinicians. This experiment is designed to investigate how good the system can classify compared to the trainee clinicians. The main purpose is to explore whether the system can be useful to assist a trainee clinician in the classification tasks. An experienced clinician and two trainee clinicians are involved in this experiment. The accuracy of the system is computed using the statistics square of the correlation coefficient or Goodness-of-fit (R2) [38], absolute mean difference and percentage of the correctly classified cases. In this experiment, we have considered two test data sets where setA consists of 11 cases and setB with 14 cases. The cases are selected randomly and all the cases are approved by the experienced clinician. The cases for the setA and setB are classified by the two trainee clinicians who have less experience in this domain and about the system.
34
M.U. Ahmed et al.
Fig. 16. Comparison results between the system and trainee clinicians for test setA
From Fig.16 it can be seen that the system using the fuzzy similarity matching algorithm can classify correctly better than the trainee clinicians. Considering the setA with 11 cases, the system classifies 81% correctly and the trainee clinicians classify with an accuracy of 64% and 55% correctly. The obtained Goodness-of-fit (R2) value for the setA is 92% which is similar as the trainee clinicians R2 values i.e. 86% and 88%.
Fig. 17. Comparison results between the system and trainee clinicians for test setB
Case-Based Reasoning for Medical and Industrial Decision Support Systems
35
The percentage of the correctly classified cases by the system for the test setB is 79 whereas the trainee clinicians have succeeded to classify the cases with an accuracy of 57%. For the setB, the R2 value for the system is 0.83 while calculated R2 for the trainee clinicians are 0.80 and 0.81. The absolute mean difference or error rates for the classification of both the test sets are comparatively lower (0.18 and 0.28) than the trainee clinicians. It can be observed from Fig. 16 and Fig.17 that for both the test data sets (setA and setB) the system can perform better than the less-experienced\trainee clinicians. Thus a multi-model case-based DSS in stress management [62] could help to transfer experience to a less-experienced clinician or work as a second option for an experienced clinician.
4 Decision Support in Industrial Applications Experienced staffs acquire their experience during many years of practice and sometimes also through expensive mistakes. The acquired experience is difficult to preserve and transfer and it often gets lost if the corresponding personnel leave their job due to retirements etc. The proposed CBR approach to collect, preserve and reuse the available experience enables a large potential for time and cost savings, predictability and reduced risk in the daily work [73]. In this study we focus on agent-based technology and CBR. Intelligent agents offer a concept and framework enabling flexible interactions with agents, systems and humans. An agent may also have knowledge on what the engineers currently are working on and what knowledge they have in order to offer better support and identify relevant knowledge and experience e.g. past solved cases, documentations, PM’s, etc. CBR is an efficient method to identify past experience in the form of cases that may help to solve the current problem. Intelligent agents deploying CBR enable the agents to gain experience by collecting past solved cases, adapt them to current problem and context e.g. the experience level of the technician. By identifying similar situations, transfer relevant information and experience, and adapt these cases to the current situation will both transfer knowledge and help this decision process [72]. Some decisions can be made autonomously by the agent in critical situations if no technician is close by. CBR solutions may also reduce costs for technical support since technicians often need considerably less time the second time they encounter a similar problem. But even access to the case containing the solution to a similar problem saves often considerable time according to the technicians. 4.1 Intelligent Agents In this section we give a brief introduction to agents and also motivate why the agent concept is suitable for the domain of condition monitoring. There are a number of different definitions of agents, but the difference for practical
36
M.U. Ahmed et al.
applications are often less important, the definitions are often based on the fact that agent research often is application oriented and having a particular applications in mind may lead to slightly different definitions [59], [68] state that “an agent is anything that can be viewed as perceiving its environment through sensors and acting upon that environment through effectors”. A pure reactive system like a thermostat would meet this basic definition, but most definition also includes social skills (communication) and some “intelligent” behavior, e.g. ability to proactiveness, learning and predicting. An agent’s goals or desires may be to decrease maintenance costs without reducing reliability and life expectancy. Wooldridge and Jennings [70] define agents to be computer systems that have properties such as: − autonomy, − social abilities, and − reactivity and pro-activeness In the context of condition monitoring the agent perceives the environment through one or more sensors. Additional information about the environment may also be acquired through communication with other agents or systems (a system may be given an agent wrapper to enable uniform communication). An agent’s ability to influence its environment may in the context of condition monitoring be to operate a valve/switch or adjust a process. An action may also be to communicate with some other agents or human, e.g. a technician close by and ask for help to carry out some preventive or corrective needs. The Maintenance Agent. A maintenance agent is specialized in interpreting data from the device it is connected to. Fig. 18 presents the outline of a maintenance agent in its environment. The agent observes its environment through one or more sensors. Additional information about the environment may also be acquired through communication with other agents or systems.
Fig. 18. Outline of the Maintenance Agent in its environment
Case-Based Reasoning for Medical and Industrial Decision Support Systems
37
The agent may have some basic domain knowledge about when to bring the findings to the attention of a human and when to shut down a process. The agent also has social skills to communicate its findings. It may also ask for additional information to make a final decision and it has facilities to receive appropriate feedback [60] Handling groups of sensors with a dependency between measurements enabling sensor agents to collaborate and learn from experience, resulting in more reliable performance. Maintenance agents may also improve their performance, e.g. recalibrate sensors if needed, or determine if sensors are faulty. Similar sensors may also share experience enabling them to avoid repetition of similar failures or make estimates on their reliability. 4.2 Factors Affecting Decisions by Agents In an agent based approach a critical issue is the agent’s decision whether to take a certain action autonomously or to collaborate with humans (technician/economist) in problem solving. For this decision a number of factors have to be considered. Some of them are domain dependent and also dependent on the reasoning method applied by the agent, since different methods and techniques enable more or less informed decision making. CBR Systems have some desirable properties enabling an informed decision. These systems make reasoning in terms of similarity, confidence and usefulness. These are important for agents as well as humans during a decision making process. The most central measurement in CBR systems is similarity, i.e., how similar a previous case is to the current situation and also reflecting how well the previous solution can be reused in the current situation. Some adaptation of the solution may be needed. If all the symptoms and conditions are identical between the current situation and the case from the case library, the same solution can be reused without modifications. Otherwise, even if a good matching case is found, other factors may influence the decision and the agent may decide to either doing nothing or applying/adapting a solution case further down the similarity ranking list or apply multiple solutions. Other factors the agent may take into account to make an informed and final decision are given below. Some of the most central factors in the context of maintenance are (not given in priority order): 1.
How similar is the case to the current situation
2.
Track record of how successful the case was in the past
3.
The confidence in the case and its solution given a current situation
4.
The benefit of a case (how efficiently the solution solves the problem)
5.
The cost of implementing the solution correctly
38
M.U. Ahmed et al.
6.
The consequences/costs, short term/long term if the agent/human is idle by taking no action
7.
The consequences/costs if the proposed solution in the case is wrongly deployed
The track record of a case (factor 2) is important since a good matching case may have a less good track record and other statistics appearing against it. The confidence in a case (factor 3) may depend on the nature of the cases in the case library that are similar to the current situation. E.g. if there are many similar cases nearby the same solution, the confidence grows. But if there are surrounding cases with a very different solution, the confidence in the most similar case may be reduced. The benefit of a case (factor 4) may also have a large influence on which case is selected, e.g. one case may have a solution fixing the problem temporarily while other cases offer long term solution. Factor 5-7 are cost and risk related factors. They have a major influence on the selection of the final case and also if an expert should be included in the decision process. These factors should reflect company policy, current economical situation and also laws and regulations. An example would be that a specific well matching case is the best matching case, and there is a high confidence and success rate connected to the case, but the solution in the case increases the risk of hazardous leakage damaging the environment, and environmental regulations may forbid this and may give the company unacceptable negative publicity. It may be argued that some of these factors may be included into the case descriptions and similarity measurement, but since many of them change with time and are complex in themselves, we propose that for monitoring and diagnostic tasks in industry it may be an advantage and lead to reduced complexity if these factors are handled separately in the decision process or decision support process instead of completely integrating them into the CBR system. 4.3
Designing and Intelligence
Building
Agent-Based
Systems
Using
Artificial
In this section we give an example of an agent based maintenance system both able to perform corrective maintenance, preventive maintenance, and condition based maintenance (possibly with help of other agents and technicians). Agents are being implemented with a wide variety of different techniques; both using traditional software engineering methods and techniques such as object oriented programming and Artificial Intelligence methods and techniques such as Artificial Neural Networks or CBR. CBR [1] offers an alternative to implement intelligent diagnosis systems for real-world applications [64]. Motivated by the doctrine that similar situations lead to similar outcomes, CBR fits well to classify the current new sensor signals based on experiences of past categorizations. The main strength lies in the fact that it enables directly reusing concrete examples in history and consequently eases the knowledge acquisition bottleneck [1].
Case-Based Reasoning for Medical and Industrial Decision Support Systems
39
Fig. 19. An example of an agent based system using case-based reasoning
In Fig. 19 an example of an agent using CBR is shown. The Sensor signal is pre-processed compared with the case library based on domain dependent similarity matching; the best matching cases are adapted to the current situation and suggested as solution to a human. Fault Diagnosis System Based on Sensor Signals and CBR – A Case Study. Abnormality of industrial machines can be reflected by some key states during their operation. Using sensor technology it is possible to detect and measure the values of these system states and their profiles. We can then process and analyses the collected sensor signals in order to find out hidden symptoms. The received signals are processed by wavelet analysis [54] in order to filter out noise and at the same time to extract a group of related features that constitutes a reduced representation of the original signal. The derived feature vector is then compared with the known cases in the case library with its neighboring cases sorted out. The agent system can, based on the symptoms; reasons about the class of fault associated with the machine or make prediction about what potential problem is likely to occur in a near future. A general system structure for this purpose is illustrated in Fig. 20, which includes signal filtering, feature extraction, and pattern classifier as its important components.
40
M.U. Ahmed et al.
Fig. 20. Fault diagnosis based upon sensor signals
As a case study we applied the proposed approach to diagnosis of industrial robots manufactured by a large company in Sweden. The prototype system developed for this purpose is shown in Fig. 21. Sound signals are gathered from the robot to be tested via a microphone device and then transmitted to the computer for pre-processing. The pre-processing is tasked to filter out or remove unwanted noise as well as identify period in-formation from a sound profile. Subsequently sound features are extracted from the frequency domain and they are assembled into a feature vector as a condensed representation of the original sound signal. Classification of the feature vector is performed based upon previously classified sound descriptions in the case library. The experiments have shown that this system is able to successfully diagnose faults in an industrial robot based on a low number of previous examples. The system is able to successfully diagnose faults in an industrial robot based on sound recordings (6 recordings from faulty robots and 24 recordings from normal robots are used in the evaluation).
Fig. 21. Schematic of system logic
It is worth mentioning that the above prototype system has some similarities with the Open System Architecture for Condition Based Maintenance (OSA-CBM) [69]. That architecture suggests that a Condition Based Maintenance (CBM) system be divided into seven modules [56] including sensors; signal processing; condition monitoring, diagnosis, prognosis, decision support, and presentation. The system
Case-Based Reasoning for Medical and Industrial Decision Support Systems
41
Fig. 22. System transfer to OSA-CBM standard
presented here in this paper has microphone as sensor module and pre-processing & feature extraction steps as signal processing module in correspondence to the OSACBM architecture. In addition, the case-based classification in Fig. 21 also serves as a condition monitoring module by detecting and identifying deviations in sound profiles. Fig. 22 depicts the system transferred to OSA-CBM standard. Signal Pre-Processing and Feature Extraction. Sounds of robots in industrial environments typically contain unwanted noise. Signal pre-processing is used to purify the original signal by removing unwanted components such as noise and/or to enhance components related to the condition of the object such that more reliable diagnosis results will be warranted. Noise can be caused internally by various parts in the diagnosed object or externally by disturbance from surroundings which are added to the sensor data received. Feature extraction is purported to identify characteristics of the sensor signals as useful symptoms for further analysis. This stage is critical for fault diagnosis in many industrial applications. In order to supply the pattern classifier with a moderate number of inputs for effective analysis and reasoning, representative features from the sensor signals have to be extracted. Algorithms used for classification can easily be misguided if presented with data of to high dimension. E.g. the k-nearest neighbor algorithm which is often used for case-based classification performs best on smaller dimensions with less than 20 attributes [63]. We deal with signal preprocessing and feature extraction by applying wavelet analysis [54]. The Wavelet theory is a further development of the Fourier theory. The Fourier theory says that a periodic signal can be expressed as a sum of a, possibly infinite, series of sine and cosines. As an example, the tone of an instrument is a combination of its lowest frequency tone, called the fundamental frequency of the tone, and the higher-frequency ones, called overtones. The Fourier theory has the limitation that it cannot represent non-periodic signals. Periodic signals are signals that repeat itself over a period of time like, for example, the tone from an instrument. Nonperiodic signals are for example a speech sound. The word “grease” is not a periodic signal; it contains a mix of frequencies with sharp peaks and slopes. But the sound from a tuning fork is periodic. A periodic signal is said to be localized in frequency whereas a non-periodic signal is said to be localized in time.
42
M.U. Ahmed et al.
A wavelet has the advantage that it can do both, the wavelet package transform separates a wave into “time-frequency packets”. A wavelet consists of a basis function, the mother wavelet. It can be any function witch positive and negative areas cancel out. Wavelet transforms are popular in many engineering and computing fields for solving real-life application problems. Wavelets can model irregular data patterns, such as impulse sound elements better than the Fourier transform. In a related paper [65] we experimentally verified that, under certain circumstances of strong background noise, wavelet outperforms Fourier transform in supplying distinguishable feature vectors between different faults for casebased classification. The signal f (t ) will be represented as a weighted sum of the wavelets ψ (t ) and the scaling function ϕ (t ) by equation 3.
f (t ) = A1ϕ (t ) + A2ψ (t ) +
∑A
n∈+ Z , n∈Z
ψ ( 2 n t − m)
n ,m
(3)
where ψ (t ) is the mother wavelet and ϕ (t ) is the scaling function. In principle, a wavelet can be a function which positive and negative areas canceling out. That means a wavelet function has to meet the following condition (equation 4): ∞
∫ψ (t )dt = 0
(4)
−∞
Dilations and translations of the mother wavelet function define an orthogonal basis of the wavelets as expressed by equation 5 −s 2
ψ ( sl ) (t ) = 2 ψ (2 − s t − l ) where variables
ψ (t )
(5)
s and l are integers that scale and dilate the mother function
to generate other wavelets belonging to the Daubechies wavelet family. The
scale index s indicates the wavelet's width, and the location index l gives its position. The mother function is rescaled, or "dilated" by powers of two and translated by integers. To span the data domain at different resolutions, the analyzing wavelet is used in a scaling equation as following: (equation 6) N −2
ϕ (t ) = ∑ (−1) k c k +1ψ (2t + k )
(6)
k =1
where ϕ (t ) is the scaling function for the mother function ψ (t ) , and
c k are the
wavelet data values. The coefficients {c0 ,..., c n } can be seen as a filter. The filter or coefficients are placed in a transformation matrix, which is applied to a raw data vector (see Fig. 23). The coefficients are ordered using two dominant patterns, one works as a smoothing filter (like a moving average), and the other works to bring out the "detail" information from the data. The wavelet coefficient matrix is applied to the input data vector. The matrix is applied in a hierarchical
Case-Based Reasoning for Medical and Industrial Decision Support Systems
43
algorithm, sometimes called a pyramidal algorithm. The wavelet data values are arranged so that odd rows contain an ordering of wavelet data values that act as the smoothing filter, and the even rows contain an ordering of wavelet coefficients with different signs that act to bring out the data's detail. The matrix is first applied to the original, full-length vector. Fig. 23 shows an example of a data vector consisting of 8 samples. The samples can be any type of data; sensor signals from various process applications, stock market curves etc. In this paper the samples are acoustic signals from a gearbox of an industrial robot.
Fig. 23. Original signal consisting of 8 samples
The data vector is smoothed and decimated by half and the matrix is applied again (see Fig. 24).
Fig. 24. Smoothed data vectors
Then the smoothed, halved vector is smoothed, and halved again, and the matrix applied once more. This process continues until a trivial number of "smoothsmooth-smooth..." data remain (see Fig. 25).
Fig. 25. The result of the pyramidal algorithm
44
M.U. Ahmed et al.
This system uses the wavelet packet transform algorithm. It is a computer implementation of the Discrete Wavelet Transform (DWT). It uses the Daubecies mother wavelet, scaling function and wavelet coefficients [58]. The result of the pyramidal algorithm is a tree of smoothed data values (see Fig. 25). Each collection of smoothed data values (node in the tree) can be seen as a “time-frequencypacket”. Each “time-frequency-packet” can be seen as a filtered version of the original data samples. As an example, the left “packet” in Fig. 25 can be seen as a low pass filtered version of the original data and the right “packet” can be seen as a high pass filtered version of the original data. The leaves of the tree can be seen 0
as high and low pass units of length 2 . The depth of the tree is determined from n
the length of the input data. If the input data are of length 2 the depth of the tree will be n . A suitable collection of “time-frequency-packets” can be selected by taking a cross section of the tree at an arbitrary depth. Each sibling in the cross section of the tree is spanning the entire time of the original data set. This means that going deeper in the tree produces at better resolution in frequency but a poorer resolution in time. The best compromise between time and frequency resolution is to take a cross section in the tree were the length of each sibling is the same as the number of siblings in the cross section. At a given depth n and with original data size S , the length of a sibling (or leaf) is
S n and the number of siblings is 2 . 2n
The wavelet packet algorithm offers the basis for the pre-processing and feature extraction processes. The input signal is first divided into windows of discrete time steps. Each window is then passed to the wavelet packet algorithm resulting in a wavelet “packet tree” as pictured in Fig. 26. The wavelet data values from a cross section of the wavelet packet tree are then passed to the feature extraction process. Our system uses normalized wavelet data values as features. The values are selected from a cross-section of the wavelet packet tree. Gear defects often show their presence as sharp peaks or dips in the sound. Such peaks or dips can be spotted in some dominant wavelet data values in certain packets in the cross section of
Fig. 26. Feature identification from wavelet data values
Case-Based Reasoning for Medical and Industrial Decision Support Systems
45
the wavelet packet tree. The feature extraction component examines the wavelet data values and extracts one dominant value from each packet in a cross section at an arbitrary depth. In Fig. 26 the grey area shows a cross section at level 2 in the tree. The chosen coefficients are those that are marked as bold. They are chosen because they are the dominant values in each packet in that cross section. Frequency-based features characterize sensor signals according to their amplitudes under significant frequencies. As many fundamental signal analysis methods are available to yield frequency spectra, we seem to have more solid basis for extracting features based on frequency than for deriving time-based features. We thus adopt frequency-based features as descriptors of condition parts of cases in our research. Generally a vector of frequency-based features is formulated as in equation 7.
FV = [ Amp( f1 ), Amp( f 1 ),..., Amp( f n )]
(7)
where Amp( f i ) denotes the function of amplitude which depends on frequency
f i and n is the number of frequencies in consideration. A feature vector is assembled from these dominant wavelet values. A feature vector forms a cross section of wavelet data values at level n in the wavelet packet tree containing 2 features. This system is dynamic and can assemble vectors from all depths of the tree. n
Case-Based Classification using Extracted Features. After the features have been extracted from sensor signals, we perform CBR to make classification of the current fault using known cases in the case library. Fig. 27 gives an overall illustration for this procedure, which consists of the following two steps: 1.
Retrieval: compare the feature vector with the known cases in the library by means of similarity calculation and subsequently select the k nearest cases exhibiting the highest similarity degrees;
2.
Solution fusion: determine the fault class associated with the current feature vector in terms of both the classes of the retrieved cases and their similarity values with respect to the probe case.
Fig. 27. Case-based classification as decision support
46
M.U. Ahmed et al.
The matching algorithm calculates the Euclidian distance between the case that is to be classified and those cases previously stored in the case library. The distance function uses the feature vectors along with a set of weights defined on the features. Such weights c j are incorporated into the distance calculation, as indicated in (equation 8), to reflect different importance of different features. d
∑a
j
− b j ∗ c j , a, b, c ∈ ℜ d
(8)
j =1
The classification of robot sound is based on the above matching function. The result of matching yields a scored list of the most similar cases. This list can be presented to responsible technicians as decision support for their further evaluation. An alternative is to derive a voting score for every class involved in the retrieved list of similar cases and then the final decision is settled upon the class exhibiting the highest voting score [66]. It is worthwhile to mention that the performance of our CBR system is improved each time when a new classified case is injected into the case library. The system can thereafter be tested with sounds from other robots previously classified by experts so as to estimate its accuracy. If the accuracy is estimated to be adequate, this CBR system can then be applied to diagnosing robot faults for practical usage. Sound Classification and Results. Sounds from 24 healthy robots and 6 faulty robots were collected to enable case-based classification of conditions of robots. Two types of faults need to be recognized in the experiments hereafter called Fault 1 and Fault 2. A notch on the big gear wheel in the gearbox causes Fault 1. This fault is hearable and is characterized by a low frequency impulse sound in the middle of the rotation of the axis. Fault 2 is caused due to a slack between the gear wheels in the gearbox and can be heard as bumps at the end of each rotation. A feature vector is assembled with peak wavelet coefficients taken from different depths in a wavelet package tree [54] and it is then matched with the previously inserted cases in the case library. The prototype system demonstrated quite good performance by making right judgments in 91% of the all tests (see further down). Table 5 displays a ranked list of the three best matching cases in the case library according to the similarity values calculated. As can be seen from the table, a previously diagnosed notch fault recording is deemed to be the most similar case thereby making the strongest recommendation to classify the probe situation into notch fault. The cases ranked the second (case #12) and the third (case #4) are descriptions classified as normal in the case library. This list of the most similar cases can be presented to human operators as decision support. Table 5. A ranking of the most similar cases for the sound profile
Case name Notch fault #2 Normal case #12 Normal case #4
Similarity 98% 84% 83%
Case ranking 1 2 3
Case-Based Reasoning for Medical and Industrial Decision Support Systems
47
We also investigated the classification accuracy in relation with different feature vector sizes in order to assess the smallest number of features that still produce good classification performance. The diagram in Fig. 28 indicates the relation between the classification error rate and the number of features.
Fig. 28. Relation between classification performance and the number of features
The top curve in the line chart diagram shows the results when only top 1 case was considered for solution fusion. The bottom curve in the line chart diagram shows the classification results when the top three cases were considered. When only the nearest case was considered, the system produced a classification rate of 91%. When the three nearest cases were considered, the classification rate of the system rose to 99%.
5 Conclusion Case based reasoning is now a well established approach for building intelligent computer-aided DSS-both in medical and industrial domain. However, recent progresses in these fields offer CBR researchers new challenges and opportunities. This chapter provides examples of how CBR is applied in the context of different decision making tasks and challenges in medical and industrial domain. A multimodel case-based DSS for stress management and an agent-based CBR maintenance system for industrial applications are presented here. It can be observed for both of these areas, several artificial intelligence and signal processing techniques are applied besides the CBR approach. Thus, the chapter addresses the issue of how CBR systems are being capable of integrating with other AI techniques and able to handle new challenges in two technical domains:
48
M.U. Ahmed et al.
1) The clinical DSS assists a clinician in a number of complex tasks in stress management by combining more than one artificial intelligence techniques with CBR. The reliability of the clinical system based on sensor readings could certainly be increased by providing contextual information supporting the reasoning tasks. Therefore, the system considers additional information in a textual format applying textual information retrieval. Here, it is also illustrated that it is possible to increase accuracy in the classification tasks, by extending the case library with artificial cases. A case study also shows that the system provides results close to a human expert. Today the system is based on one physiological parameter i.e. finger temperature sensor signal, in future several other parameters such as heart rate, breathing rate etc. could be investigated as a reference of the work for more reliable and efficient decision support in stress management. 2) As shown in the case-study, the concept of intelligent agents in combination with CBR offer a potential of increased production quality, flexibility, reliability and fast delivery times in production industry. Agents may enable improved decision making since they can be designed to learn from experience, use and transfer experience relevant to the current situations, collaborate with other agents, systems and humans. This enables flexible and modular maintenance systems where different suppliers can deliver agents, developed to be experts in specific tasks. To bring the benefits of agent based maintenance systems to industry the first issue is to spread knowledge and understanding of the agent paradigm and its strengths and weaknesses. Thinking in terms of agents gives a number of advantages in system design and development, and may lead to valuable features and functionality that may not have been thought of without this framework of thought.
References 1. Aamodt, A., Plaza, E.: Case-based reasoning: Foundational issues, methodological variations, and system approaches. AI Communications 7, 39–59 (1994) 2. AAPB, The Association for Applied Psychophysiology and Biofeedback (March 2010), http://www.aapb.org/i4a/pages/index.cfm?pageid=336 3. Bareiss, E.: Examplar-based Knowledge Acquisition: A unified Approach to Concept, Classification and learning. PHD thesis, 300 North Zeeb Road, Ann Arbor, AI 481061346 (1989) 4. Bareiss, E.: RPROTOS: A Unified Approach to Concept Representation, Classification, and learning. Ph.D. thesis, Department of Computer Science, University of Texas (1988) 5. Begum, S., Ahmed, M.U., Funk, P., Xiong, N., Schéele, V.B.: A Case-Based Decision Support System for Individual Stress Diagnosis Using Fuzzy Similarity Matching. In Press of the International Journal of Computational Intelligence (2009) 6. Begum, S., Ahmed, M.U., Funk, P., Xiong, N., Scheele Von, B.: Using calibration and fuzzification of cases for improved diagnosis and treatment of stress. In: The Proceedings of the 8th European Workshop on Case-based Reasoning, pp. 113–122 (2006) 7. Bergmann, R., Kolodner, J., Plaza, E.: Representation in case-based reasoning. The Knowledge Engineering Review 20(3), 209–213 (2005)
Case-Based Reasoning for Medical and Industrial Decision Support Systems
49
8. Bichindaritz, I., Marling, C.: Case-based reasoning in the health sciences: What’s next? Artificial Intelligence in Medicine 36(2), 127–135 (2006) 9. Cannon, W.B.: Bodily changes in pain, hunger, fear and rage: An account of recent research into the function of emotional excitement, 2nd edn. Appleton-Century-Crofts, New York (1929) 10. Funk, P., Xiong, N.: Case-Based Reasoning and Knowledge Discovery in Medical Applications with Time Series. Journal of Computational Intelligence 22(3/4), 238– 253 (2006) 11. Gierl, L., Schmidt, R.: CBR in Medicine. In: Lenz, M., Bartsch-Spörl, B., Burkhard, H.-D., Wess, S. (eds.) Case-Based Reasoning Technology. LNCS (LNAI), vol. 1400, pp. 273–298. Springer, Heidelberg (1998) 12. Healey, J.A., Picard, R.W.: Detecting Stress during Real-world Driving Task using Physiological Sensors. IEEE Trans. on Intelligent Transportation System 6(2), 156– 166 (2005) 13. Hinkle, D., Toomey, C.: Applying Case-Based Reasoning to Manufacturing. AI Magazine 16(1), 65–73 (1995) 14. Kappes, B.: Biofeedback therapy: Training or Treatment. In Applied Psychophysiology and Biofeedback 33, 173–179 (2008) 15. Kolodner, J.L.: Maintaining Organization in a Dynamic Long-Term Memory. Cognitive Science 7(iv), 243–280 (1983) 16. Kolodner, J.L.: Reconstructive Memory: A Computer Model. Cognitive Science 7(iv), 281–328 (1983) 17. Kolodner, J.L.: Case-Based Reasoning. Morgan Kaufmann, San Mateo (1993) 18. Koton, P.: Using experience in learning and problem solving. Massachusetts Institute of Technology, Laboratory of Computer Science. Ph.D. Thesis MIT/LCS/TR-441 (1989) 19. Lawrence Wilson, M.D.: Autonomic Nervous System Health, http://www.drlwilson.com/Articles/NERVOUS%20SYSTEM.htm (Last referred September 2009) 20. Lehrer, M.P., et al.: Respiratory Sinus Arrytmia Biofeedback Therapy for Asthma: A report of 20 Unnnmedicated Pediatric Cases Using the Smetaniknnnn Method. Applied Psychophysiology and Biofeedback 25(3), 193–200 (2000) 21. Managing stress: A guide for UFT members, http://www.uft.org/member/publications/health/ stress/stressdefined/ (Last referred August 2009) 22. Mason, L.J.: Control Symptoms of Stress with Temperature Training Biofeedback, EzineArticles (September 2008), http://ezinearticles.com/?ControlSymptoms-of-Stress-with-Temperature-TrainingBiofeedback&id=90394 23. Montani, S.: Exploring new roles for case-based reasoning in heterogeneous AI systems for medical decision support. In: Applied Intelligence, pp. 275–285 (2007) 24. Ontañón, S., Plaza, E.: Collaborative case retention strategies for CBR agents. In: Ashley, K.D., Bridge, D.G. (eds.) ICCBR 2003. LNCS (LNAI), vol. 2689, pp. 392–406. Springer, Heidelberg (2003) 25. Ramon, L.M., David, M., Derek, B., David, L., Barry, S., Susan, C., Boi, F., Mary, L.M., Michael, T.C., Kenneth, F., Mark, K., Agnar, A., Ian, W.: Retrieval, reuse, revision and retention in case-based reasoning. The Knowledge Engineering Review 20(3), 215–240 (2005)
50
M.U. Ahmed et al.
26. Reisbeck, C.K., Schank, R.C.: Inside Case-Based Reasoning. Lawrence Erlbaum Associates, Hillsdale (1989) 27. Noble, R.E.: Diagnosis of stress. International journal Metabolism - Clinical and Experimental, Elsevier Science (USA) 51(6), Part 2, 37–39 (2002) 28. Selye, H.: The Stress of Life. McGrawHill, New York (1956) (Rev. ed. 1976) 29. Seung, H.K., Sim, K.L.: Intelligent Knowledge Acquisition with Case -Based Reasoning Techniques, University of Wollongong, NSW, Australia 30. Simpson, R.L.: A Computer Model of Case-Based Reasoning in Problem Solving: An Investigation in the Domain of Dispute Mediation. Technical Report GIT-ICS-85/18, Georgia Institute of Technology, School of Information and Computer Science, Atlanta, US (1985) 31. Ahmed, M.U., Begum, S., Funk, P., Xiong, N., von Schéele, B.: A Multi-Module Case Based Biofeedback System for Stress Treatment. In: Artificial Intelligence in Medicine. Elsevier, Amsterdam (in press, 2010) 32. Watson, I., Marir, F.: Case-Based Reasoning: A Review, AI-CBR, Dept. of Computer Science, University of Auckland, New Zealand, http://www.aicbr.org/classroom/cbr-review.html (last referred August 2009) 33. Bemmel, J.H.V., Musen, M.A.: Handbook of Medical informatics. Springer, Heidelberg (1997) ISBN 3-450-63351-0 34. Turban, E., Aronson, E.J.: Decision support systems and intelligent systems, 6th edn. Prentice Hall, Englewood Cliffs (2001) ISBN 0-13-089465-6 35. Shortliffe, E.: Computer-based medical consultations: MYCIN. Elsevier/North Holland, New York (1976) 36. Watson, I.: Applying Case-Based Reasoning: Techniques for Enterprise Systems. Morgan Kaufmann Publishers Inc., San Francisco (1997) 37. http://www.pbmsystems.se/system2/ft.asp (Last referred March, 2010) 38. Carol, C.H., Balakrishnan, N., Nikulin, M.S., Huber-Carol, C., Mesbah, M.: Goodnessof-Fit Tests and Model Validity, p. 507. Birkhauser Verlag, Basel (2002) ISBN 0817642099 39. Fuzzy Logic. Stanford Encyclopedia of Philosophy. Stanford University (July 23, 2006) http://plato.stanford.edu/entries/logic-fuzzy/ (Retrieved September 29, 2008) 40. Jang, J.S.R., Sun, C.T., Mizutani, E.: Neuro-fuzzy and Soft Computing. A computional approach to learning and machine intelligence. Prentice Hall, NJ (1997) ISBN 013261066-3 41. Lukasiewicz, J.: A system of modal logic. Journal of Computing Systems 1, 111–149 (1953) 42. Lukasiewicz, J.: Comptes rendus des seances de la societe des sciences et des letters de Varsovie, cl. III 23. Journal Philosophische Bemerkungen zu mehrwertigen Systemen der Aussagenlogik, 51–77 (1930) 43. Salton, G., Wong, A., Yang, C.S.: A Vector Space Model for Automatic Indexing. Communications of the ACM 18(11), 613–620 (1975) 44. Salton, C., Buckley: Term Weighting Approaches in Automatic Text Retrieval. Technical Report. UMI Order Number: TR87-881. Cornell University (1987) 45. Weber, R., Ashley, K.D., Brüninghaus, S.B.: Textual case-based reasoning. The Knowledge Engineering Review 00(0), 1–00 (2005) 46. Wikipedia, History of logic, http://en.wikipedia.org/wiki/History_of_logic (last refereed March, 2010)
Case-Based Reasoning for Medical and Industrial Decision Support Systems
51
47. Wikipedia, Information retrieval, http://en.wikipedia.org/wiki/Information_retrieval (last refereed March, 2010) 48. Zadeh, L.A.: Outline of a new approach to the analysis of complex systems and decision processes. IEEE Trans. Systems, Man Cybernet. 3, 28–44 (1973) 49. Zadeh, L.A.: Fuzzy sets. Information and Control 8(3), 338–353 (1965) 50. Bonissone, P., Cheetham, W.: Fuzzy Case-Based Reasoning for Residential Property Valuation. In: Handbook on Fuzzy Computing (G 15.1). Oxford University Press, Oxford (1998) 51. Dvir, G., Langholz, G., Schneider, M.: Matching attributes in a fuzzy case based reasoning. Fuzzy Information Processing Society, 33–36 (1999) 52. Richter, M.M.: Modeling Uncertainty and Similarity-Based Reasoning - Challenges. In: Proceedings of the 8th European Workshop on Uncertainty and Fuzziness in CBR, pp. 191–199 (2006) 53. Wang, W.J.: New similarity measures on fuzzy sets and on elements. Fuzzy Sets and Systems, 305–309 (1997) 54. Bachman, G.: Fourier and Wavelet Analysis. Springer, New York (2000) 55. Ahmed, M.U., Begum, S., Funk, P., Xiong, N., Schéele von, B.: A Three Phase Computer Assisted Biofeedback Training System Using Case-Based Reasoning. In: Schaaf, M. (ed.) 9th European Conference on Case-based Reasoning workshop proceedings, Trier, Germany, August 2008, pp. 57–68 (2008) 56. Olsson, E., Funk, P., Jackson, M., Bengtsson, M.: Technical Design of Condition Based Maintenance Systems - A Case Study using Sound Analysis and Case-Based Reasoning. In: MARCON (Maintenance and Reliability Conference), Knoxville, TN, USA, May 2004, p. 12 (2004) 57. Begum, S., Ahmed, M.U., Funk, P.: Case-Based Systems in the Health Sciences - A Case Study in the Field of Stress Management. WSEAS Transactions on Systems 8(1109-2777), 344–354 (2009) 58. Daubechies, I.: Orthonormal Bases of Compactly Supported Wavelets. Comm. Pure Appl. Math. 41, 906–966 (1988) 59. Franklin, S., Graesser, A.: Is it an agent, or just a program?: A taxonomy for autonomous agents. In: Jennings, N.R., Wooldridge, M.J., Müller, J.P. (eds.) ECAI-WS 1996 and ATAL 1996. LNCS, vol. 1193, pp. 21–35. Springer, Heidelberg (1997) 60. Funk, P., Olsson, E., Bengtsson, M., Xiong, N.: Case-Based Experience Reuse and Agents for Efficient Health Monitoring, Prevention and Corrective Actions. In: Proceedings of the 19th International Congress on Condition, COMADEM, pp. 445–453 (2006) 61. Ahmed, M.U., Begum, S., Funk, P., Xiong, N., von Schéele, B.: Case-based Reasoning for Diagnosis of Stress using Enhanced Cosine and Fuzzy Similarity. Transactions on Case-Based Reasoning on Multimedia Data 1(1) (2008) ISSN: 1864-9734 62. Ahmed, M.U., Begum, S., Funk, P.: A Multi-Modal Case-Based System for Clinical Diagnosis and Treatment in Stress Management. In: Delany, S.J. (ed.) Seventh Workshop on Case-Based Reasoning in the Health Sciences, Seattle, Washington, USA, July 2009, pp. 215–224 (2009) 63. Mitchell, T.M.: Machine Learning, pp. 230–236. McGraw-Hill, New York (1997) 64. Nilsson, M., Funk, P.: A Case-Based Classification of Respiratory Sinus Arrhythmia. In: Funk, P., González Calero, P.A. (eds.) ECCBR 2004. LNCS (LNAI), vol. 3155, pp. 673–685. Springer, Heidelberg (2004)
52
M.U. Ahmed et al.
65. Olsson, E., Funk, P., Bengtsson, M.: Case-Based Diagnosis of Industrial Robots Based on Acoustic Signals. In: Funk, P., González Calero, P.A. (eds.) ECCBR 2004. LNCS (LNAI), vol. 3155, pp. 686–701. Springer, Heidelberg (2004) 66. Olsson, E., Funk, P., Xiong, N.: Fault Diagnosis in Industry Using Sensor Readings and Case-Based Reasoning. Journal of Intelligent and Fuzzy Systems (2004) 67. Ahmed, M.U., Begum, S., Funk, P., Xiong, N.: Fuzzy Rule-Based Classification to Build Initial Case Library for Case-Based Stress Diagnosis. In: Hamza, M.H. (ed.) 9th IASTED international conference on Artificial Intelligence and Applications (AIA) 2009, Innsbruck, Austria (2009) 68. Russel, S., Norvig, P.: Artificial Intelligence A Modern Approach, International edn., pp. 31–52. Prentice Hall International Editions, Englewood Cliffs (1995) 69. Thurston, M.G.: An Open Standard for Web-Based Condition-Based Maintenance Systems. In: AUTOTESTCON Proceedings, Valley Forge, PA, USA, pp. 401–415 (2001) 70. Wooldridge, M., Jennings, N.R.: Intelligent agents: Theory and practice. The Knowledge Engineering Review 10(2), 115–152 (1995) 71. Begum, S., Ahmed, M.U., Funk, P., Xiong, N., von Schéele, B.: Classify and Diagnose Individual Stress Using Calibration and Fuzzy Case-Based Reasoning. In: Weber, R.O., Richter, M.M. (eds.) ICCBR 2007. LNCS (LNAI), vol. 4626, pp. 478–491. Springer, Heidelberg (2007) 72. Ahmed, M.U., Olsson, E., Funk, P., Xiong, N.: Efficient Condition Monitoring and Diagnosis Using a Case-Based Experience Sharing System. In: 20th International Congress and Exhibition on Condition Monitoring and Diagnostics Engineering Management, COMADEM 2007, IT-Instituto de Telecomunicacoes, Faro, Portugal, June 2007, pp. 305–314 (2007) 73. Ahmed, M.U., Olsson, E., Funk, P., Xiong, N.: A Case-Based Reasoning System for Knowledge and Experience Reuse. In: Löfström, et al. (eds.) Proceedings of the 24th annual workshop of the Swedish Artificial Intelligence Society, Borås, Sweden, pp. 70–80 (2007) 74. Ahmed, M.U., Westin, J., Nyholm, D., Dougherty, M., Groth, T.: A fuzzy rule-based decision support system for Duodopa treatment in Parkinson. In: Eklund, P., Minock, M., Lindgren, H. (eds.) SAIS 2006, Umeå, May 10-12, pp. 45–50 (2006) 75. Begum, S., Ahmed, M.U., Funk, P., Xiong, N., Schéele, B.V.: Similarity of Medical Cases in Health Care Using Cosine Similarity and Ontology. In: Wilson, D.C., Khemani, D. (eds.) ICCBR 2007. LNCS, pp. 263–272. Springer, Heidelberg (2007) 76. Xiong, N., Funk, P.: Concise case indexing of time series in health care by means of key sequence discovery. Journal of Applied Intelligence 28, 247–260 (2008)
Chapter 3
Development of Industrial Knowledge Management Applications with Case-Based Reasoning Mehmet H. Göker1, Catherine Baudin2, and Michel Manago1 1
Kiolis 5 rue Rubens 75013 Paris, France {mgoker,mmanago}@kiolis.com 2 eBay Whitman Campus 2065 Hamilton Ave San Jose, CA 95125 [email protected] Abstract. The successful development, deployment and utilization of CaseBased Reasoning Systems in commercial environments require the development team to focus on aspects that go beyond the core CBR engine itself. Characteristics of the Users, the Organization and the Domain have considerable impact on the design decisions during implementation and on the success of the project after deployment. If the system is not technically and organizationally integrated with the operating environment, it will eventually fail. In this chapter, we describe our experiences and the steps we found useful while implementing CBR applications for commercial use. We learned these lessons the hard way. Our goal is to document our experience and help practitioners develop their own approach and avoid making the same mistakes.
1 Introduction The development of knowledge management applications for business environments requires balancing the needs of various parties within the client’s organization. While end users desire to have a system that operates effectively and efficiently without changing their existing workflow, the business unit may be interested in reducing costs, optimizing processes, capturing data, and endorsing corporate policies. The IT department of the client will be interested in applications that fit into their standard deployment environment and will certainly not appreciate the need for an application that learns, modifies its knowledge components, and changes its behavior without anybody changing the actual code of the system. Balancing these requirements without endangering the long term success of an application can become challenging. S. Montani & L.C. Jain (Eds.): Successful Case-Based Reasoning Appl., SCI 305, pp. 53–82. © Springer-Verlag Berlin Heidelberg 2010 springerlink.com
54
M.H. Göker, C. Baudin, and M. Manago
The design decisions made during the development of Case-Based Knowledge Management systems impact the long term success of these applications drastically. The application has to be designed in such a way that it delivers useful solutions to end users, accommodates the needs of users with different levels of knowledge and responsibility, operates within the existing knowledge creation and revision workflow of the company, makes use of existing knowledge sources and the organization around them, supports authoring in a light-weight manner, facilitates long term growth by means of reporting facilities and maintenance operations, is easy to deploy and operate in a corporate environment, allows the business unit to make changes to application settings with immediate effect, can be deployed in a short timeframe, is based on industry standards, requires no customizations and is cheap. While this list of desired characteristics is only partial, it shows that some of the requirements can be rather contradictory and require optimization. This chapter is based on the INRECA methodology [BeAl03] and the personal experience the authors gained while developing and deploying several medium and large scale Case-Based Reasoning (CBR) projects during their tenure at Kaidara Software1 and other organizations. It aims to describe the tasks and the sequence that we found useful during the specification, implementation and deployment of realworld CBR systems. We hope that it serves as a basis on which other practitioners can develop their own User approach. Most of the applications described in this chapter have been in operation for more than five years and CBR went through several reviApplication sions. Regrettably, we cannot include more information than we disclose Organization Domain here – a side effect of being in industry. Some more information on the applications can be found on Kaidara’s website at Fig. 1. Environment of a CBR application www.kaidara.com.
2 Defining and Designing a CBR System As with any knowledge management application, Case-Based Reasoning applications are defined by the environment they will operate in. The users, the organization 1
Kaidara Software Inc., 5150 El Camino Real, Suite 100, Los Altos, CA 94022 www.kaidara.com
Development of Industrial Knowledge Management Applications with CBR
55
in which the system will run and the application domain for which the system provides solutions have drastic impact on the manner in which the application needs to be designed. Ignoring one of these aspects will cause the application to join the hundreds of other knowledge management applications that have died a slow death. 2.1 User Types In general, the following user types need to be taken into consideration while designing the application: • End Users are the internal or external clients that the business unit is targeting with the application. They utilize the system to search for content. • Authors use the application to create and review content. • Subject Matter Experts are acknowledged authorities in the domain of the application. They can specify, review and approve content, vocabulary, relationships and similarity settings by using the application. • Knowledge Engineers specify and update system settings (similarity, domain model etc.) and maintain the knowledge in the application. They implement the settings suggested by subject matter experts and adapt the behavior of the CBR application accordingly. A knowledge engineer does not need to have experience in the application domain itself but should be familiar with the system and the tools required to maintain the knowledge containers2 [Ri95]. • System Administrators manage the application in the IT environment. They enable the CBR application to execute in the server environment of the client and to communicate with other relevant IT systems (CRM applications, database etc.). While not every environment will need to have all of these roles filled with dedicated personnel and the tasks of these user types will vary between implementations, the needs associated with each one of these roles will put specific demands on the application and will have to be supported. Failure to consider any one of the roles will reduce the chances of the system to be successful. 2.2 Application Domain Every client is certain that their domain is complex and cannot easily be represented in a knowledge management application. While it is true that each application domain is different, our experience is that the level of complexity for applications belonging to the same class is generally comparable. The effort involved in representing knowledge and implementing a useful application is influenced by the following factors:
2
The knowledge containers of a case-based reasoning system are the vocabulary, the similarity computation, the adaptation knowledge and the cases themselves [Ri95].
56
M.H. Göker, C. Baudin, and M. Manago
• Application type: The application type influences the design of the knowledge containers as well as the user interaction required. Common application types include diagnosis & troubleshooting, e-commerce, design, legal, medical etc. • Available data sources: The quality, quantity and accessibility of information to populate the case-base are critical for the design of the application. The manner in which the information is provided can range from structured databases to textual records to web-pages to human experts. • Operating environment: The environment, both with respect to IT hardware and software (e.g. embedded application, standalone, web based) as well as the organization in which the system will operate (e.g. technician use, call center, self-help, product search) create requirements that range from memory size to user interface specifications. Applications may also operate in multiple modes (e.g. standalone and connected) and will require the implementation of synchronization operations. • User types: The level of experience and goals of the user that will interact with the system defines the manner in which the information needs to be represented and how the interaction modalities with the system have to be designed. • Impact of inaccurate responses: Depending on the application domain, the impact of inaccurate responses (false positives or false negatives) will vary from being a minor nuisance to life threatening. While a wrong choice in a restaurant search application will not have a major impact on the user and the company operating the system, a wrong repair suggestion for a medical device might have bigger human and legal ramifications. The application and the workflows to use, create and maintain knowledge have to be designed accordingly. 2.3 Organizational Aspects A knowledge management application has to be designed to fit into the organization of a client and support the employees in doing their daily work or end-users in the task they are trying to execute. An application that requires the client, its employees and the end users to restructure the way they work is typically more difficult to implement than an application that support employees and users in their normal routines and provides clients with a path for improving their organization. Aspects to consider include • Workflow: How information is passed between users in the organization. This includes existing knowledge creation, review and maintenance workflows as well as the corporate culture. • Authorization and Authentication: Who is able to see and do what with which information. The user group may contain company internal users from various departments and management levels as well as external clients. • IT Environment: The HW, OS, database, Web/Application Server, Corporate IT policies, Staging and Publishing specifications, approach to SaaS models etc. will impact the design of the application and need to be considered as early in the design process as possible.
Development of Industrial Knowledge Management Applications with CBR
57
• Logging, Feedback options and Reporting: Each user interaction with the system might be recorded (for quality assurance purposes) on a highly detailed level and analyzed later. The level at which the interactions are being logged is application specific and depends on the application domain and planned maintenance operations. Feedback enables the users to voice their opinions regarding the system in general, specific interaction modalities or individual solutions. Based on logs and the feedback provided by users, various reports can be implemented and used to maintain the system and analyze its impact on the organization. Issues that need to be considered range from privacy concerns to the development of a representation (vocabulary) that supports the creation of the reports that are required by the client.
3 CBR System Development Steps The development of a Case-Based knowledge management application differs from the development of standard software applications. Rather than being of pure transactional nature, knowledge management applications adapt their behavior according to the information that users enter and update. The role of a knowledge engineer who is able to modify the system’s behavior without coding is unusual and typically frowned upon by IT organizations. In general, the following steps have to be performed during the development of a system (Figure 2): o o o o o o o o o o o o
Initial Application Area and Project Team Selection, Kick-Off Project Team Training Requirements Specification Data Analysis and Vocabulary Definition for Initial Application Area, Initial Knowledge Acquisition System Design System Implementation Standalone System Test and Revision Data Analysis and Vocabulary Definition for Remaining Application Areas Continuous Knowledge Acquisition and Revision System Integration Test and Revision of Integrated System Deployment and Go-Live.
In this section, we will briefly go over the steps involved in the development of Case-Based knowledge management applications and highlight the areas that differ from “normal” software development. We will not go into the implementation and testing tasks due to their relatively conventional nature (independent of the software development methodology one chooses to follow). The continuous vocabulary definition and knowledge acquisition tasks will be covered in the initial Data Analysis and Vocabulary Definition task.
58
M.H. Göker, C. Baudin, and M. Manago
Initial Application Area and Project Team Selection Kick-Off
Project Team Training
External Data
Requirements Specification
Initial Knowledge Acquisition
Data Analysis and Vocabulary Definition for Initial Application Area
System Design Data Analysis and Vocabulary Definition for Remaining Application Areas Standalone System Implementation Continuous Vocabulary Refinement and Knowledge Acquisition Standalone System Test and Revision
Integrated System Implementation
Integrated System Test and Revision
Sign-Off and Go-Live
Fig. 2. Observed development Steps for a Case-Based Knowledge Management Application
Development of Industrial Knowledge Management Applications with CBR
59
3.1 Initial Application Area and Project Team Selection, Project Kick-Off Once the project is approved, the business stakeholder will select the application area that is most important and should be addressed first in the course of the project. This application area should be selected amongst the most important (highest call volume, highest number of requests, highest visibility) and be representative for other knowledge areas in the domain. Rather than selecting independent sub-domains, it is advisable to select problem areas between which solutions could be reused. For diagnosis applications, we found it beneficial to select and model one problem type across multiple products rather than to represent several problem types for one product. This has the benefit of enabling the development team to quickly demonstrate how knowledge from one product can be used to help diagnose other products. The project team for the application is selected according to the initial application area. It should contain representatives of the business side, the knowledge area (subject matter experts) as well as the IT department of the customer. Having more than one subject matter expert (SMEs) that has to work in the domain on a day-to-day basis on the project team is advisable. It will encourage discussions during knowledge acquisition sessions and ensure that the application is based on a broader consensus and does not only represent one expert’s opinion. After the initial application area and project team has been selected, a kick-off meeting should be held. In this meeting, the parties are introduced and the business stakeholder states his goals for the application. Since not all of the parties involved in the kick-off will take part in the later training and the project, it is advisable to give an introduction to the basics of Case-Based Reasoning. This will ensure that the team has a basic common vocabulary in future discussions. 3.2 Project Team Training Even if there is some previous familiarity with knowledge management topics, it is important for the entire project team to be trained and introduced to Case-Based Reasoning and the approach to developing applications. Depending on the participants, the training should cover aspects such as general Case-Based Reasoning, vocabulary definition, similarity computation, approaches to guided search and free text processing or feature extraction, server configuration and potentially application development based on an API. • Knowledge Engineers: Should be trained on CBR in general, knowledge representation and its effects on retrieval quality and maintainability, similarity settings, domain modeling, and on how to maintain an application. • Authors and Subject Matter Experts: Should be trained on CBR in general, authoring and reviewing cases, representation and its effects on retrieval quality and authoring effort. • End Users: For simple and well designed applications, no training should be needed. If the application is complex and impacts and changes the day-to-day work of the users simple training or help files are recommended. • System Administrators: Should be trained on how the application is deployed, how application and knowledge updates are performed, staged and published.
60
M.H. Göker, C. Baudin, and M. Manago
3.3 Requirements Specification During Requirements Specification, business analysts, project engineers and knowledge engineers work with the client to elicit the requirements for the project, arrive at a common understanding regarding the goals, and document them. The requirements specification is the basis for the development of the entire application and is used to generate criteria for acceptance tests at the end of the project. Aspects that are covered in the requirement specification include: • Problem Description: Goals of the system, intended audience, project charter as defined by the business owner • Project Organization: Roles, responsibilities and contact information of personnel involved in the project • Core Functional Requirements: A detailed, step by step description of what the application is going to do • Data Analysis and vocabulary definition requirements: Available data, data sources and required transformations, data transfer needed from other applications • User types, roles and responsibilities: A description of various user types that are going to work with the application and what they will be able to do • Workflows for Case or Content creation, approval, utilization and maintenance: A description of the workflows in the application • User interface requirements: A description of the user interface requirements (as dictated by the customers IT department) and how they will impact the layout of the application. • Logging, feedback and reporting requirements: Requirements for logging, user feedback and reports that will be generated using this data. • Software environment and integration: The software environment in which the application is going to run (J2EE and versions, .NET and versions, application servers, database environment, operating systems, supported browser types etc.) as well as the applications that exchange data with the system need to be specified. If the application is a web application, the architecture of the client’s server environment needs to be analyzed (how many layers, security requirements between layers, database organization etc.) • System administration requirements: Specification of the requirements related to operating the system within the IT environment of a customer. Requirements related to user management, backup and restore strategies, options for rollback, versioning of application and content, staging and publishing processes, load balancing, failover and session persistence, server startup etc. need to be clarified. • Documentation requirements: The required documentation (specifications, design documents as well as manuals) and their formats. • Training Requirements: Who will be trained when and on which topics. • Support Options and Requirements: How much support is going to be provided and to whom (Support Level Agreements – SLAs). • Communication and scope change process: How are changes in the specification requested, approved and communicated. • Target dates and project plan: What are the target dates and when will the system be operational.
Development of Industrial Knowledge Management Applications with CBR
61
3.4 Data Analysis and Vocabulary Definition During Data Analysis and Vocabulary Definition, business analysts, knowledge engineers and domain experts work together to define the core representation that will be used in the system for storing and retrieving cases. Details of this task depend on the type of CBR system that is being implemented (structural, conversational, textual [c.f. BeAl03, Be02]). However, in general, the following tasks need to be performed: • Analyze existing data and information sources, • Clean existing data (noisy data, structure variants) • Define initial vocabulary (domain model for structural CBR systems) as well as application settings (similarity etc.), define representation, specify synonyms • Analyze initial case creation, revision, utilization and maintenance workflows as well as reporting requirements to enhance vocabulary as needed • Determine data extraction methods for data conversion, extract initial set of cases and revise rules if needed • Perform initial knowledge acquisition to optimize the vocabulary and test similarity settings, create seed case-base / import product data. 3.5 Selection and Impact of Representation Selecting the representation method and vocabulary for a CBR system is one of the most important development steps and influences the speed of deployment, the long term maintainability, user interaction styles and the maximum granularity that is available to represent information in the domain. In general, cases can be represented in three different styles: textual, conversational, and structural [BeAl03, Be02]. In the textual CBR approach, cases are represented in free-text form and similarity computation is based on statistical and information retrieval techniques. The vocabulary that needs to be defined in these systems may be as limited as a set of synonyms. Conversational CBR systems represent cases as lists of questions and answers. The number and sequence of questions can differ between cases and questions do not necessarily have to be reused. During vocabulary creation, questions and lists of possible answers are created and, if the development environment permits is, organized into groups [Gu01, GuAhSa02, GuAh03]. In the structural CBR approach, the developer of the vocabulary decides ahead of time what features (attributes and associated values) will be relevant when describing cases and may refine the model during the case acquisition phase (especially if the cases are acquired from existing text, see section 3.6) In general,the representation defines the maximum complexity that can be stored in cases. This structured, potentially object-oriented set of features is known as the domain model. While cases in textual and structural CBR systems are independent of each other, cases in conversational CBR systems may be linked by means of the question and answer clusters they share. The representation in these systems is akin to a
62
M.H. Göker, C. Baudin, and M. Manago
decision tree and shares some of its characteristics. The suitability of No Start Transient each representation type depends on the complexOnce in a while ity of the application domain, the number of ATTRIBUTE: Constantly cases that will be repreProblem Stalling Description sented in the system as Once in a while well as the level of expertise of the users. Searching and maintainOccasionally Power ing a textual CBR sysFluctuation tem may be acceptable In the mornings for a small number of documents. However, with increasing number Fig. 3. Representation of a problem type using a single of cases, a textual CBR taxonomic attribute system will not be able to perform better than a free text search engine. A pure conversational system will deliver good results for domains with limited representational complexity and a small number of cases. Since the effort required to add and remove cases from the case-base grows exponentially with the number of questions that are used in the representation, the suitability of this approach to complex problems is limited. Structural CBR systems require an up-front effort to create the vocabulary and are therefore not suitable for open ended search tasks on topics that cannot be anticipated. Once a suitable vocabulary is defined, new cases can easily be added and removed by selecting values for attributes. The effort is independent of the number of cases already in the casebase and grows linear with the domain complexity. Pure structural CBR requires a relatively stable domain model and that cases have a comparable structure. Real world applications typically require a mixture of representations. Large organizations will have textual documents they want to reuse, the number of cases will be high and the representation of the cases may be extremely detailed and change frequently. Applications need to be able to incorporate textual cases into their casebase and also allow extending the representation of each case in a flexible manner. The definition and structure of the vocabulary impact the remaining knowledge containers and enable the system designer to balance the complexities of each. Figure 3 depicts an attribute describing a problem one might experience with an automobile. While this representation is easy to navigate and enables the definition of a single similarity metric, it is obviously difficult to extend and maintain in a consistent manner. The same information can also be represented by creating two attributes (Figure 4) and encoding the knowledge in the cases by combining values from each. This representation is easier to maintain and extend, however it requires a similarity function that uses two attributes rather than one. Constantly
Development of Industrial Knowledge Management Applications with CBR
63
Constantly No Start ATTRIBUTE: Problem Descripon
Stalling
Power Fluctuaon
Transient ATTRIBUTE: Frequency
Once in a while Occasionally In the mornings
Fig. 4. Representation of a car problem with two attributes
3.6 Initial Knowledge Acquisition The type of knowledge acquisition effort in a CBR system depends on the level of structure of its underlying representation and on the nature of the available knowledge sources. For example, textual CBR systems might require the addition of a general layer of meta-knowledge such as: title or problem description to add some structure to free-text cases. More structured CBR systems based on a body of controlled vocabulary, provide fine grain similarity retrieval along with the power or classical structured data analysis but were traditionally geared toward structured cases imported from databases or acquired by subject matter experts directly in the right form. However, nowadays the need to reuse existing data in various forms, tends to blur the distinction between textual and structured CBR. No matter which representation is chosen, for an application to be successful, it has to be initially launched with sufficient content so that users can find what they are looking for most of the time and do not get frustrated. This requires the ability to import existing content stored in a different representation and make it available through the search facilities of the case-based system. If the available information contains some structure, automated tools to transform the information can be used. However, companies produce volumes of textual data in free-text documents, notes in database tables or in spreadsheets. Extracting useful information from this unstructured data is a challenge in spite of a number of tools that have appeared in the marketplace to assist or automate this process. One problem is that free text is notorious for its inconsistent vocabulary. As an example, a problem description for an LCD projector may refer to a "yellow spot at the center of the screen," "a yellowish circle on the screen" or a "brown splotch right in the middle of the image" all of which may describe the same problem. In addition, information trapped in notes is usually riddled with abbreviations and spelling errors which adds to the difficulty. These discrepancies make it difficult to accurately retrieve answers to specific problems.
64
M.H. Göker, C. Baudin, and M. Manago
3.6.1 Case Acquisition from Text Traditionally, full-text search systems have been the preferred tools for exploiting unstructured knowledge. These tools index large collections of text automatically and retrieve information by matching user requests with words from the text. Most fulltext search tools now process natural language queries and accept synonyms, but they are more adequate for accessing large volumes of text on random subjects, such as on the Web, than suited to provide accurate answers to specific questions. In addition, where most intelligent human agents interact with users to clarify queries, full-text search systems just produce results, good or bad, in response to the original request. Along with traditional search, a range of text mining tools and techniques aim at analyzing text collections in order to organize them in ways that provide insight in their content. For example, text clustering automatically groups documents by similarity and produces document clusters sometimes described by the words that best represent them. The clusters, however, depend entirely on word frequencies within a collection and do not take into account any explicit criteria or human input thus providing no guarantees on the way a text collection will be partitioned. Another class of text mining tools that operate without human supervision is based on concept discovery. These tools analyze text collections to extract sequences of words that are repeated and identified based on lexical and statistical criteria. Concept discovery tools can also look for proximity relations among concepts, such as groups of words that often occur together in a paragraph or a sentence. This technology has been mostly used in data visualization to let users browse and access information and has had limited applications, partly because of its focus on open exploration rather than on addressing specific information concerns. These tools may uncover interesting vocabulary and relations, but they cannot be directly used to draw robust conclusions on relationships and trends in the data. The fact that the phrase "yellow spot" occurs significantly more often in text referring to product P1 than to product P2 does not necessarily mean that there are more problems with spots on screens for P1. In fact it could just be that the technician who logged the information for P1 tends to use this phrase whereas another might use "brown splotch" and "yellowish circles" when discussing P2. In other words, there is no guarantee that trends in raw text reflect anything else than vocabulary preferences. Automated text mining techniques that operate directly on raw text can give some idea of what a collection is about, but they do not provide accurate retrieval or robust analytical power. This type of activity is still the kingdom of information systems that are based on structured data and on controlled vocabularies where one concept is represented by one symbol rather than on random words with syntactic variations and synonyms. For this reason an effective way to exploit unstructured data for applications that require precise answers to questions is to map textual information to a data model or vocabulary identified by humans. This model mapping technique is particularly adapted to systems that are already based on a structured domain model. 3.6.2 Model-Directed Text Mapping In model-driven text mapping, input text is first matched to predefined phrases organized in a data model before being accessed and analyzed. This process
Development of Industrial Knowledge Management Applications with CBR
65
occurs in three phases: the first phase is the data analysis and vocabulary definition step. The second phase is the definition of the mapping methods and the addition of synonyms to bridge the gap between the text and the model. The third step is the text-processing phase where unstructured documents are associated with attributes and values from the data model. When this process occurs in batch where several thousand records are processed at once, mechanisms to efficiently detect and validate "hard cases" are essential and might constitute a fourth step. The data model or vocabulary specifies what type of information is expected as input. For example, a model of mechanical problems experienced by car drivers might contain a hierarchy of problem types for a class of vehicles along with values that refer to environmental conditions (rough road, uphill, etc.), frequencies of occurrence, etc. A data model usually contains values and relationships that may be associated to attributes. For example, Figure 5 shows part of a data model for troubleshooting projectors. To bridge the gap between text and the vocabulary in the model, a textmapping engine usually needs two main components: synonyms and mapping procedures. Some synonyms can be found in general thesauruses, but each domain has its own vocabulary. Spot and circle are synonyms in projector troubleshooting, but not in everyday language. While synonyms must often be provided for each application area or industry, many syntactic differences between a text and a model can be bridged by loosening comparison criteria for text strings. In particular, heuristic matching methods can specify what syntactic variations should be tolerated for what types of entities. People, for example, can be matched primarily on last names, first and middle name initials so the associated matching procedure will recognize: John Doe, Doe J. and J. Doe as possibly the same person. Likewise, a matching procedure may specify if partial value matches should be tolerated: can marine blue in the model match blue in the query even if the word marine is absent? Can "marine blue" match "marine deep blue"? Are the orders in the phrases significant? Mapping procedures can also specify the level of tolerance of the comparison to misspellings in the input. Again this level usually depends on the type of data being recognized. For example, error codes or product lines tend to be precise. Chances are that E8456 is different from E8457 whereas the value "intermittently" and "intermittently" are the same even though these two strings also differ by only one character. In general, there are many possible ways to match text to a controlled vocabulary in a model, ranging from broad categorization techniques [CoLe96] to heuristic matching [HuBa97, Rau91]. The key to text mapping is the flexibility to associate different matching methods to different parts of a data model, so as to reflect the differences inherent to each type of data. Finally a data model that contain relationships facilitates the text analysis itself because each time a value from the data model is recognized in the input, the selection narrows the set of remaining values to be mapped. Realizing that a customer problem is with tires automatically rules out problems with gearboxes and engines for the rest of the text mapping process (Figure 5). In the same way, if the model is "Honda Accord" then the body style cannot be Minivan.
66
M.H. Göker, C. Baudin, and M. Manago
Fig. 5. Domain Model to be leveraged for feature extraction (Text2Data ©Kaidara Software)
When text mapping is performed in bulk rather than interactively as an ongoing task, the data-mapping engine must provide ways to validate the results. Some text mapping engines associate a flag to "risky matches" to indicate that this result should be checked. Targeted risk assessment dramatically cuts the number of records that have to be validated. It is not possible to get 100 percent accuracy automatically when interpreting free-text, but the ability of a text mapping system to "get outside help" by flagging dubious results is the next best thing. Figure 6 below shows a modelmapping interface where data administrators can get feedback on the success of a given text mapping strategy on a sample of text records. Each line represents a text record. The second column shows the value assigned to a given attribute next to the initial portion of free text (right column) that is mapped to this value. For example, the highlighted row shows how portion of the original text “.. powers on then powers off” is mapped to the attribute value “projector starts then stops”. Model-driven text mapping is not a technique that applies to open-ended information retrieval systems. It shines in narrowly focused domains where it can be combined with retrieval systems based on structured data to enhance accuracy, user interaction, and data analysis, and where human interpretation can assist with modeling. Text interpretation driven by a domain model becomes easier once the model has been created and does not require a full linguistic parsing of sentences to identify key content and probable meaning in a user query. In this context, automated text mining and concept discovery tools may play an important role in support of data modeling and text mapping as organizations continue to accumulate unstructured data.
Development of Industrial Knowledge Management Applications with CBR
67
Fig. 6. Domain model guided feature extraction (Text2Data ©Kaidara Software)
3.6.3 Knowledge Acquisition from Experts For application areas where prior experience exists only in expert’s heads, subject matter experts can be interviewed to create the cases and vocabulary. The form shown in Figure 7 was used for knowledge acquisition for the HOMER project [GöRB99]. During knowledge acquisition, it is important to ask subject matter experts to stay focused on individual events such as a specific problem they fixed, a specific contract they sold etc. This can be achieved by first asking the experts what the specific problem they resolved was, then asking for the actual cause of the problem (or most important characteristic for selecting the specific solution), and afterwards for the actual solution. Once the specific case has been identified, information regarding the problem solving process can be acquired by asking the expert which characteristics of the situation prompted him/her to select the given solution. These are the features that the subject matter expert needs to check before deciding which solution is most appropriate for the given scenario and form the basis for the application vocabulary. After an initial case has been entered, the developers should ask the expert for alternatives, e.g. what would have happened if the printer had been another model, and thereby expand the coverage of individual solutions or add terms to the vocabulary of the system and cases to the case-base.
68
M.H. Göker, C. Baudin, and M. Manago
Problem Nr : 816 Author: S. Itani
Homer Case Acquisition Date: 26.04.99 Verified by: J. Fleisch
Problem Description (Failure) Reason (Fault) Solution
Printer does print pages full of gibberish File is Postscript, Printer does not understand PS Send File to Postscript Printer, delete file from queue
What did you check to find out what the problem was ? Printer Model File Type
HP LJ 6L Postscript
Other Notes:
The reverse of this problem did also happen, somebody sent a PCL file to a pure PS printer
Fig. 7. Case acquisition form for areas where human experts are available
For application areas where no previous experience exists (e.g. a brand new design), analytical cases can be created by using an approach similar to Failure Mode and Effects Analysis (FMEA) [DIN25448]. A sample form for case entry is given in Figure 8.
Case Acquisition Date: 03/07/2001 Verified by: D.Choisel
Case Nr : 978 Author: M. Göker Analytical Case Description System Module: Module Function: Failure Mode: Observed Behavior: Fault: Diagnostic Steps: …. Solution:
Drum Particle Transfer Particles do not stick to drum Patchy Print-Out Worn out Drum Change Toner Cartridge and verify failure persists …. Replace Drum
Fig. 8. FMEA based creation of analytic cases
Development of Industrial Knowledge Management Applications with CBR
69
3.7 System Design During this task, the application is designed in accordance with the requirements specification. A reasonable development philosophy for knowledge management applications is that the tools should adapt to the user rather than the users having to change the way they work to facilitate the application. The application needs to become an extension of the users, a tool that enables them to work much more efficient and effectively. This applies to end-users of the applications as well as knowledge engineers, administrators and IT personnel. The following steps have to be performed: • Functional design (what the application is going to deliver) • User Interaction and workflow design o Query formulation o Result display o Authoring and Review workflow o Application workflow and detailed user rights design o Reporting design • Integration design • GUI Design according to corporate standards • Staging and publishing design • IT architecture design • Design of application test scenarios In the following sections, we will again only cover aspects of the design process that have major differences with routine IT system design, i.e. we will only cover Functional, user Interaction, Reporting and Integration Design.
Fig. 9. Free Text Query Entry
70
M.H. Göker, C. Baudin, and M. Manago
3.7.1 User Interaction and Workflow Design Query formulation In general, CBR applications provide three different modes of user interaction and will switch between and mix these interaction modalities depending on the information required to diagnose the current problem: Free Text Interaction, Guided Search (conversational interaction) and parametric search. • Free Text Interaction: This allows the end users to formulate their problems using free text. The system will parse their input according to the knowledge it has about the domain (vocabulary, domain model, synonyms, abbreviations, extraction rules) and extract features that can be used as a basis of a query (Figure 9). If there are ambiguities with respect to a value for an attribute (which value is meant or which attribute the value belongs to), the system will clarify by prompting the user (Figure 10). Before submitting the final query, the system will also give the option to review what it has understood.
Fig. 10. Clarification Questions
• Guided Search: Guided search (or conversational interaction) will prompt the users for information and guide them towards a solution in the most efficient manner (Figure 11). The question order is dynamically generated based on the content in the case-base and the answers the user has provided so far. Users are able to skip questions (e.g. for expensive or time consuming tests or irrelevant questions) and the system will dynamically re-compute the next most important question to arrive at a solution as efficiently as possible. Users do not perceive much difference between the clarification questions and guided questions.
Development of Industrial Knowledge Management Applications with CBR
•
71
Parametric Search: Rather than being guided or using natural language, experts may prefer to enter their query directly, down to the minute details, by using structured forms (Figure 12). Information is entered in structured forms using radio-buttons, drop-down boxed etc. (expert search). The values for attributes can be entered in any order the user desires and the problem can be described as specific as the user wants to. While this mode may overwhelm and confuse the inexperienced user, experts are able to specify their request in a very detailed manner, potentially even adding individual weights to specific attributes. This weight is on top of the weighting factors that can be set by the system administrator.
Users can start with one mode of interaction (e.g. free text) and if the system determines that the information the user has provided so far is insufficient to provide a small enough set of good solutions, it will switch to guided mode and prompt the user for more information Figure 13 shows a simple (and incomplete) interaction diagram of such a system. The system also needs the ability to pull information from other software (e.g. databases or CRM systems) and use this to complete and enhance the query.
Fig. 11. Guided Search
72
M.H. Göker, C. Baudin, and M. Manago
Fig. 12. Parametric Search Interface
Fig. 13. Sample interaction diagram
Development of Industrial Knowledge Management Applications with CBR
73
3.7.2 Result Display After the query has been specified and the system has retrieved potential solutions to the user’s query, the system has to present them. The presentation modality has to be selected according to the content that is presented and the operating environment of the application. As for any knowledge management application, it is important for a CBR application to explain the reasoning it uses to make its selections. One way of achieving this it to present the results in two steps: a comparison table (e.g. Figure 14) and a detail display (e.g. Figure 15).
Fig. 14. Comparison table for a PC search application
The comparison table includes the parameters that the user asked for and contrasts these with parameters of potential solutions. It highlights the differences and matching parameters and gives an overall similarity measure. A well designed, domain specific comparison table enables end users to follow the reasoning of the system. Increases their trust and allows them to see and choose between possible alternative solutions.
74
M.H. Göker, C. Baudin, and M. Manago
After the user has selected a specific solution, the details can be displayed in a detail display. The end user is also able to leave feedback regarding the individual case on the case detail page (Figure 15).
Fig. 15. Solution Details Page with Feedback Option
3.7.3 Management of “Out of Scope” Questions One of the typically neglected aspects in the development in the development of knowledge management applications is the question of how to handle questions that are outside of the scope of the application. While asking a diagnosis application for a restaurant recommendation may have some entertainment value if done on purpose, in mission critical environments, giving misleading answers to questions that the system has no knowledge about and is not designed to operate in can pose dangers. The system needs to know what it does not know and only provide answers when it is highly confident that the question it answers is within its area of expertise. Questions that the system does not feel confident enough to answer can be escalated to experts (Figure 16).
Development of Industrial Knowledge Management Applications with CBR
75
Fig. 16. Escalation of Out of Scope questions
3.7.4 Authoring and Review Workflow While every organization has different requirements, it seems to be good practice to enable authors to create new or modify existing cases buy using the same application that end users use to search for solutions. To avoid creating duplicate cases, authors should use the application to search for cases first. The similarity thresholds and number of cases that the application will return have to be specified in the design process. Once the authors have performed an initial search, they will have the ability to create a new case from the results table and to edit or delete a case from the case details display (Figure 17).
Fig. 17. Creation of a new case from the results table
76
M.H. Göker, C. Baudin, and M. Manago
Especially in corporate environments, the authoring of new solutions is not a trivial task and may require the involvement and approval of various departments ranging from marketing to legal. Typically, the query of an end user is escalated to a help desk operator or agent if the end user is not satisfied with the system’s response. The agent can create an initial version of a case and, if appropriate, send it back to the end user as a stop-gap measure. The initial solution will need to be reviewed in terms of technical correctness by a subject matter expert. Depending on the organization and application, once the subject matter expert has approved the solution, it may need to go through an approval by additional instances before being released to the general public (see Figure 18).
Resolved User Query
New Problem
End User Released Cases
Escalated User Query
Draft Reply to User
Additional Reviewer(s)
Agent Returned for Revision
Returned for Revision
Technically Approved Case
Draft Case
Subject Matter Expert
Fig. 18. Sample workflow for case creation
One approach to generate the company specific version of the workflow shown in Figure 18 is to analyze the available information and its flow for different user types. At any time while using the system, the user will be able to work on a new task (query the system, review a case etc.), have a repository available (a view of the case-base), can accept or forward a case (accept solution, initiate next process step) or return (reject) a case (Figure 19).
Development of Industrial Knowledge Management Applications with CBR
77
Accepted or forwarded Case
New Case
User Returned Case
Case Repository
Fig. 19. Information flow analysis for a generic user
Based on the generic information flow shown in Figure 19 the access rights and responsibilities for some typical user types are as follows:
Table 1. Information and flow for typical user types in a CBR application End User New Task (editable)
•
New query
Author • •
Case Repository (read only)
•
Reference Cases in Case-Base
•
Forwarded Case (Accepted)
•
Solution displayed on screen
•
Returned Case (Replied)
•
None
•
•
Subject Matter Knowledge Expert Supervisor Cases under • Cases under • Cases under Author Subject Matter Knowledge revision Expert revision Supervisor revision Cases rejected by • Cases rejected by Subject Knowledge • Technically Matter Experts Supervisors approved cases from Subject • Draft cases from Matter Experts Authors Reference Cases • Reference, Draft • Reference, Draft, in Case-Base and technically technically approved Cases approved as well Draft Cases in in same as approved but same application area not yet published application cases in relevant area application area. Draft case to • Technically • Reference case to be reviewed by approved case to be published for Subject Matter be reviewed by end users after Expert Knowledge next staging & Supervisor publishing None • Technically • Rejected case to rejected case to be returned back be sent back to to Subject Matter Author for Expert for review. review
The authoring and review workflow should be integrated with existing content management processed and applications within organizations. Content creators and reviewers should not be required to use multiple applications to access and review their solutions and be able to track the progress (approval status) of their cases (Figure 20).
78
M.H. Göker, C. Baudin, and M. Manago
Fig. 20. Status screen for authors
3.7.5 Detailed User Rights and Application Workflow Design For each user type in an application, the functionality and data the user has available at any state within the application will be different. To ensure that the parameters for similarities, cut-offs, visibility, available functionality and follow up pages are set correctly, a thorough analysis needs to be performed. Table 2 gives an overview of a sample analysis of the availability of functions and their parameters for each user for each page of an application. This table needs to be adapted for each application and environment. 3.7.6 Logging, Feedback and Reporting Design In addition to the maintenance that is typical for every software application, a case-based knowledge management system will require maintenance for each knowledge container [RB03, RBRe01, GöRB99]. The knowledge contained in these is an incomplete model of the real world. Whenever the real world changes, the model in the system has to be updated. The necessity for changes in the model may either arise from real changes in the world or from the learning effect associated with using the case-based system. Maintenance operations require information regarding the state of the knowledge containers. To acquire information about the state and quality of the vocabulary as well as interaction characteristics of the application, system logs that capture the interaction of the end user with the system can be generated and analyzed. Depending on the selected granularity, these logs can track every
No
My Cases page
Draft / rejected / under approval with approval progress
Author
Subject Matter Expert newly submitted / draft / rejected / under approval with approval progress
Knowledge Supervisor newly submitted / draft
Case Detail page View Actions
5 No limit Create New Case/Case Detail
No
No
No
Yes Yes Yes
No
Admin
Based on roles and case status. For End-User show Vehicle Issue + Case Verification path (Test) Escalate / accept OR Create New Create New Create New Create New reject diagnostic path Case/Open Case Case/Open Case Case/Open Case Case/Open (if accept go to soluCase tion page, if no go back to result page)
Search pages (switching between searches looses the information) Yes Yes Yes Yes Free Text Query Yes Yes Yes Yes Guide (with top list of cases) Yes Yes Yes Yes Expert (no weights) Based on roles Views Automatic switching between searches Yes when more than Yes when more than No No From Free Text Query to 3 cases above 100% 3 cases above 100% Guide Yes when more than Yes when more than No No From Expert to Guide 3 cases above 100% 3 cases above 100% 75% 70% No No Similarity Cut-off Table of results page (no icons, percentage score) Based on roles (upper can see lower) and visibility attributes (zone, dealer code, user ID) Visibility 5 5 5 5 Case/page 3 5 No limit No limit # of pages Escalate / Case Detail Create New Create New Create New Actions from query Case/Case Detail Case/Case Detail Case/Case Detail
End User
GUI
Table 2. Sample functionality and parameter analysis
Development of Industrial Knowledge Management Applications with CBR 79
End User
Admin page
Delete Case Handling
NA
NA
Open Case page (No Open Case page for End-User) NA View NA Save Action (only his own cases and rejected cases) NA Save As Action (for versioning) NA Delete Action (only his own cases and rejected cases) NA Additional Actions
GUI
Yes
Yes
Yes
Yes
Yes
Admin
NA
NA
NA
User management / Server monitoring / Links to logs.
Submit for Review Submit for Publish/Reject NA by Subject Matter Review by Expert KS/Reject Case will not be physically deleted from the database but the status of the case will be set to “delete”. Client will implement a batch process to wipe those cases out of the database on a regular basis.
Yes
Yes
Yes
Yes
Knowledge Supervisor
Yes
Subject Matter Expert
Based on roles and case status. Yes Yes
Author
Table 2. (continued)
80 M.H. Göker, C. Baudin, and M. Manago
Development of Industrial Knowledge Management Applications with CBR
81
interaction of the users with the system. The reports that are generated using this data will allow fine-tuning the interaction and retrieval parameters and provide feedback to engineering or product development. User feedback with respect to the systems behavior in general can provide valuable information regarding similarity settings as well as potential adaptation rules and vocabulary. Feedback regarding the individual cases can provide insight into the validity and suitability of the content. In addition to these transaction oriented reports, reports that analyze the knowledge content and coverage of the case-base in general can be generated and used to verify that there are no irrelevant, contradictory or redundant cases in the system. 3.7.7 System Integration A CBR system as a knowledge management tool is never a standalone application. The application is typically embedded or exchanges data with other applications. Considering possible interactions and integration points with other software as early as possible in the design process ensures that no costly re-writes are required at a later stage. Integration may require: • Ability to exchange information with third party tools via APIs, XML, databases etc. • Adherence to IT standards of the respective customer (from OS to Hardware to J2EE, Web- and Application servers as well as custom user interface widgets) • Ability to deploy on the “stable” software environment of the customer and the data transfer requirements associated with this environment. • Ability to deployment in multiple languages with the same content. • Ability to deployment in a staged (development, staging, publishing) environment with load-balancing and failover. This can be an especially critical point since modifications to the knowledge containers of the system will occur on the publishing server and requires a separate staging process for the knowledge containers. • Ability to use the database of the customer to store/access information • And, most of all, patience in discussions with the IT department for days/weeks.
4 Conclusion In this chapter, we described some of the experiences we gained while developing commercial Case-Based Reasoning Applications. We tried to convey what we found to be best practices, stressed the areas that we found to be different from standard software development and pointed out typical mistakes. The successful development, deployment and long term utilization of a CBR solution are only partially dependent on outstanding technology and a capable development team (both of which certainly help). To make a system a long term success, it has to be technically and organizationally integrated in the operating environment and leverage existing processes and data repositories. We also experienced that, among other factors, the continued availability of subject matter experts and technical personnel, the creation and execution of sustainable knowledge acquisition,
82
M.H. Göker, C. Baudin, and M. Manago
utilization and maintenance processes, the stability of the project team, and the continued, visible support of business stakeholders have considerable impact on the long term success of a project. We hope that by documenting some of the lessons we learned, we can provide practitioners a reference that they can leverage to develop and fine-tune their own approach.
References [BeAl03] Bergmann, R., Althoff, K.D., Breen, S., Göker, M., Manago, M., Traphöner, R., Wess, S.: Developing Industrial Case Based Reasoning Applications: The INRECA Methodology. In: Bergmann, R., Althoff, K.-D., Breen, S., Göker, M.H., Manago, M., Traphöner, R., Wess, S. (eds.) Developing Industrial Case-Based Reasoning Applications, 2nd edn. LNCS (LNAI), vol. 1612, pp. 85–98. Springer, Heidelberg (2003) [GöRB99] Göker, M., Roth-Berghofer, T.: The Development and Utilization of the CaseBased Help-Desk Support System HOMER. In: Engineering Applications of Artificial Intelligence, vol. 12(6), pp. 665–680. Elsevier Science, Amsterdam (1999) [Ri95] Richter, M.: Introduction. In: Lenz, M., Bartsch-Spörl, B., Burkhard, H.-D., Wess, S. (eds.) Case-Based Reasoning Technology. LNCS (LNAI), vol. 1400, pp. 1–15. Springer, Heidelberg (1995); Richter, M.: The Knowledge Contained in Similarity Measures (invited talk at ICCBR 1995), http://wwwagr.informatik.unikl.de/~lsa/CBR/Richtericcbr95remarks.html [DIN25448] DIN 25448: Ausfalleffektanalyse (Fehler-Möglichkeits- und -EinflußAnalyse) Deutsches Institut für Normung e.V.,Beuth Verlag GmbH, Berlin (1990) [RB03] Roth-Berghofer, T.: Knowledge Maintenance of Case-Based Reasoning Systems – The SIAM Methodology. Dissertationen zur künstlichen Intellignez DISKI 262, Akademische Verlagsgesellschaft Aka GmbH, Berlin (2003) [RBRe01] Roth-Berghofer, T., Reinartz, T.: MaMa: A maintenance manual for case-based reasoning systems. In: Aha, D.W., Watson, I. (eds.) ICCBR 2001. LNCS (LNAI), vol. 2080, pp. 452–466. Springer, Heidelberg (2001) [Be02] Bergmann, R.: Experience Management: Foundations, Development Methodology, and Internet-Based Applications. Springer, Heidelberg (2002) [Gu01] Gupta, K.M.: Taxonomic conversational case-based reasoning. In: Aha, D.W., Watson, I. (eds.) ICCBR 2001. LNCS (LNAI), vol. 2080, pp. 219–233. Springer, Heidelberg (2001) [GuAh03] Gupta, K.M., Aha, D.W.: A framework for incremental query formulation in mixed-initiative case-based reasoning. In: Ashley, K.D., Bridge, D.G. (eds.) ICCBR 2003. LNCS, vol. 2689, pp. 172–180. Springer, Heidelberg (2003) [GuAhSa02] Gupta, K.M., Aha, D.W., Sandhu, N.: Exploiting taxonomic and causal relations in conversational case retrieval. In: Craw, S., Preece, A.D. (eds.) ECCBR 2002. LNCS (LNAI), vol. 2416, pp. 133–147. Springer, Heidelberg (2002) [Rau91] Rau, L.F.: Extracting Company Names from Text. In: IEEE CH2967, August 1991, pp. 29–32 (1991) [HuBa97] Huffman, S., Baudin, C.: Notes Explorer: Toward Structured Retrieval in Semistructured Information Spaces. In: Proceedings of the 1997 IJCAI Conference, Nagoya Japan (1997) [CoLe96] Cowie, J., Lehnert, W.: Information Extraction. Communications of the ACM 39(1), 80–91 (1996)
Chapter 4
Case Based Reasoning for Supporting Strategy Decision Making in Small and Medium Enterprises Jerzy Surma Collegium of Business Administration Warsaw School of Economics Al. Niepodleglosci 162, 02-554 Warsaw, Poland [email protected] Abstract. The practice of strategic management proves that when the management board is strongly limited in its capacity to take rational actions, specifically in the context of great decision complexity and uncertainty, it is good practice to refer to experience through reasoning by analogy. In this paper we would like to concentrate on supporting strategic decisions for small and medium enterprises (SME). Complexity of analogy-based reasoning has its roots in an attempt to solve new problems basing on past cases from a different domain, while we will focus on case-based approach for a single domain. Therefore we have chosen a case-based reasoning as a suitable decision making paradigm. We present the STRATEGOS case-based reasoning system for supporting strategic decision making by SME management board. Making correct strategic decisions by CEO (Chief Executive Officer) is one of the greatest challenges of management. The evaluation of the STRATEGOS system by CEO’s is presented in order to justify that the real use of case-based reasoning and its implementation in the described system is a credible attempt to support this complex issue.
1 Introduction The practice of strategic management proves that when the management board is strongly limited in its capacity to take rational actions, specifically in the context of great decision complexity and uncertainty, it is good practice to refer to experience through reasoning by analogy [1]. As Thagard points out: “analogies can be computationally powerful in situations when conceptual and rule-based knowledge is not available” [2]. As regards strategic management statements in a similar vein is possible: “Reasoning by analogy is a common form of logic among business strategists. Facing a novel opportunity or predicament, strategists think back to some similar situation they have faced or heard about, and they apply the lessons from that previous experience” [3][4]. This approach seems to be reasonable especially in a turbulent environments. According to Courtney, in situations of S. Montani & L.C. Jain (Eds.): Successful Case-Based Reasoning Appl., SCI 305, pp. 83–96. © Springer-Verlag Berlin Heidelberg 2010 springerlink.com
84
J. Surma
true ambiguity (uncertainties are both unknown and unknowable), analogies and reference cases are able to support strategy decisions [5]. Using analogies seems to be the golden mean between the positioning school and the evolutionary school of strategic planning. In the case of the positioning school it helps to escape the unrealistic assumptions concerning the rationality of managerial decisions, while in the case of the evolutionary school it helps introduce rational elements in the “reactionary” and ad hoc actions of managers. This issue has been thoroughly discussed by Gavetti and Rivkin, who refer to the concepts of company’s plasticity and rationality in its search for the right strategic decisions [6].
2 Research and Implementation Problems In the mentioned context in strategy decision making the following questions are crucial: „Is it possible to form the company’s strategy adapting an existing strategy prepared for a similar company” ? The positive answer leads to two further questions: „What does it mean that two companies are similar and how can this similarity be measured” ? and „What adaptations (modifications) should be made for the adopted strategy to be acceptable” ? Using analogies in strategy planning has been thoroughly researched both by means of a case study analysis [6] and experimental research with the use of the NK-model [7]. Using the NK-model and referring to the concept of business landscape [8] made it possible to conduct formal research on using analogies in complex decision situations. This approach has been subject to criticism, which suggested referring to other paradigms and hybrid approaches to strategic reasoning [9]. The NK-model itself is also problematic, as it simplifies the reality in a significant way. The company and the decision landscape are represented in the form of a binary attribute vector, which by definition restricts the description of the represented fragment of reality. Representing knowledge on a company is a complex issue and it requires considering such elements as description using quantitative attributes, order and hierarchies in the value sets of qualitative attributes, using elements of object representation or semantic networks. It is also crucial to take into consideration the time factor in the context of the company’s life cycle and the changes of its “parameters” in time. A key issue in such a reasoning paradigm is the problem of adapting the solution to the new decision situation. The adaptation requires referring to general knowledge on the company, where knowledge is represented in the form of business rules which make it possible to verify the reliability of the solution and suggest modifications to the proposed solution. In the NK-model approach no reference is made to the ontology of the company, which means that solutions are not adapted. This flaw decreases the value of the discussed solution considerably. Another fundamental drawback of the NK-model is its computational complexity, it is NP-complete [10], which de facto renders it useless in real life business situations. In response to this criticism it should be emphasized that the initiators of applying this model in reasoning by analogy did not intend to build a support system for real life business decisions. The actual aim was to develop an environment for computer simulations confirming or discarding proposed research hypotheses.
Case Based Reasoning for Supporting Strategy Decision Making in SME
85
In this paper we would like to concentrate on supporting strategic decision in a real business situations. Complexity of analogy-based reasoning has its roots in an attempt to solve new problems basing on past cases from a different domain, while we will focus on case-based approach for a single domain. We would like to present STRATEGOS system, based on the case-based reasoning (CBR) framework, for supporting strategic decision making. The main user of this system should be a management board of member a given SME. The initial research on the first STRATEGOS prototype was successful [11], and then the whole system was implemented and formally described [12]. In the next section its architecture and functionality is presented.
3 Case-Based Reasoning as the Implementation Framework 3.1 The Main Idea The strategy planning problem might partially be solved by means of applying the case-based reasoning (CBR) approach. It results from the specific characteristics of these systems [13]. Firstly a particular case is the basic element of knowledge representation, not a rule as in expert systems. Subsequently, the acquisition of knowledge consists in analyzing the particular cases from past experience and therefore it is not necessary to establish rules in order to generalize knowledge. Secondly a relatively easy update/expansion of the system through adding new cases, which follows the process of remembering one’s experiences. And finally excellent and credible justification for the recommendations (solutions) for business users. These exceptionally favorable characteristics result, first of all, from expert knowledge gained through relying on specific, individual cases solved in the past. The great opportunity is based on the CBR working cycle reflecting reasoning by analogy [14]. However, so far there has been no thorough research on applying case-based reasoning to support strategic decision making. There has also been no reliable empirical research conducted to verify this approach and assess how useful it actually is in business practice. At the same time global consulting companies have been building systems of databases containing information on the projects they have carried out with a view to adapting them for new clients. First applications of this class of systems in management include ORCA [15] – a system supporting company restructuring processes during acquisitions and mergers, and ESAS [16] – a system supporting business strategy planning processes. Both approaches mentioned above were promising prototypes. 3.2 Knowledge Representation Case-based reasoning framework requires the three main components: case representation, general knowledge representation, and similarity measure for its functionality. The case representation should reflect the company itself (company
86
J. Surma
description), its market environment (context description), and one or more strategic decision taken in this particular situation. In order to established it properly we conduct some surveys with CEO’s of the selected SMEs. Based on those interviews and the empirical research on the case representation for SMEs [12] the following case structure and case features were established: Company description: market share, localization, products/services, number of employees, sales volume (trends in at least two years period), sales volume (export), EBITDA (trends in at least two years period). Context description: industry, industry life cycle phase, Porter five forces analysis (threat of substitute products, threat of the entry of new competitors, intensity of competitive rivalry, bargaining power of customers, bargaining power of suppliers). Strategic decision: context (short description of the subject), product/market decision based on the Ansoff matrix (product × market), positioning decision based on the Porter’s generic strategies, and implementing strategy: strategic initiatives description.
„Before” strategic action
“After” strategic action
Company description ‘
Company description “
Context description ‘
Context description “
Planned decisi
Strategic decision’
Planned decisions (suggested solution)
Strategic decision “
Realized decisions (confirmed solution)
Fig. 1. The STRATEGOS case representation
In the strategic decision section we have chosen the well-known and relatively intuitive strategic tools suitable and easy to use by SME CEOs. Additionally, every information included in the case representation might be enhanced with text, images, files, hyperlinks, etc. In order to represent the strategic decision process, which is time-based, the case representation is divided into two sections: “before”
Case Based Reasoning for Supporting Strategy Decision Making in SME
87
and “after” the strategic action, where the strategic action is a specific strategic decision - see fig. 1. The “before” section describes the situation of the company and the planned strategic decisions as at a specific moment. The “after” section describes the company later, when it is possible to see the results of the strategic decisions actually performed. The crucial issue is concern with general knowledge (domain ontology) representation. This knowledge is important during reuse phase of the CBR cycle. Due to this knowledge it is possible to adapt the proposed solution from a retrieved case to the new case. Unfortunately strategic decision process is extremely complex, and it is almost impossible to represent the ontology properly. Despite this in our approach we decided to use general knowledge as a warning system in situation when the solution proposed is unrealistic for formal reasons. There are the warning examples: Inappropriate case retrieval based on the rule: “if a new case company and a retrieved company are in the different industry life cycle phase then the proposed decisions might be wrong” Inappropriate proposed solution based on the rule “ if the company has just started to penetrate a market with current products and proposed decision is: intensive foreign market development then this is risky and unrealistic proposal” It is also important to define an appropriate similarity measure for the retrieval phase. Most of the case-based approaches retrieve a previous case based on the superficial syntactical similarities. The same is in the current STRATEGOS implementation where similarity measure merges the company and context description in one vector a =(a1, a2, …, an) of attribute values. Denote by Ai the domain of the i-th attribute, then similarity measure sim is: sim: A1 × A2 × … × An → [0,1] and similarity between the input case aI and retrieved case aR is: sim(aI, aR)
1
∑
, ∑
where wi є [0,1] is a weight of i-th attribute, and distance(aIi, aRi ) є [0,1] is a normalized Euclidean distance in the case of numeric attributes and the discrete distance measure (which takes the value 0 if aIi = aRi and 1 otherwise) in the case of categorical variables [17]. Due to this similarity measure it is possible to avoid “false analogies”, cases that are importantly dissimilar and not useful as a reference examples. 3.3 The CBR Cycle Based on the CBR cycle the whole STRATEGOS decision making functionality will be described. In the beginning the specific input problem is given by the SME management board. The task (problem) is to establish a proper strategic decision for their company (new case). The company is described by set of attributes
88
J. Surm ma
Fig. 2. The part off the input screen for the “new case” (STRATEGOS)
including the current co ontext description, The STRATEGOS problem solvinng cycle consist of 4 phases1: Retrieve The solution is retrieved from the case base basing on the similarity between a new case (see example off a new case on fig. 2) and cases already stored in the casse base. Similarity measure takes into account the attributes in the ‘before’ strateggic action section of the casse description (company and context) – see fig. 1. Thhe retrieved cases are shown n to the user ranked basing on the similarity value – seee fig.3. The user might takee them into account or decide to use the cases that werre searched manually. Due to t this user might be more convinced when the retrieveed cases are personally chossen. This approach confirms that STRATEGOS is only a decision supporting system. On the fig. 4 it is shown how a new case is comparre, he chosen retrieved case. Every choice is verified througgh attribute by attribute, to th the general knowledge, as a it was shown in the example “inappropriate case retrieval” warning in order to t avoid unrealistic proposals. 1
This reasoning cycle was firstly presented by the author during the SMS 29th Annuual 2 “Strategies in Uncertain World” as common ground preesInternational Conference 2009 entation: “Case-Based Reaasoning for Supporting Strategic Decision Making in Turbuleent Environments for SMEs”.
Case Based Reasoning for Su upporting Strategy Decision Making in SME
889
Fig. 3. The list of retrieved cased (STRATEGOS)
Fig. 4. The detaileed view on the chosen retrieved case (STRATEGOS)
Reuse After the retrieve phase it i is possible to establish a solution for a new case whicch is called then a solved caase – see fig.5. Informally a solved case structure is aas follows:
90
J. Surm ma
Solved case (section ‘Beforee’): • • •
Company descriptiion := new case company description Context description := new case context description Planned decision (suggested ( solution) is based on the decision suggested by retrieved case (sectio on ‘After’), general knowledge, user knowledge & experience
Solved case (section ‘After’)): empty in this phase
Fig. 5. The view on the straategic decision description in the retrieved case (STRATEGOS S)
It is important to undeerline that suggested solution (planned decision) is baseed mainly on strategic decisiion taken in reality in the retrieved case, as described iin the section ‘After’ – see example e on the fig.6. Of course the personal input of thhe user is extremely importaant, and he can add his own knowledge and experiencce. Frankly speaking the maiin goal of this phase is to give inspiration and to proposse rational choices based on n the retrieved cases to the management board. Finallly every proposed solution is i verified by the general knowledge, as it was shown iin the example “inappropriatte proposed solution” warning.
Case Based Reasoning for Su upporting Strategy Decision Making in SME
991
Fig. 6. The suggested solution (Ansoff matrix) for a new case (STRATEGOS)
Revise The solved case that was established in the previous phase has a planned strateggic decision placed in the ‘Before’ section of the case structure. This is kind of prooposal for a strategic action ns plan. The most important goal of the revision phase is to recognized what actually happened with that company after taken strateggic decision – see fig.7. Of course it is needed at least several months period in order to see any real effects. Formally F in the CBR cycle after revision phase a solveed case is treated as a tested//repaired case: Tested/repaired case (section n ‘Before’) - no change, the same as it is in the solved case Tested/repaired case (section n ‘After’): • • •
Company descriptiion := current situation which is influenced by the realized straategic decision and other internal (company) and external (market) factors Context description := current context description Realized decision (confirmed solution) is a decision taken in reality that is influ-enced by the plann ned decisions, real possibilities/budget, current market situation, organizational capability to perform planned actions, etc.
92
J. Surm ma
It is very important to tak ke user remarks concerning the reasons why the proposeed approach was successful or unsuccessful. Firstly to explain a divergence betweeen the planned and the finallly performed decisions. Secondly to enumerate the moost crucial factors (internal an nd external) that probably influenced the company situation (this kind of businesss knowledge, for instance the market analysis, might bbe added to the case as an attached a file). All those remarks are extremely important for a future case re-use by y other managers.
Fig. 7. The revised phase – establishing realized situation (STRATEGOS)
Retain Finally the tested/repaired d case is placed into the case base as a lesson learned foor the future re-use (a learn ned case). The case reflects the lesson learned: the ‘beefore’ section of the case reepresent the particular situation and the planned solution, and the ‘after’ section rep presents the real actions and what was the situation of thhe company after. The qualitty of learned cases is a crucial problem in the whole CB BR cycle, because quality of suggested solution directly depends on this. It should bbe emphasized that the lesso ons learned might be negative as well; it means that thhe company has taken wron ng strategic decisions, and this negative case might bbe retrieved from the case base as a “do not do the same” case. It should bbe
Case Based Reasoning for Supporting Strategy Decision Making in SME
93
mentioned that the company might be represented in the case base by a set of cases ordered in time (episode), so we can have the whole life-time history of the company led by the strategic decision. This is a problem of building dynamics memories is called in a literature episodic-based reasoning [18] [19], and is currently under development in STRATEGOS framework. As we can see, maturity and quality of STRATEGOS as a decision making tool for supporting real life decisions, is not only dependent on technical issues like similarity measure, knowledge representation, etc. The main issue is to gather a valuable set of cases, and this requires long and time consuming co-operation with management boards. This might be the largest obstacle, and we will return to this point in the conclusions.
4 Empirical Evaluation Empirical tests of STRATEGOS system were conducted based on pattern cases and real cases. Case base of the system was completed with 454 pattern cases prepared on the basis of standard knowledge in the field of strategic management. This technical evaluation of the STRATEGOS system was supplemented with quality research. The main user of the system is a CEO of a SME. In this context a survey among some selected CEOs was made. They were shown how a STRATEGOS system prototype works. The test group was selected by a target selection and it is composed by 33 CEOs of SMEs operating in IT and telecomm sectors. The sectors were selected so that the CEOs functioned in a strongly competitive and innovative market, posing significant strategic challenges. It is important to underline that 11 out of 33 CEOs analyzed head listed companies, which in turn involves a great level of transparency of that company and ongoing verification of CEO’s activities by the market. All analyzed CEOs were male, average age 42 years, of which 11 years as CEO. Everyone in the group (with six exceptions) was an engineer by education. Almost everyone admitted lack of formal education in basics of strategic management. Each of the CEOs was interviewed individually in the form of a structured interview, where in most cases answers to questions were recorded according to Likert’s scale2. Comments and remarks were also recorded. Each interview was divided into two parts. During the first part the CEOs were asked about sources of their strategic decisions. Questions asked to CEOs are presented in table 1. The factor analysis3 based on those questions gave very interested impact on understanding of the CEO strategy making. The first factor of strategic decisions was very clearly articulated. It is a profound lack of support and relation to any theory (questions 1, 4 ,5 respectively loadings value are: -0,82, - 0,87, -0,91). In this context the second factor becomes very important, namely an evolutionary approach to strategy implementation (question 2, loading value: 0,77) and inspiration of analogous business activities, not necessarily in the industry of a given CEO (question 9, loading value: 0,75. Such a result is also brought about by the lack of formal education, characteristic 2 3
From (1) definitely not, to (5) – definitely yes. Factor analysis: factor loadings, extraction: principal components.
94
J. Surma
of SME CEOs. The result is even stronger if we remember that it is based on CEOs’ own declaration, namely a situation when each of them tries to put himself in a most favourable light. The analysed CEOs asked directly about sources of their inspiration and selection of strategic decisions in overwhelming majority (68%) indicated their experience and intuition – see fig. 8. Again, a relatively large share of inspiration by actions of other companies. Inspiration here is understood both as imitating actions of one’s competitors and finding analogies in operations of companies in other industries. In this context the paradigm of decision support embedded in STRATEGOS system seems to go very well with the needs of managers and the way they think. This was confirmed by quality research made in the second part of the survey, where the analysed CEOs were confronted with the system and asked to evaluate it.
Table 1. List of judgments to evaluate for CEO’s Item 1 2 3 4 5 6 7 8 9
Judgment: „My strategy decisions are based on the formally planned strategy” are based on the strategy plan carefully revised by the current situation” are a kind of ad-hoc decision driven by the current situation” are taken based on my formal knowledge on strategy planning” are based on the specific strategy theory (paradigm)” are based on my intuition” are based on my experience and similar situation from the past” are based on imitation the similar companies in my sector” are based on inspiration by analogy from different businesses”
After the presentation of the entire work cycle of the system the analysed CEOs were asked to evaluate the system after the presentation of the entire work cycle of the system for a given demonstrative case – see fog.5. In table 2 a summary of answers is presented (4 key question, Likert’s scale).
Table 2. The STRATEGOS system evaluation by SME CEO’s Judgment This tool is supporting me in real strategy decision making This tool give me education in strategy decision making I understand the STRATEGOS problem solving life cycle This tool is giving me a solution for my strategic problems
Mean 4,37 4,21 4,75 1,56
SD 0,62 0,52 0,43 0,51
As transpires the evaluation results are very positive, the system was met with an outstanding reception. The results reflect the real-life approach of CEOs, where STRATEGOS is used as a system supporting strategic decisions, and not a system bossing around. CEOs very enthusiastically commented on functioning of the system, they also underlined their willingness to use it in real life, once the condition of adequate quality and capacity of data base is met.
Case Based Reasoning for Supporting Strategy Decision Making in SME
95
40.0% 35.0% 30.0% 25.0% 20.0% 15.0% 10.0% 5.0% 0.0%
Fig. 8. Sources of the strategy decisions pointed by SME CEO’s
5 Final Remarks Strategic management decisions are rooted in the sphere of emotions, intuition and unconsciousness, rather than the sphere of the rational. Every possible support to managers, which increases rationality of the decision making process, lowers the risk of decisions taken in the conditions of great uncertainty and improves the chance of eventual success. According to our experiments a very strong link was ascertained connecting experience and intuition in making strategic decisions, which is caused by many reasons, one of them being the lack of CEOs formal education of CEO. A proposition that in the entire SMEs CEO population this phenomenon would be even stronger seems justified. The CEOs analysed displayed humbleness towards experiences of other companies and many times they interpreted the case base as a sort of their own memory extension. The CEOs analysed combined acceptance of STRATEGOS with a strong feeling of limitation of reasoning appealing solely to analogies and experience. The analysed treated the system as an inspiration or a verification for their actions, being fully aware that every decision-making situation is unique and unrepeatable (see the last row in the table 2). As it was mentioned before the main problem is quantity and quality of the case base. We are going to develop the motivation system for SME managers to convince them to use STRATEGOS. One of the biggest obstacle is confidentiality problem. Nevertheless we are inspired by ADIRAS association (www.adiras.org) – SMEs board proposal, where manager-owners participate jointly –through ADIRAS- in the management of their organizations, assisted by an external facilitator. The whole framework is implemented and available for CEO’s as an advisory portal. Updated info about the project and the most recent version of the system can be retrieved at www.strategos.pl.
96
J. Surma
Acknowledgments. This research is financially supported by the Ministry of Science and Higher Education in the budget for 2008-2010 as a research project. I would like to thank my students Jakub Tomiczek and Mateusz Chrzęst, who implemented the STRATEGOS prototype as their master’s thesis written under my supervision.
References 1. Roberto, M.: Making Difficult Decisions in Turbulent Times. Ivey Business Journal (January/February 2002) 2. Thagard, P.: Mind: Introduction to Cognitive Science. MIT Press, Cambridge (1996) 3. Gavetti, G., Rivkin, J.: How Strategists Really Think. Harvard Business Review, 05 (2005) 4. Gavetti, G., Levinthal, D., Rivkin, J.: Strategy Making in Novel and Complex Worlds: The Power of Analogy. Strategic Management Journal 26 (2005) 5. Courtney, H.: 20/20Foresight, Creating Strategy in an Uncertain World. Harvard Business School Press, Boston (2001) 6. Gavetti, G., Rivkin, J.: Rationality and plasticity over time: toward a grounded theory of the origin of strategies. Working paper, Harvard Business School (2004) 7. Levinthal, D.: Adaptation on rugged landscapes. Management Science 43 (1997) 8. Ghemawat, P.: Strategy and Business Landscape. Pearson/Prentice Hall (2006) 9. Farjoun, M.: Strategy Making, Novelty and Analogical Reasoning – Commentary on Gavetti, Levinthal, and Rivkin. Strategic Management Journal 29(2008), 1001–1016 (2005) 10. Rivkin, J.: Imitation of complex strategies. Management Science 46, 824–844 (2000) 11. Surma, J.: Creating business strategy with the support of Business Intelligence. In: Proceedings of BIR 2008 - The 7th International Conference on Perspectives in Business Informatics Research. Gdansk University Press (2008) 12. Surma, J.: Supporting strategic decision making with case-based reasoning. International Journal of Business Insights and Transformation 2(1) (October 2009 - March 2010) 13. Kolodner, J.: Case Based Reasoning. Morgan Kaufmann, San Francisco (1993) 14. Aamodt, A., Plaza, E.: Case Based Reasoning: Foundational Issues, Methodological Variations, and System Approaches. In: AI Communications, vol. 7. IOS Press, Amsterdam (1994) 15. Bareiss, R., Slator, B.: From Protos to ORCA: Reflections on a unified approach to knowledge representation, categorization, and learning. In: Nakamura, Taraban, Medin (eds.) Categorization and Category Learning by Humans and Machines. Academic Press, San Diego (1993) 16. Frangou, A.: ESAS: A case-based approach to business planning and monitoring. Expert Systems 15(3) (1998) 17. Hullermeier, E.: Case-Based Approximate Reasoning. Springer, Heidelberg (2007) 18. Sanches-Marre, M., Cortes, U., Martinez, M., Comas, J., Rodriguez-Roda, I.: An Approach for Temporal Case-Based Reasoning: Episode-Based Reasoning. In: Muñoz-Ávila, H., Ricci, F. (eds.) ICCBR 2005. LNCS (LNAI), vol. 3620, pp. 465–476. Springer, Heidelberg (2005) 19. Montani, S., Portinale, L.: Accounting for the temporal dimension in case-based retrieval: a framework for medical applications. Computational Intelligence 22, 208–223 (2006)
Chapter 5
Heterogeneity in Ontological CBR Systems Amjad Abou Assali1 , Dominique Lenne1 , and Bruno Debray2 1
University of Technology of Compi`egne, CNRS HEUDIASYC {amjad.abou-assali,dominique.lenne}@utc.fr 2 INERIS [email protected]
Abstract. We present in this chapter our platform COBRA, an Ontology-based Case-based Reasoning (CBR) platform. We work currently on the diagnosis of the failures of gas sensors installed at industrial sites. COBRA allows to author and reuse past experiences in order to diagnose new failure situations. However, it can be used, in general, to develop CBR systems for classification tasks. COBRA is based on a knowledge base that integrates domain knowledge along with cases in an ontological structure, which enhances its semantic reasoning capacities. Users can describe their cases using instances from the knowledge base. The resulting case base is heterogeneous where cases do not always share the same attributes. We focus, in this chapter, on the problems of heterogeneity, and we present our case alignment approach allowing to treat this heterogeneity.
1 Introduction In industrial sites concerned by the Seveso-II directive [1], risks exist due to the presence of hazardous substances and processes. To reduce such risks, safety barriers are set up depending on the type of process and on the hazardous situation to control as well as on the local environmental conditions. However, barriers may not work properly, and thus hazards may arise. In such a situation, industrial experts intervene to diagnose the barriers failure basing mostly on past failure experiences occurred in similar situations. The hypothesis of experts here is that “if a barrier did not work correctly in a past similar situation, it is strongly probable that it does not work, in the current situation, for similar reasons”. This hypothesis leads us to a Case-Based Reasoning (CBR) approach [2]. CBR is a problem-solving approach used to solve a new problem by remembering a previous similar situation and by reusing information and knowledge of that situation [3]. We work currently on the diagnosis of the failures of gas sensors, safety devices that play an essential role in the functioning of safety barriers (such
Institut National de l’Environnement industriel et des RISques, France.
S. Montani & L.C. Jain (Eds.): Successful Case-Based Reasoning Appl., SCI 305, pp. 97–116. c Springer-Verlag Berlin Heidelberg 2010 springerlink.com
98
A.A. Assali, D. Lenne, and B. Debray
as emergency safety valves or automatic extinguishers) installed in industrial plants. Such sensors are intended to detect certain gases so that if there is a leak somewhere in the plant, a safety action can be undertaken either automatically or by means of a human intervention. Failures may arise due to a variety of reasons, some of which are often not obvious to the plant operator and therefore require the intervention of an expert. In this context, a CBR system is a helpful tool allowing to guide operators and experts through the diagnosis of new failure situations. A case represents a diagnosis of the failure of a gas sensor in a given industrial environment; i.e. the description of the environment where the sensor was installed, as well as the cause(s) of its failure. Due to the nature of our domain of application, cases attributes may vary from one diagnosis situation to another, which gives rise to a heterogeneous case base (in reference to the classification of Watson [4]). Cases heterogeneity complicates the case retrieval phase since no matching is defined a priori between query and cases attributes. In this chapter, we present the architecture of COBRA, our ontology-based CBR platform. This platform allows to develop CBR systems based on ontological models describing the domain and case structures. One of the interesting features of COBRA is that it allows a dynamic representation of cases; i.e. users can define the attributes (descriptors) of their cases at run time, which can lead to a heterogeneous case base. We introduce then our approach of case alignment that aims to overcome the heterogeneity problems.
2 Related Work The integration of general domain knowledge into CBR systems was an important aspect in several projects. In such an approach, called knowledgeintensive [5], the CBR reasoner exploits not only the case base, but also other types of knowledge related to the domain. In knowledge-intensive systems, knowledge are structured generally using ontologies. Recio-Garc`ıa et al. [6] identified different uses of ontologies in a CBR system. They can be used as the vocabulary to describe cases and queries, as a knowledge structure where cases are located, and as the knowledge source to achieve semantic reasoning methods for similarity assessment. In the Creek architecture [7], we find a strong coupling between case-related and domain knowledge. Creek contains three types of knowledge described by a densely linked semantic network: a generic ontology containing domainindependent concepts, a domain ontology, and knowledge related to cases. Fuchs and Mille proposed a CBR modeling at the knowledge level [8]. They distinguished four knowledge models: 1) the conceptual model containing the concepts used to describe the domain ontology regardless of the reasoning process; 2) the case model that separates the case into three parts: problem, solution, and reasoning trace; 3) the models describing the reasoning tasks; 4) and the reasoning support models.
Heterogeneity in Ontological CBR Systems
99
D`ıaz-Agudo and Gonz` alez-Calero [9] proposed a domain-independent architecture that helps in the integration of ontologies into CBR applications. Their approach is to build integrated systems that combine case specific knowledge with models of general domain knowledge. So, they presented CBROnto [10], a task/method ontology that provides the vocabulary for describing the elements involved in the CBR processes, and that allows to integrate different domain ontologies. CBROnto was reused later by jColibri, a powerful object-oriented framework for building CBR systems [6]. It splits the case base management into two concerns: persistence and in-memory organization, which allows different storage mediums of cases (text/xml files, ontology, etc.) accessed via specific connectors. However, jColibri does not allow the treatment of dynamic and heterogeneous case bases. In this work, we decided to keep the interesting aspects of jColibri, and to add our own layer that allows to work with heterogeneous case bases.
3 COBRA Architecture Several CBR architectures were presented in the literature. Aamodt and Plaza [3] presented the famous CBR cycle composed of the four processes: Retrieve, Reuse, Revise, Retain. A fifth process, Elaborate, was distinguished later [11], which consists in elaborating a new query for which similar cases are to be retrieved. Lamontagne and Lapalme [12] presented a global view of CBR systems where two parts can be seen: processes and knowledge containers used to preserve and exploit previous experiences. Inspired by these architectures, COBRA architecture is composed of two main parts (Fig. 1):
Fig. 1. COBRA architecture
100
A.A. Assali, D. Lenne, and B. Debray
– Processes: This is the functional part of the system and consists of off-line and on-line processes. The off-line processes include the case authoring and the adaptation knowledge acquisition processes. The on-line processes represent the reasoning cycle: elaborate, retrieve, adapt (reuse), enrich, validate, and retain. We distinguish here a new process, enrich, allowing the user to enrich the description of his problem until a solution is found. – Knowledge containers: A CBR system can be seen as a knowledge-based problem solving system. Richter [13] introduced the concept of knowledge containers that contain and structure the knowledge exploited by a casebased reasoner. This knowledge concerns the application domain as well as the problem solving methods employed. COBRA relies on four knowledge containers that were distinguished by Richter [13]: vocabulary, case base, similarity measures, and adaptation knowledge. The similarity measures are used to compute the similarity between cases attributes. The adaptation knowledge are used to construct solutions to new problems by reusing the solutions of past cases. To describe the vocabulary and the case base, our COBRA is based on two knowledge models: the domain and case models. These models are represented in an ontological structure to allow a better communication between the knowledge about the cases and the domain. 3.1
Domain Model
This model represents the knowledge about gas sensors, the current domain of application, in an ontological structure. However, there was a need to develop an ontology reusable across several domains of industrial safety. Thus, to clarify the types of ontologies to be developed, we followed the classification proposed by Oberle [14]. This classification distinguishes the ontologies according to three dimensions (Fig. 2): purpose (reference, application), expressiveness (lightweight, heavyweight), and specificity (generic, core, domain). Accordingly, two lightweight ontologies were developed [15]:
Fig. 2. Ontology classification dimensions by Oberle [14]
Heterogeneity in Ontological CBR Systems
101
1. A core ontology that contains generic concepts about industrial safety, such as Equipment, Dangerous phenomenon, Safety barrier, Effect, etc. This ontology allows using the set of general concepts across several domains by specializing them according to each domain. 2. A domain ontology about safety barriers, in particular gas sensors. The concepts of this ontology are specializations of other concepts in the core ontology (Fig. 3). Gas sensors are intended to work in specific environmental conditions (humidity, temperature, presence of dust, etc.) to perform a safety function which is to detect a leak of a hazardous gas in situ. Thus, the domain ontology contains concepts such as: Gas sensor, Safety function, Environmental condition, etc.
Fig. 3. Part of the domain model
3.2
Case Model
A case in our system represents a diagnosis experience, and thus it consists of three main parts: a description part describing the context of the experience, a failure mode part describing the type of failure, and a cause part describing the different possible causes of this failure. Let’s take, for example, the failure of gas sensors. The description part may contain: the gas to be measured, the sensor technology used (e.g. infrared, electrolytic), the concentration alarm threshold (i.e. at what concentration of the gas the sensor must give an alarm), etc. The failure mode can be of various types:
102
A.A. Assali, D. Lenne, and B. Debray
– a false alarm, such as: untimely alarm, too low alarm threshold, overestimated concentration, gas mistaken for another; – a failure to detect the gas, such as: failure to operate at all, underestimated concentration, too high alarm threshold, undetected gas; – a late detection when the sensor has a too long response time; – a failure to transmit the information. Moreover, the failure cause may correspond to: – – – –
an inadequate sensor’s technology; a contaminated gas sensor; a wrong calibration of sensors; an inadequate maintenance.
A case in general is described by a couple (problem, solution). According to our model, the description and failure mode parts correspond to the problem part, and the cause part corresponds to the solution part. Inspired by the approach of jColibri, in order to enhance the communication between the case base and the domain model, the case model is represented within an ontology that integrates the domain model [16]. This ontology contains the following main concepts (Fig. 4):
Fig. 4. Part of the case model
– cbr-case that subsumes the various case types that may exist in the system. – cbr-description that subsumes the case main parts, failure mode and cause.
Heterogeneity in Ontological CBR Systems
103
– cbr-index that allows to integrate the domain model concepts used to describe cases. Cases are thus represented as instances of the ontology and can have two types of attributes: – Simple attributes: which correspond to simple (data-type) properties of the ontology that have simple values, i.e. string, int, float, etc. – Complex attributes: which correspond to instances of the ontology that have, in turn, their own simple properties.
4 System Processes As seen before, our system contains two types of processes: off-line processes and on-line processes that represent the reasoning cycle allowing to construct a solution to a new problem (Fig. 5).
E la borate
Help list
Initial des cription
R etrieve
E nriched des cription
(guided by adaptability)
Adaptable C as es
Adapt
S olution(s)
V alidate
E nrich
No
S olution validated?
Y es
R etain
Fig. 5. COBRA on-line processes
This cycle begins with the elaboration of a new target problem from an initial description provided by the user. The retrieval phase is guided by the adaptability [17]; i.e. source cases are retrieved and weighted according to their adaptability level. This level is determined based on some adaptation knowledge that we acquire using a semi-automatic method (out of the
104
A.A. Assali, D. Lenne, and B. Debray
scope of this chapter). During the adaptation phase, a transformational adaptation [18, 19] is applied to construct candidate solutions using the source cases that were identified as adaptable. If no adaptable case is found (during the retrieval phase), or if the solutions proposed are not validated by the user (during the validation phase), the system asks the user to enrich the description of the target problem during the enrichment phase. This cycle is repeated until a good solution is proposed by the system and validated by the user. This solution as well as the target problem are retained in the case base as a new case. In this chapter, we describe the processes of case authoring, query elaborating, and case retrieval, in order to present the problem of heterogeneous case bases and our approach to solve it. 4.1
Case Authoring
To construct case bases, three ways are considered in the literature [20]. In this work, domain experts were asked to author cases in terms of their experience in failure diagnosis. On the other hand, cases were constructed from existing documentations that contain already known failure situations. Cases are authored using instances from the domain model. However, when we began to author cases, we realized that cases do not always share the same attributes, and thus, two objectives appeared in this phase: – First, experts must not be limited to a certain number of attributes to describe their experience. They have to be able to use any instance they need from the domain model. Consequently, the case base produced may be heterogeneous, which complicates the case retrieval phase. – Since different attributes can be used to describe a case, it will be helpful to guide the expert during the authoring of his experience. This is done by showing him a list of the most used instances that appeared in other similar cases ordered by their importance. Thus, the case base is an important source of help that can be exploited not only in the case retrieval phase, but also in the authoring phase. The constructed cases can be enriched with new attributes that are derived from existing attributes based on the relationships between attributes in the ontology and on a set of inference rules (Fig. 6), thanks to the inference engine of the Jena library1 . Let’s take, for example, a case where a “wet dust separator” (an equipment) exists. The presence of this equipment implicates the presence of dust (an environmental condition) in the environment, which is not explicitly described in the case. The “query elaborating” process is similar to that of the case authoring since the query structure is the same as the case structure. 1
http://jena.sourceforge.net/
Heterogeneity in Ontological CBR Systems
105
Fig. 6. Part of the inference rules
4.2
Case Retrieval and Heterogeneity Problems
For a given target problem, this process aims to retrieve the most relevant source cases that can be reused to construct a solution for this problem. The retrieval is guided by the adaptability [17]; i.e. a case is retrieved if its solution can be reused to construct a solution for the target problem. To determine adaptable cases, given a target problem, each attribute of the query must be compared to its corresponding attribute in each source case (Fig. 7).
Source problem
?
Target problem
b1
a2
b2
...
...
Retrieve
a1
Fig. 7. The problem of heterogeneity in the retrieval phase
In homogeneous case bases, all cases share the same predefined structure, and thus, corresponding attributes are already identified. On the other side, heterogeneous case bases contain cases that do not share a predefined structure (in terms of attributes), which complicates the retrieval process (Fig. 8). To solve the problems of heterogeneity, we propose the approach of case alignment.
106
A.A. Assali, D. Lenne, and B. Debray Query Solvent vapor
?
Water vapor
?
Hydrogen
Low humidity
?
?
...
Presence of dust
...
Methane
Infrared sensor
?
...
Case 2
Case 1
Fig. 8. No correspondences are predefined between query and cases attributes
5 Case Alignment Case alignment aims at finding correspondences, called mappings, between the attributes of cases, in general, or between the attributes of a case and a query (target problem). Definition 1. A case alignment is a process (Fig. 9), controlled by a matching operator, that takes as input two (or more) cases, C and C , and produces a set of mappings, denoted by M , between pairs of attributes q, q that belong to C and C respectively. An alignment may use an external resource in order to achieve the matching. This resource, in our case, is the domain ontology, denoted by O, which describes the vocabulary used to represent the cases.
C O
Matching operator
M
C' Fig. 9. Case alignment process
An alignment process is based on the similarity between cases attributes to determine their mappings. However, this procedure leads sometimes to ambiguous situations. We propose in this work an approach to align cases based on similarity, but also on the role of attributes that we introduce later. We present next the similarity measures that we used as well as the alignment approach.
Heterogeneity in Ontological CBR Systems
5.1
107
Similarity Measures
Generally, with object-oriented case structures, similarity measures follow the “local-global principle” [21, 22]: the goal is to determine the similarity between two objects, i.e. one object representing the case (or a part of it) and one object representing the query (or a part of it). For each simple attribute, a local similarity measure determines the similarity between the two attribute values, and for each complex attribute, a global (object) similarity measure is used. Then, the similarity values from the local and global similarity measures are aggregated to the global similarity between the objects being compared. From an ontological point of view, the similarity computation of two ontology concepts or instances can be divided into two components [21, 6]: a concept-based similarity (or inter-class similarity) that depends on the location of the concepts in the ontology, and a slot-based similarity (or intra-class similarity) that depends on the fillers of the common attributes between the compared objects. We do not pretend here to define new similarity measures. We use the measures presented in the literature that we found pertinent to our work. Let q, q be two instances of the ontology. The concept-based similarity, simcpt , is computed using the measure of Wu and Palmer [23] defined as follows: simcpt (q, q ) =
2 × prof (LCS(q, q )) prof (q) + prof (q )
(1)
where prof is the depth of a concept or an instance in the ontology hierarchy, and LCS is the Least Common Subsumer concept of two instances. In a special case, when q and q represent the same instance in the ontology, we have: prof (LCS(q, q )) = prof (q), and thus: simcpt (q, q ) = 1. The slot-based similarity measure, simslt is defined as follows: sim(q.s, q .s) simslt (q, q ) = s∈CS (2) |CS| where CS (Common Slots) is the set of common simple attributes of q and q , |CS| is its cardinality, q.s (or q .s) represents the simple attribute s of q (or q ), and sim(q.s, q .s) is the similarity between the two simple attributes. To compute this similarity, we have defined two calculation modes that can be associated to attributes: – ignore: for the properties that must not be taken into account in the similarity. – exact: a strict mode that allows to verify the equality of property values. By considering these modes, the similarity sim(q.s, q .s) is calculated as follows: 1 if (wq.s = exact) and (vq.s = vq .s ) sim(q.s, q .s) = 0 otherwise
108
A.A. Assali, D. Lenne, and B. Debray
where wq.s is the calculation mode associated ti the simple attribute q.s, and vq.s is the value of this attribute in q. The global similarity measure of q and q is given by the following formula [24]: sim(q, q ) = (1 − α) × simcpt (q, q ) + α × simslt (q, q )
(3)
where α is a parameter allowing to control the importance of the slot-based similarity in the calculation (at present, α = 0.4). 5.2
Similarity-Based Alignment
Let C, C two cases to be aligned. For each attribute q ∈ C, we consider that its corresponding attribute in C , denoted by q , is the attribute with which q has the maximum similarity; i.e. sim(q, q ) = max (sim(q, qi )), qi ∈ C , n ∈ N∗ 1in
(4)
Definition 2. A mapping is thus defined as a triplet q, q , s where s represents the degree of confidence associated to the mapping and corresponds to the similarity between q and q ; i.e. s = sim(q, q ). Taking into account the similarity between the two attributes (Formula 4) is not in itself sufficient, because it always happens to find q according to this definition while q may have no corresponding attribute in C . This problem appears particularly when C is not enough described; in other words, when C does not have enough attributes in its description. To overcome such a problem, we propose to compare the obtained similarity sim(q, q ) with the maximum similarity obtained for q within the whole case base. Let Ω = {Cj : 1 j k, k ∈ N∗ } be the case base, where Cj = {qjl : 1 l mj , mj ∈ N∗ }. We define the following condition to be verified in order to determine if q is the corresponding attribute to q or not: sim(q, q ) β max1jk,1lmj (sim(q, qjl ))
(5)
where β is a specific threshold calculated after experimentations (currently, β = 0.6). In addition to this condition, and in order to improve the results of an alignment process, we present the notions of similarity regions and role of attributes. Similarity Regions. We consider that the similarity measures are not always applicable to each pair of concepts or instances of the ontology. For example, a gas instance must not be compared at all with an equipment instance. To prevent such comparisons, we propose to define the notion of similarity regions (Fig. 10).
Heterogeneity in Ontological CBR Systems
109
Definition 3. A similarity region is a sub-hierarchy of the ontology where concepts and instances are comparable with each other. The definition of such regions is manual and depends on the target application. For example, in our application, a gas cannot be compared with a liquid. In other applications, if such comparisons were allowed, we can define a similarity region that includes the sub-hierarchies of both concepts “Gas” and “Liquid”.
Fig. 10. Example of similarity regions
Concerning the alignment process, before comparing a query attribute and a case attribute, it must be verified first if these two attributes belong to the same similarity region. 5.3
Role-Based Alignement
The alignment based solely on the similarity between attributes may sometimes give erroneous results. Let’s take, for example, the following excerpt of a case description: “At an industrial site, an infrared sensor was used to detect the methane. Other gases were present at the site such as the hydrogen. The sensor did not work as expected, and there was an explosion consequently”. Now, let’s suppose a query looking for cases where a gas sensor was used to detect the hydrogen. Following the similarity-based approach, we find that the hydrogen of the case is the attribute corresponding to the hydrogen of the query. However, it is not the aimed result since we look for the hydrogen when
110
A.A. Assali, D. Lenne, and B. Debray
it is the gas to be detected, which means that its corresponding attribute must be the methane. To solve this ambiguity, we propose to describe the role of case attributes that may give rise to ambiguous situations. For example, the hydrogen of the case is a gas present at site, and the methane is the gas to be detected. A role-based alignment aims thus to identify the attributes that have the same role and considers them as corresponding attributes. 5.4
Case Alignment Approach: An Overview
Our case alignment approach consists of two phases (Fig. 11): in the first phase, it determines the set of mappings, M1 , based on the roles of attributes (role-based alignment). In the second phase, it determines the set of mappings, M2 , using the similarity-based alignment for the attributes that are still not aligned after the first phase; i.e. the attributes whose role is not defined. Consequently, the overall set of mappings, denoted by M , is the union of M1 and M2 . Case Alignment
C C'
Role-based alignment
O
Not aligned attributes
Similarity Regions
Similarity-based alignment
M1
M
M2
Fig. 11. Case alignment approach
5.5
Illustrative Example
Let C, C be two cases to be aligned, and q, q two attributes that belong to C and C respectively. Our alignment approach is based on the following four elements: ➀ sim(q, q ) = max1in (sim(q, qi )), qi ∈ C , n ∈ N∗ ➁ (sim(q, q )/ maxsimall ) β, where maxsimall is the maximum similarity obtained for the attribute q within the whole case base. ➂ Similarity regions. ➃ Roles of attributes.
Heterogeneity in Ontological CBR Systems
111
We will show through the following example the interest of each of these elements in the alignment process. Let’s consider the cases in the following tables (Table 1) that we have simplified for this example.
Table 1. Simple cases about failures of gas sensors Case 1
Case 2
Attribute
Role
Attribute
PID sensor
---
Catharometer sensor
Role ---
Solvent vapor
Gas to be detected
Methane
Gas to be detected
Wet dust separator
Equipment
Water vapor
Gaz present at site
Failure to detect the gas
Failure mode
Solvent vapor
Gaz present at site
Fouling of sensor
Cause
False alarm
Failure mode
A gas causes interferences with the sensor
Cause
Case 3
Case 4
Attribute
Role
Attribute
Electrochemical sensor
---
Catharometer sensor
Role ---
Hydrogen
Gas to be detected
Hydrogen
Gas to be detected
Low humidity
Environmental condition
High humidity
Environmental condition
Failure to detect the gas
Failure mode
Failure to detect the gas
Failure mode
Drying of the cell
Cause
Inadequate sensor’s technology
Cause
Let’s suppose a query (Table 2) looking for cases where a PID sensor (Photoionisation sensor) was used to detect solvent vapors (a flammable gas). This sensor was installed in an environment with a presence of dust (environmental condition).
Table 2. A query example Query Attribute
Role
PID Sensor
---
Solvent vapor
Gas to be detected
Presence of dust
Environmental condition
By considering only the first element ➀, the table 3 shows the mappings found for each attribute of the query, and the similarity value for each mapping. We note in the first case the “presence of dust” that has been inferred, thanks to the inference rules, due to the presence of a “Wet dust separator”. Among the obtained results, we can note the following erroneous mappings: 1. The attribute “Presence of dust” does not correspond to the attributes found in the last three cases (i.e. “Water vapor”, “Low humidity”, “High humidity”); 2. For the “Solvent vapor” (gas to be detected) of the query, the “Solvent vapor” of the second case was found while it was a gas present in the site and not the gas to be detected (which is the methane in this case).
112
A.A. Assali, D. Lenne, and B. Debray Table 3. Results obtained by considering the first element ➀ Query
Attribute
Case 1 (1) Role
Case 2 (0,871)
Attribute
Similarity
Attribute
Case 3 (0,884)
Similarity
Attribute
Case 4 (0,884)
Similarity
Attribute
Similarity
0,778
Catharometer sensor
0,778
PID sensor
---
PID sensor
1
Catharometer sensor
0,778
Electrochemical sensor
Solvent vapor
Gas to be detected
Solvent vapor
1
Solvent vapor (Gaz present at site)
1
Hydrogen
0,833
Hydrogen
0,833
Presence of dust
Environmental condition
Presence of dust
1
Water vapor
0,364
Low humidity
0,615
High humidity
0,615
By applying the condition corresponding to the second element ➁, we eliminate the mapping Presence of dust, Water vapor found for the second case, as shown in the table 4. Table 4. Results obtained by considering the second element ➁ Query Attribute
Case 1 (1) Role
Attribute
Case 2 (0,717) Similarity
Attribute
Case 3 (0,884)
Similarity
Attribute
Case 4 (0,884)
Similarity
Attribute
Similarity
0,778
Catharometer sensor
0,778
PID sensor
---
PID sensor
1
Catharometer sensor
0,778
Electrochemical sensor
Solvent vapor
Gas to be detected
Solvent vapor
1
Solvent vapor (Gaz present at site)
1
Hydrogen
0,833
Hydrogen
0,833
1
---
---
Low humidity
0,615
High humidity
0,615
Presence of dust
Environmental Presence of dust condition
In the table 4, the attribute “Presence of dust” should not be compared to the attributes found for the last two cases (“Low humidity”, “High humidity”). We avoid such comparisons by defining similarity regions (the element ➂), which gives the results shown in the table 5.
Table 5. Results obtained by considering the similarity regions Query
Case 1 (1)
Case 2 (0,717)
Case 3 (0,692)
Case 4 (0,692)
Attribute
Role
Attribute
Similarity
Attribute
Similarity
Attribute
Similarity
Attribute
Similarity
PID sensor
---
PID sensor
1
Catharometer sensor
0,778
Electrochemical sensor
0,778
Catharometer sensor
0,778
Solvent vapor
Gas to be detected
Solvent vapor
1
Solvent vapor (Gaz present at site)
1
Hydrogen
0,833
Hydrogen
0,833
Presence of dust
Environmental condition
Presence of dust
1
---
---
---
---
---
---
Although the results have improved, the second problem highlighted earlier persists; i.e. we look for the “Solvent vapor” as a gas to be detected and not as a gas present at site, which means that its corresponding attribute in the second case should be the methane. Taking into account the roles of attributes (element ➃) allows us to solve such a problem, which gives the desired results in the table 6.
Heterogeneity in Ontological CBR Systems
113
Table 6. Results obtained by considering the roles of attributes Query Attribute
Case 1 (1) Role
Attribute
Case 2 (0,692)
Similarity
Attribute
Case 3 (0,692)
Similarity
Attribute
Case 4 (0,692)
Similarity
Attribute
Similarity
0,778
Catharometer sensor
0,778
PID sensor
---
PID sensor
1
Catharometer sensor
0,778
Electrochemical sensor
Solvent vapor
Gas to be detected
Solvent vapor
1
Méthane (Gaz to be detected)
0,833
Hydrogen
0,833
Hydrogen
0,833
Presence of dust
Environmental condition
Presence of dust
1
---
---
---
---
---
---
6 COBRA: Ontology-Based CBR Platform This work led to the development of COBRA (Conversational Ontology-based CBR plAtform), a domain-independent CBR platform (Fig. 12).
Fig. 12. COBRA platform
COBRA is developed in Java as an Eclipse-based2 application, thanks to the Rich Client Platform3 (RCP) framework. Thus, it benefits from several reusable functionalities of Eclipse. The platform contains the following main viewers (Fig. 12): the ontology explorer viewer (upper left side) that shows the domain ontology; the case base viewer (upper right side); the adaptable cases viewer; the help viewer 2 3
http://www.eclipse.org/ http://wiki.eclipse.org/index.php/Rich Client Platform
114
A.A. Assali, D. Lenne, and B. Debray
that shows the most used instances in the case base; and the properties viewer allowing to modify the attributes values of a selected case attribute. Case authoring is done by creating a new case, and then filling its simple attributes and/or adding instances from the ontology. The user can choose from existing instances and/or create and add new ones to the ontology. Thus, authoring cases allows also to enrich the knowledge base by new instances. The user can also associate roles to the case attributes if necessary. As seen in the figure 13, the platform is based on jColibri, but it extends it with a layer that allows the treatment of dynamic and heterogeneous case bases. Thanks to the platform architecture, developing a new CBR system is made by supplying its domain ontology and reconfiguring some XML files.
Fig. 13. COBRA modules
7 Conclusion In this chapter, we presented the architecture of our platform COBRA, an ontology-based CBR platform. COBRA allows developing CBR systems for classification tasks. It is currently used in the domain of gas sensors and aims to capitalize knowledge about gas sensor failures, and to provide support to experts and safety engineers to diagnose new failure situations. COBRA allows authoring heterogeneous case bases. However, this heterogeneity leads to difficulties in the case retrieval phase. To overcome theses difficulties, we proposed the approach of case alignment. This approach is based on the similarity between cases attributes, but also on the notions of similarity regions and roles of attributes. One of the main processes of COBRA is the adaptation process that allows to create solutions for new problems by adapting the solutions of past problems. This process is based on knowledge specific to the domain, which are usually difficult to acquire. Therefore, we proposed, in this work, a semiautomatic approach to acquire adaptation knowledge from the case base, which is out of the scope of this chapter.
Heterogeneity in Ontological CBR Systems
115
To evaluate COBRA and the proposed approaches, cases have been added to the case base. These cases correspond to real situations observed in industry or to tests realized in the Ineris during campaigns for qualification of sensors. The evaluation has been done on two phases: the first is a technical phase that allows an evaluation from a developer’s point of view. The other phase is done by users to evaluate the quality of results (diagnosis) returned by the system for some given queries. The first results of evaluation show that the approach of case alignment, including its elements (similarity regions, roles of attributes, etc.), can identify convenient mappings between the attributes. We intend now to realize other experiences with a larger case base, and to adapt COBRA to other domains of application. Acknowledgements. The present work has received the financial support of the French Ministry of Ecology and sustainable development. The authors also thank Mr. S´ebastien Bouchet (Ineris) for his active participation to the development of the gas sensor ontology and the case base.
References 1. EC: Council Directive 96/82/EC of 9 December 1996 on the control of majoraccident hazards involving dangerous substances (1996) Seveso-II-directive 2. Riesbeck, C., Schank, R.: Inside Case-Based Reasoning. Lawrence Erlbaum Associates, Mahwah (1989) 3. Aamodt, A., Plaza, E.: Case-Based Reasoning: Foundational Issues, Methodological Variations, and System Approaches. AI Communications 7, 39–59 (1994) 4. Watson, I.: Applying Knowledge Management: Techniques for Building Corporate Memories. Morgan Kaufmann, San Francisco (2003) 5. Aamodt, A.: A Knowledge-Intensive, Integrated Approach to Problem Solving and Sustained Learning. PhD thesis, University of Trondheim, Norway (1991) 6. Recio-Garc`ıa, J., D`ıaz-Agudo, B., Gonz` alez-Calero, P., Sanchez, A.: Ontology based CBR with jCOLIBRI. Applications and Innovations in Intelligent Systems 14, 149–162 (2006) 7. Aamodt, A.: Explanation-Driven Case-Based Reasoning. Lecture Notes In Computer Science, 274 (1994) 8. Fuchs, B., Mille, A.: Une mod´elisation au niveau connaissance du raisonnement a partir de cas. In: L’Harmattan (ed.) Ing´enierie des connaissances (2005) ` 9. D`ıaz-Agudo, B., Gonz` alez-Calero, P.: An architecture for knowledge intensive CBR systems. In: Blanzieri, E., Portinale, L. (eds.) EWCBR 2000. LNCS (LNAI), vol. 1898, pp. 37–48. Springer, Heidelberg (2000) 10. D`ıaz-Agudo, B., Gonz` alez-Calero, P.: CBROnto: a task/method ontology for CBR. In: Procs. of the 15th International FLAIRS, vol. 2, pp. 101–106 (2002) 11. Cordier, A., Fuchs, B., Mille, A.: Engineering and learning of adaptation knowledge in Case-Based Reasoning. In: Staab, S., Sv´ atek, V. (eds.) EKAW 2006. LNCS (LNAI), vol. 4248, pp. 303–317. Springer, Heidelberg (2006) 12. Lamontagne, L., Lapalme, G.: Raisonnement ` a base de cas textuels: Etat de l’art et perspectives. Revue d’intelligence artificielle 16, 339–366 (2002)
116
A.A. Assali, D. Lenne, and B. Debray
13. Richter, M.: The knowledge contained in similarity measures. In: Invited Talk at the First International Conference on Case-Based Reasoning(ICCBR 1995), Portugal (1995) 14. Oberle, D.: Ontologies. Semantic Web and Beyond, vol. 1, pp. 33–53. Springer, US (2006) 15. Abou Assali, A., Lenne, D., Debray, B.: Ontology Development for Industrial Risk Analysis. In: IEEE International Conference on Information & Communication Technologies: from Theory to Applications (ICTTA 2008), Damascus, Syria, pp. 1–5 (2008) 16. Abou Assali, A., Lenne, D., Debray, B.: Case Retrieval in Ontology-Based CBR Systems. In: Mertsching, B., Hund, M., Aziz, Z. (eds.) KI 2009. LNCS (LNAI), vol. 5803, pp. 564–571. Springer, Heidelberg (2009) (to appear) 17. Smyth, B., Keane, M.: Retrieving Adaptable Cases: The Role of Adaptation Knowledge in Case Retrieval. In: Wess, S., Richter, M., Althoff, K.-D. (eds.) EWCBR 1993. LNCS, vol. 837, pp. 209–220. Springer, Heidelberg (1994) 18. Carbonell, J.: Derivational Analogy and its Role in Problem Solving. In: Proceedings of the third Annual National Conference on Artificial Intelligence, AAAI 1983, Washington, D.C., USA, pp. 64–69 (1983) 19. Wilke, W., Bergmann, R.: Techniques and knowledge used for adaptation during case-based problem solving. In: Mira, J., Moonis, A., de Pobil, A.P. (eds.) IEA/AIE 1998. LNCS, vol. 1416, pp. 497–506. Springer, Heidelberg (1998) 20. Yang, C., Farley, B., Orchard, B.: Automated Case Creation and Management for Diagnostic CBR Systems. Applied Intelligence: The International Journal of Artificial Intelligence, Neural Networks and Complex Problem-Solving Technologies 28(1), 17–28 (2008) 21. Bergmann, R., Stahl, A.: Similarity Measures for Object-Oriented Case Representations. In: Smyth, B., Cunningham, P. (eds.) EWCBR 1998. LNCS (LNAI), vol. 1488, p. 25. Springer, Heidelberg (1998) 22. Richter, M.: Similarity. Studies in Computational Intelligence, vol. 73, pp. 25–90. Springer, Heidelberg (2008) 23. Wu, Z., Palmer, M.: Verbs Semantics and Lexical Selection. In: Proceedings of the 32nd Annual Meeting of the Association for Computational Linguistics, New Mexico, USA, pp. 133–138 (1994) 24. Zhang, K., Tang, J., Hong, M., Li, J., Wei, W.: Weighted Ontology-Based Search Exploiting Semantic Similarity. In: Zhou, X., Li, J., Shen, H.T., Kitsuregawa, M., Zhang, Y. (eds.) APWeb 2006. LNCS, vol. 3841, p. 498. Springer, Heidelberg (2006)
Chapter 6
The Adaptation Problem in Medical Case–Based Reasoning Systems Rainer Schmidt and Olga Vorobieva Institute for Medical Informatics and Biometry, University of Rostock, D-18055 Rostock, Germany [email protected]
Abstract. Case-Based Reasoning has become a successful technique for medical applications. However, one of the problems that prevent it from becoming even more wide spread in medicine is the difficulty of carrying out the adaptation task. In Case-Based Reasoning just very few general adaptation techniques exist. Furthermore, in medicine adaptation is often more difficult than in other domains, because usually more and complex features have to be considered. So, in medical applications adaptation usually requires domain specific adaptation rules. Over the years, we have developed a couple of medical case-based systems. In this chapter, we do not present all of them, but only those ones where adaptation was performed in an interesting way. This means, for example, why in specific situations specific adaptation techniques seem to be appropriate or why in other specific situations adaptation might even be rather simple. We do not only summarise our experiences with adaptation in medicine, but we want to elaborate typical medical adaptation problems and hope to indicate possibilities how to solve them.
1 Introduction Case-Based Reasoning (CBR) has become a successful technique for knowledgebased systems in many domains, whereas in medicine some more problems arise to use this technique. A CBR system has to solve two main tasks [1]: The first one is the retrieval, which is the search for or the calculation of similar cases. For this task much research has been undertaken. The basic retrieval algorithms for indexing [2], Nearest Neighbour match [3], pre-classification [4] etc. have already been developed some years ago and have been improved in the recent years. So, actually it has become correspondingly easy to find sophisticated CBR retrieval algorithms adequate for nearly every sort of application problem. The second task, the adaptation, means modifying a solution of a former similar case to fit for a current problem. If there are no important differences between a query case and a similar case, a solution transfer is sufficient. Sometimes just few substitutions are required, but usually adaptation is a complicated process. In the
S. Montani & L.C. Jain (Eds.): Successful Case-Based Reasoning Appl., SCI 305, pp. 117–141. © Springer-Verlag Berlin Heidelberg 2010 springerlink.com
118
R. Schmidt and O. Vorobieva
early 90th the focus of the CBR community lay on retrieval, in the late 90th CBR researchers investigated various aspects of adaptation. Though theories and models for adaptation [e.g. 5, 6] have been developed, adaptation is still domain dependent. Usually, for each application specific adaptation rules have to be generated. Since adaptation is even more difficult in medicine, we want to elaborate typical medical adaptation problems and we hope to indicate possibilities how to solve them. This chapter is organized as follows. In the next section it is reviewed how adaptation is handled in medical CBR systems. In section 3 four medical CBR systems are presented, which deal with typical tasks and apply different adaptation techniques: adaptation rules for diagnosis, constraints for therapy advice, and compositional adaptation for course analysis. In section 4 therapy support programs for the endocrine domain are presented. Based on these programs an adaptation model for therapy support is developed in section 5. For the other main medical task, diagnosis, we were not able to develop such a model, partly because just one of our systems performs diagnosis and maybe because domain specific adaptation rules might be the most appropriate adaptation technique for diagnostic applications.
2 Medical Case–Based Reasoning Systems Though CBR has not become as successful in medicine as in some other domains so far, several medical systems have already been developed which at least apply parts of the Case-Based Reasoning method. Here we do not want to give a review of all these systems (for that see [7, 8, 9]), but we intend to show the main developments concerning adaptation in this area. In section 3 the adaptation techniques are illustrated by medical CBR systems serving as examples. 2.1 Avoiding the Adaptation Task Some CBR systems avoid the adaptation task. They do not apply the complete CBR method, but only a part of it, namely the retrieval. These systems can be divided into two groups, retrieval-only systems and multi modal reasoning systems. Retrieval-only systems are often used for image interpretation, which is mainly a classification task [10]. However, retrieval-only systems are also used for other visualisation tasks, e.g. for the development of kidney function courses [11] and for hepatitic surgery [12]. Multi modal reasoning systems apply parts of different reasoning methods. From CBR they usually incorporate the retrieval step, often to calculate or support evidences [13], e.g. in CARE-PARTNER [14] CBR retrieval is used to search for similar cases to support evidences for a rule-based program. A retrieval-only system for kidney function course analysis and prediction [15] is presented in section 3.1.
The Adaptation Problem in Medical Case–Based Reasoning Systems
119
2.2 Solving the Adaptation Problem So far, only a few medical systems have been developed that apply the complete CBR method. In these systems three main techniques are used for adaptation: adaptation operators or rules, constraints, and compositional adaptation. Furthermore, abstracting from specific single cases to more general prototypical cases sometimes supports the adaptation. Adaptation rules and operators. One of the earliest medical expert systems that uses CBR techniques is CASEY [16]. It deals with heart failure diagnosis. The most interesting aspect of CASEY is the ambitious attempt to solve the adaptation task. Since the creation of a complete rule base for adaptation was too time consuming, a few general operators are used to solve the adaptation task. Since many features have to be considered in the heart failure domain and since consequently many differences between cases can occur, not all differences between former similar cases and a query case can be handled by the developed general adaptation operators. So, if no similar case can be found or if adaptation fails, CASEY uses a rule-based domain theory. Another example for applying adaptation rules is a diagnostic program concerning dysmorphic syndromes [17]. The retrieval provides a list of prototypes sorted according to their similarity in respect to the current patient. Each prototype defines a diagnosis (dysmorphic syndrome) and represents the typical features for this diagnosis. The provided list of prototypes is checked by a set of adaptation rules. These rules state that some features of the patient either contradict or support specific prototypes (diagnoses). This system is presented in section 3.2. However, the development of complete adaptation rule bases never became a successful technique to solve the adaptation problem in medical CBR systems, because very often the bottleneck for rule-based medical expert systems, the knowledge acquisition, occurs again. Constraints. A more successful technique is the application of constraints. In ICONS, an antibiotics therapy adviser [18], adaptation is rather easy. It is just a reduction of a list of solutions (recommended therapies for a similar, retrieved case) by constraints (contraindications of the query patient). This system is presented in section 3.3. A typical task for applying constraints is menu planing [19], where different requirements have to be served: special diets and individual factors, not only personal preferences, but also contraindications and demands based on various complications. Compositional adaptation. A further successful adaptation technique is compositional adaptation [20]. In TA3-IVF [21], a system to modify in vitro fertilisation treatment plans, relevant similar cases are retrieved and compositional adaptation is used to compute weighted averages for the solution attributes. In TeCoMed [22], an early warning system concerning threatening influenza waves, which is presented in section 3.4, compositional adaptation is applied on the most similar former courses to decide whether a warning against an influenza wave is appropriate.
120
R. Schmidt and O. Vorobieva
Abstraction. Since one reason for the adaptation problem is the extreme specificity of single cases, the generalisation from single cases into abstracted prototypes [18] or classes [23] may support the adaptation. The idea of generating more abstract cases is typical for the medical domain, because (proto-) typical cases directly correspond to (proto-) typical diagnoses or therapies. In MNAOMIA [23], a hierarchy of classes, cases, and concepts with few layers is used. MEDIC [24], a diagnostic reasoner on the domain of pulmonology, consists of a multi-layered hierarchy of schemata, of scenes, and of memory organisation packets of individual cases.
3 CBR Systems and Adaptation In this section, the adaptation techniques mentioned before are illustrated within medical CBR systems. At first, a retrieval–only system for the kidney function is presented. It is followed by a system for the diagnosis of dysmorphic syndromes, where adaptation rules are applied, the ICONS system for antibiotic therapy advice, where constraints are used for adaptation, and finally the TeCoMed systems that deals with the prediction of disease outbreaks, where compositional adaptation is performed. 3.1 Retrieval-Only for the Kidney Function Up to 60% of the body mass of an adult person consists of water. The electrolytes dissolved in body water are of great importance for an adequate cell function. The human body tends to balance the fluid and electrolyte situation. But intensive care patients are often no longer able to maintain adequate fluid and electrolyte balances themselves due to impaired organ functions, e.g. renal failure, or medical treatment, e.g. parental nutrition of mechanically ventilated patients. Therefore physicians need objective criteria for the monitoring of fluid and electrolyte balances and for choosing therapeutic interventions if necessary. At the ICU in Munich, physicians daily get a printed renal report from the monitoring system NIMON [25] which consists of 13 measured and 33 calculated parameters of those patients where renal function monitoring is applied. The urine osmolality and the plasma osmolality, for example, are measured parameters that are used to calculate the osmolar clearance and the osmolar excretion. The interpretation of all reported parameters is quite complex and needs special knowledge of the renal physiology. The aim of our knowledge-based system is to give an automatic interpretation of the renal state to elicit impairments of the kidney function in time and to give early warnings against forthcoming kidney failures. So, when we started building a system for course analysis and prediction of the kidney function, we were confronted with a domain where the domain theory is extremely incomplete and no standards were known. Since traditional time series techniques [26] work well with known periodicity, but do not fit in domains characterised by possibilities of abrupt changes, much research has been performed in
The Adaptation Problem in Medical Case–Based Reasoning Systems
121
the field of medical temporal course analysis. However, the methods developed so far either require a complete domain theory or well-known standards (e.g. course pattern or periodicity). An ability of RÉSUMÉ [27] is the abstraction of many parameters into one single parameter and to analyse courses of this abstracted parameter. However, interpretation of these courses requires complete domain knowledge. Haimowitz and Kohane [28] compare many parameters of current courses with well-known standards (trend templates). In the recent years, the group of Stefania Montani and Luigi Portinale has developed another method that combines temporal abstraction with CBR retrieval [29, 30] which was especially applied on haemodyalisis [31]. Furthermore, the group of Peter Funk has applied CBR on medical time series [32], which is not the same problem as we intended to solve but somehow similar. So, we had to design our own method. We combined the idea of RÉSUMÉ [27] to abstract many parameters into one single parameter with the idea of Haimowitz and Kohane [28] to compare many parameters of current courses with well-known standards. Since well-known standards were not available, we used former similar cases instead. The idea is to search with CBR retrieval methods for former patients with similar courses and to consider their course continuations as possible prognosis for a query patient. We propose a prognostic model for multi-parametric time courses that combines two abstraction steps with Case-Based Reasoning (figure 1).
Measured and Calculated Parameters
State Abstraction Course of Kidney Function States
Time Abstraction Trend Descriptions
CBR - Retrieval Similar Courses serve as Prognoses Fig. 1. Prognostic model for time course
122
R. Schmidt and O. Vorobieva
The first step is a state abstraction from a set of parameter values to a single kidney function state. Therefor few requirements have to be met. Meaningful states to describe the parameter sets and a hierarchy of the states must exist. Furthermore, knowledge to define them must be available. The second abstraction means to describe a course of states. An often-realized idea is to use different trend descriptions for different periods of time, e.g. shortterm or long-term trend descriptions etc. [e.g. 33]. The third step means CBR retrieval. Since all attributes have ordered, nominal values, CBR-Retrieval-Nets [34], which are based on Spreading Activation [35], are appropriate. Example. The following kidney function states may be observed in this temporal sequence (figure 2): selective tubular damage, reduced kidney function, reduced kidney function, selective tubular damage, reduced kidney function, reduced kidney function, sharply reduced kidney function So we get these six state transitions: decreasing, steady, increasing, decreasing, steady, decreasing with these trend descriptions: current state: sharply reduced kidney function T1: decreasing, reduced kidney function, one transition T2: decreasing, selective tubular damage, three transitions T3: fluctuating, selective tubular damage, six transitions T4:1.23 In this example, the short-term trend description T1 assesses the current state transition as “decreasing” from a “reduced kidney function” to a “sharply reduced kidney function”. Since the medium-term trend description T2 accumulates steady state transitions, T2 determines a “decrease” in the last four days from a “selective tubular damage” to a “sharply reduced kidney function”. The long-term trend description T3 assesses the entire course of seven days as “fluctuating”, because there is only one increasing state transition and the difference between the severity values of a “selective tubular damage” and a “sharply reduced kidney function” equals two. The following similar course (figure 2) with these transitions is retrieved: decreasing, increasing, decreasing, steady, steady, decreasing with these trend descriptions: current state: sharply reduced kidney function T1: decreasing, reduced kidney function, one transition T2: decreasing, selective tubular damage, four transitions T3: fluctuating, selective tubular damage, six transitions T4: 1.17
The Adaptation Problem in Medical Case–Based Reasoning Systems
123
Both courses are shown in a comparative way to the user (figure 2). After another day with a “sharply reduced kidney function” the patient belonging to the similar course had a kidney failure. The physician may notice this as a warning and it is up to him to interpret it. Adaptation. In our system, the user can get additional information, e.g. about courses of the original measured data or about the typicality of the presented similar courses. However, the system does not perform any adaptation. This would lead in an automatic decision. Since no complete knowledge exists in this domain, adaptation rules or constraints are not available and consequently not applicable. In a similar situation, the TeCoMed system (see section 3.4) uses compositional adaptation and provides automatic warnings if necessary. This might be also possible for the kidney function. We did not implement such a decision, because the doctors with whom we were co-operating did not accept this idea. They insisted on the responsibility of the doctors (users) for such a decision.
Fig. 2. Comparative presentation of a current and a similar course
124
R. Schmidt and O. Vorobieva
In the lower part of each course the (abbreviated) kidney function states are depicted. The upper part of each course shows the deduced trend descriptions. 3.2 Adaptation Rules for Dysmorphic Diagnosis When a child is born with dysmorphic features or with multiple congenital malformations or if mental retardation is observed at a later stage, finding the correct diagnosis is extremely important. Knowledge of the nature and the etiology of the disease enables the pediatrician to predict the patient’s future course. So, an initial goal for medical specialists is to diagnose a patient to a recognized syndrome. Genetic counseling and a course of treatments may