Case-Based Reasoning P R I N C I P L E S & P R A C T I C E CBRCBR.

Slides:



Advertisements
Similar presentations
Rolls-Royce supported University Technology Centre in Control and Systems Engineering UK e-Science DAME Project Alex Shenfield
Advertisements

Chapter 1: Introduction
25 February 2009Instructor: Tasneem Darwish1 University of Palestine Faculty of Applied Engineering and Urban Planning Software Engineering Department.
Imbalanced data David Kauchak CS 451 – Fall 2013.
Case Tools Trisha Cummings. Our Definition of CASE  CASE is the use of computer-based support in the software development process.  A CASE tool is a.
Application of Inductive Learning and Case-Based Reasoning for Troubleshooting Industrial Machines - Michel Manago and Eric Auriol 컴퓨터공학과 신수용.
Chapter 11 Artificial Intelligence and Expert Systems.
1 / 24 CS 425/625 Software Engineering Software Evolution Based on Chapter 21 of the textbook [SE-8] Ian Sommerville, Software Engineering, 8 th Ed., Addison-Wesley,
Knowledge Acquisitioning. Definition The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development.
Case-based Reasoning System (CBR)
Managing Reuse Presented by: Aisha Al-Hammadi. Outline Introduction History. The technical and managerial advantages of Reusing Solutions. The main challenges.
(c) 2007 Mauro Pezzè & Michal Young Ch 1, slide 1 Software Test and Analysis in a Nutshell.
MSIS 110: Introduction to Computers; Instructor: S. Mathiyalakan1 Specialized Business Information Systems Chapter 11.
Building Knowledge-Driven DSS and Mining Data
Software Architecture Quality. Outline Importance of assessing software architecture Better predict the quality of the system to be built How to improve.
A Web-based Intelligent Hybrid System for Fault Diagnosis Gunjan Jha Research Student Nanyang Technological University Singapore.
CSC230 Software Design (Engineering)
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 11 Slide 1 Architectural Design.
Data Structures and Programming.  John Edgar2.
CS Machine Learning. What is Machine Learning? Adapt to / learn from data  To optimize a performance function Can be used to:  Extract knowledge.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
Becerra-Fernandez, et al. -- Knowledge Management 1/e -- © 2004 Prentice Hall Chapter 16 Knowledge Application Systems: Systems that Utilize Knowledge.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements l.
Database Systems: Design, Implementation, and Management Ninth Edition
CS3500 Software Engineering How does a “program” differ from a “software system”? Program System Tens to hundreds of lines of code Thousands to millions.
Copyright R. Weber Machine Learning, Data Mining ISYS370 Dr. R. Weber.
Object-Oriented Software Engineering Practical Software Development using UML and Java Chapter 1: Software and Software Engineering.
Fault Diagnosis System for Wireless Sensor Networks Praharshana Perera Supervisors: Luciana Moreira Sá de Souza Christian Decker.
European Network of Excellence in AI Planning Intelligent Planning & Scheduling An Innovative Software Technology Susanne Biundo.
Case Base Maintenance(CBM) Fabiana Prabhakar CSE 435 November 6, 2006.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 6 Slide 1 Requirements Engineering Processes l Processes used to discover, analyse and.
University of Dublin Trinity College Localisation and Personalisation: Dynamic Retrieval & Adaptation of Multi-lingual Multimedia Content Prof Vincent.
 Knowledge Acquisition  Machine Learning. The transfer and transformation of potential problem solving expertise from some knowledge source to a program.
