Case Maintenance的案例维护.pptVIP

Case Base Maintenance (CBM) Fabiana Prabhakar CSE 435 November 6, 2006 Introduction The growing use of CBR applications has brought with it increased awareness of the importance of case-base maintenance (CBM). Large scale CBR systems are becoming more prevalent, with case library sizes ranging from thousands to millions of cases. Large case-bases raises concern about the utility problem for case retrieval, underlining the potential need to control case-base growth through case deletion policies. Definition CBM is the process of refining a CBR system’s case base to improve the system’s performance. Standard CBR learning The system always add each new case to the case base. Domain expert adds a variable number of new cases. Indexing of the cases. Knowledge-based Systems Utility Problem The cost associated with searching for relevant knowledge outweighs the benefit of applying the knowledge. Traditional Deletion Policies A simple deletion policy is random deletion. According to this policy a random item is removed from the knowledgebase once the knowledge-base size exceeds some predefined limit. Minton’s utility metric [Minton, 1990]. Chooses a knowledge item for deletion based on an estimate of its performance benefits. Utility=(ApplicationFreq*AverageSavings)-MatchCost Remembering to Forget Competency Preserving Case Deletion Policy for CBR Systems (Smyth and Keane, 1995) Coverage and Reachability Coverage of a case is the set of target problems that can be solved by such case. Reachability of a target problem is the set of cases that can be used to provide a solution for the target problem. Case Competence Categories Pivotal Cases: its deletion directly reduces the competence of the system. A case is pivotal if it is reachable by no other case but itself. Auxiliary Cases: do not effect competence at all. A case is auxiliary case if the coverage it provides is subsumed by the coverage of one of its reachable cases. Case Competence Categories (Cont.) Spanni