150 likes | 252 Views
This paper, authored by Agnar Aamodt and Enric Plaza, presents a comprehensive overview of Case-Based Reasoning (CBR) within the context of artificial intelligence. Published in AI Communications, it highlights foundational issues, methodologies, and results from European research. Core elements of CBR such as retrieval, reuse, revision, and retention processes are discussed, along with their implications for knowledge management. The paper serves as a review of CBR's state-of-the-art in 1994 and addresses crucial design trade-offs that remain relevant today.
E N D
ResearchAamodt & Plaza, 1994 Robin Burke CSC 594 4/7/2004
Outline • Context • Authors • Venue • Purpose • Content • foundational issues
Authors • Agnar Aamodt • Norway • Enric Plaza • Spain
Venue • AI Communications • Main European Journal for Artificial Intelligence
Purpose • Overview of CBR • Methodology • European results • Three goals • foundational issues • methodological variations • system approaches
Foundational Issues • Characterizing CBR • Case representation • Issues related to each step of CBR cycle • knowledge-weak • knowledge-intensive
Characterizing CBR • 4 Rs • Retrieve • Reuse • Revise • Retain
Decomposition • Retrieve • identify features • search • match • select • Reuse • copy • adapt • Revise • evaluate solution • repair • Retain • integrate • index • extract
Memory organization • Dynamic memory model • cognitively-based • generalized episodes • cases discriminated by feature values • Category / exemplar model • also cognitively-based • categories defined by exemplars • prototypical examples
Retrieval • feature extraction • simple – use features present • complex – infer (deep) features • matching • simple – find nearby cases • complex – reason about similarity
Reuse • Transformational reuse • adapt the case • emphasis on experience with rules as a guide • Derivational reuse • adapt the problem-solving process • emphasis on rule-based problem-solving with experience as a guide
Revise • Evaluation • was the proposed solution successful? • simple – user critiques • complex – system generates and processes feedback • Repair • another adaptation step guided by evaluation • simple – discard failures • complex – explain failure and adjust accordingly
Retain • Extract • package problem-solving episode as a case • simple – save features of problem situation and solution • complex – save explanation of why/how the solution solved the problem • Index • decide how to label the case • simple – all input features • complex – use diagnostic / predictive features • Integrate • put the case in memory • simple – just store it • complex – adjust indexing mechanism and/or background knowledge
Bottom Line • Review of the state-of-the-art in 1994 • Indicates some of the design tradeoffs still important in case-based systems • Knowledge management field did not exist • discussion couched in AI terms (planning, problem-solving) • both fielded examples we would now consider as KM
KM Implications • Should an organizations just store stuff? • value of identifying and organizing cases • How should retrieval work? • syntactic: keywords • semantic: reasoning about the domain • What else is needed besides cases?