Introduction: Databases and Database Users
CBR for Fault Analysis in DAME Max Ong University of Sheffield.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
1 ENTROPY-BASED CONCEPT SHIFT DETECTION PETER VORBURGER, ABRAHAM BERNSTEIN IEEE ICDM 2006 Speaker: Li HueiJyun Advisor: Koh JiaLing Date:2007/11/6 1.
This chapter is extracted from Sommerville’s slides. Text book chapter
Model-Driven Analysis Frameworks for Embedded Systems George Edwards USC Center for Systems and Software Engineering
CSE 219 Computer Science III Program Design Principles.
INTERACTIVE ANALYSIS OF COMPUTER CRIMES PRESENTED FOR CS-689 ON 10/12/2000 BY NAGAKALYANA ESKALA.
소프트웨어공학 강좌 1 Chap 7. Software Prototyping - Rapid software development to validate requirements -
Configuration Systems - CSE Sudhan Kanitkar.
OBTAINING QUALITY MILL PERFORMANCE Dan Miller
1 Introduction to Software Engineering Lecture 1.
Tutoring & Help System CSE-435 Nicolas Frantzen CSE-435 Nicolas Frantzen.
What is Software Engineering? The discipline of designing, creating, and maintaining software by applying technologies and practices from computer science,
March 1999Dip HI KBS1 Knowledge-based Systems Alternatives to Rules.
1 CSCD 326 Data Structures I Software Design. 2 The Software Life Cycle 1. Specification 2. Design 3. Risk Analysis 4. Verification 5. Coding 6. Testing.
Software Prototyping Rapid software development to validate requirements.
Formal Methods in Software Engineering Credit Hours: 3+0 By: Qaisar Javaid Assistant Professor.
Software Maintenance Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
1 Knowledge Acquisition and Learning by Experience – The Role of Case-Specific Knowledge Knowledge modeling and acquisition Learning by experience Framework.
Artificial Intelligence, Expert Systems, and Neural Networks Group 10 Cameron Kinard Leaundre Zeno Heath Carley Megan Wiedmaier.
Distributed Models for Decision Support Jose Cuena & Sascha Ossowski Pesented by: Gal Moshitch & Rica Gonen.
CSE 303 – Software Design and Architecture
Requirements Engineering Requirements Engineering in Agile Methods Lecture-28.
20. september 2006TDT55 - Case-based reasoning1 Retrieval, reuse, revision, and retention in case-based reasoning.
Data Mining and Decision Support
ITEC 1010 Information and Organizations Chapter V Expert Systems.
A Validation System for the Complex Event Processing Directives of the ATLAS Shifter Assistant Tool G. Anders (CERN), G. Avolio (CERN), A. Kazarov (PNPI),
Tutoring & Help Systems Deepthi Bollu for CSE495 10/31/2003.
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
3.3. Case-Based Reasoning (CBR)
Introduction Edited by Enas Naffar using the following textbooks: - A concise introduction to Software Engineering - Software Engineering for students-
Model-Driven Analysis Frameworks for Embedded Systems
CS 425/625 Software Engineering Software Evolution
Authors: Barry Smyth, Mark T. Keane, Padraig Cunningham
Software Maintenance Part1 Introduction. Outlines What Is Software Maintenance Purposes of Maintenance Why We Need It Maintenance Difficilties Some Tips.
Presentation transcript:

Case-Based Reasoning P R I N C I P L E S & P R A C T I C E CBRCBR

Outline An Introduction to Case-Based Reasoning Standard CBR Model Research & Applications Limitations & Extensions The Future...

Introducing Case-Based Reasoning Motivations The Standard CBR Model A Case Study The Story So Far...

Motivating CBR Regularity The world is a regular place - similar problems have similar solutions. Repetition The world is a repetitive place - similar problems tend to recur. Availability of Cases

The Standard CBR Model Target Problem Case-Base Retrieval AdaptationLearning

Property Valuation: A Case Study Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: PRICE: Bungalow Co. Wicklow 3 2 1/3 Acre New Excellent ? Solution Rule-based Approach? Correct & Consistent Rules?

Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: Bungalow Co. Wicklow 3 2 1/3 Acre New Excellent Target Problem Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: Price: Bungalow Co. Wicklow 3 2 1/4 Acre 5 Years Excellent £85,000 Case Simple Similarity Count the matching features to compute a score...

Retrieving Similar Cases Target Problem 85% 70% 65% 50% 40% 85% Similar Cases Select the best matching case (highest score)...

Adapting the Best Case Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: Price: Bungalow Co. Wicklow 3 2 1/3 Acre New Excellent £100,000 Target Problem Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: Price: Bungalow Co. Wicklow 3 2 1/4 Acre 5 Years Excellent £85,000 Case Price + £10k Price + £5k Modify the case’s price to account for mismatches...

Potential Advantages Problem Solving Efficiency Reuse vs First-Principles Knowledge Engineering Effort Acquiring & Maintaining Cases User Acceptance Embedded Systems vs Case-Based Assistants

Application Areas Classification & Prediction Credit Card Fraud Detection, Property Valuation Diagnosis & Decision Support Help-Desk Support, Fault Diagnosis, Air Traffic Control Planning & Design Automatic Software Design, Route Planning, Scheduling

The Story So Far... Simplified CBR Single-Shot CBR Simple Retrieval & Adaptation Limitations Representing Complex Cases Sophisticated Models of Similarity Learning Cases & Adaptation Knowledge

Single-Shot CBR Limitations Complete problem descriptions are needed for retrieval. Complex problems may be more readily solve by reusing and combining (parts of) many cases. Solutions Incremental Case-Based Reasoning (ICBR) Hierarchical Case-Based Reasoning (HCBR)

Incremental CBR Motivations Incomplete Problem Descriptions (Eg, Help-Desks, Diagnosis) Feature Costs (Potentially many expensive tests or questions) Solution Skeletal cases used to initiate retrieval Early remindings guide the elicitation of extra information

Example: Help-Desk Support Problem: Paper Jam What sort of paper are you using? Problem: Paper Jam Paper : Envelopes : Solution:Glueless Envelopes Case 1 Paper: Slides Problem: Paper Jam Paper : Slides : Solution:Heat Res. Slides Right. If the slides aren’t heat resistant they will jam. Case 2

ICBR Advantages Diagnostic Features are Economically Selected Information theory ensures the selection of information-rich features in order to optimise diagnostic costs. Irrelevant features are ignored and expensive tests may be avoided. Assistant Technologies ICBR offers a ideal interactive framework for CBR assistants.

ICBR & Circuit Diagnosis Microprocessor Fault Diagnosis Large number of potential features. Varying costs due to the nature of features tests. A given diagnosis may depend on a relatively small number of features. Cases readily available. Results 30% - 90% reduction in feature tests.

Hierarchical CBR Motivations Complex problems require complex solutions. Retrieving and adapting a single case is unlikely to prove viable. Solution Decompose complex problems into simpler units. Retrieve, adapt, and combine cases.

Deja Vu: Software Design Plant-Control Software Steel Production Robots (Unloading/Loading Coils of Steel) Complex Control Programs Hierarchical Structure Programs can be decomposed into simpler units and recombined to produce complex solutions.

Case Hierarchies Problem A Problem B Abstract Case Concrete Case Individually reusable abstract & concrete cases Common sub-problems can be shared thereby improving the storage efficiency of the case-base.

Retrieval Issues Key Issue When is a case similar to the target problem? Problems Assessing relative feature importance. The relationship between similarity & adaptation.

The Weighting Game “Location, location, location…” Relative feature important can be critical in assessing case similarity. Eg, the location feature in property valuation. Importance encoded as feature weights. Similarity(T,C)=w 1.Sim(f t 1,f c 1 )+…+w n.Sim(f t n,f c n ) Feature Weights Case Similarity Feature Similarity

Assigning & Adjusting Weights Hand Coded Time Consuming - Another Knowledge Acquisition Bottleneck? Error Prone - Weights can be context sensitive. Automatic Learning Techniques Weights adjusted by analysing problem solving successes and/or failures. Success => Increase weights of matching features. Failure => Decrease weights of matching features.

Push & Pull Adjust feature weights to reduce similarity between target and incorrect case, thereby pushing the incorrect case away from the target. Case A (Incorrect) Target Case B (Correct) Adjust feature weights to increase similarity between target and correct case, thereby pulling the correct case towards the target

Example: Air Traffic Control Conflict Resolution Problem Select Aircraft Select Manoeuvre Crash Course!

Example: Air Traffic Control Conflict Resolution in ATC Case-Base of past conflicts plus resolutions. Complex Feature Weights Important features difficult to determine. Learning technique improved retrieval performance from 61% to 81%.

Similarity vs Adaptability The Similarity Assumption Cases, similar to the target, are easy to adapt. This assumption is often wrong! Solution Adaptability should be measured during retrieval. Retrieve adaptable cases. How?

Adaptation Guided Retrieval Adaptation Knowledge Guides Retrieval Knowledge about what can and cannot be adapted easily is used to validate matches and mismatches during retrieval. Retrieval SpaceAdaptation Space AdaptationRetrieval Adaptation Knowledge

Example: Deja Vu Plant-Control Software Design Surface similarities between features often disguise underlying adaptation problems. Results Improved retrieval accuracy. Improved system performance.

Adaptation Rule-Based Adaptation Adaptation expertise encoded as a set of rules. Knowledge acquisition problems. Solution Automatically learn adaptation rules. How?

Adaptation-Rule Induction Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: Price: Bungalow Co. Wicklow 3 2 1/3 Acre New Excellent £100,000 Type: Location: Bedrooms: Rcpt Rooms: Grounds: Age: Condition: Price: Bungalow Co. Wicklow 3 2 1/4 Acre New Excellent £85,000 IF Grounds: 1/4 Acre > 1/3 Acre THEN +£15,000 Adaptation Rule

Adaptation-Rule Induction Constrain Comparisons Limiting Case Comparisons Pruning Generated Rules Merging Rules Generalisation Results Viable Adaptation Knowledge

Learning in CBR Learning Feature Weights Learning Adaptation Knowledge Learning New Cases Newly solved problems = new cases! Expertise accumulates as more and more problems are solved.

Learning Issues Conventional Wisdom “More cases is a good thing” The Utility Problem Excess cases can cause performance problems as case retrieval eventually becomes prohibitively expensive. Saturation Point

Coping Strategies Case Forgetting Delete cases which do not contribute to system performance in a positive way. Implications Competence Problems Case-Base Size Efficiency Saturation Point Optimal system efficiency

Future Work Case-Base Maintenance Distributed CBR Future Applications

Case-Base Maintenance Need for Maintenance Large-scale, Dynamic Case-Bases Out-of-Date Cases Incorrect/Inconsistent Cases Performance Tuning Techniques Feature Weight & Adaptation Knowledge Learning Automatic Case Deletion

Distributed CBR CBR-Net Web-based CBR Systems (Help Systems, Online Shopping) Issues Distributed Client/Server Case-Bases Distributed Retrieval Adaptive Maintenance

Future Applications Personalised Content Delivery Product Selection Personalised Virtual Worlds

VRML on the Web 3D interactive worlds. Automatically construct worlds to suit the needs of individual users. Eg., Personalised shopping malls.

Conclusions Case-Based Reasoning “Reasoning as Remembering” Application Areas Prediction/Classification, Diagnosis, Planning, Design Future Work...