Download as PPS, PDF, TXT or read online from Scribd
Download as pps, pdf, or txt
You are on page 1/ 12
Lecture 19
Recap • Human Expert vs. Expert System • Why Expert Systems? – Increase Availability – Reduce Cost – Permanence – Expertise drawn from multiple sources – Reliability – Fast Response – Steady and consistent – Explanation facility • How are expert systems used (replace, assist) • Examples of expert systems: SMARTPlan, R1/XCON, MYCIN Application Areas • Medicine (MYCIN) • Manufacturing • Business (SMARTPlan) • Engineering (R1/XCON) PEACE, CAD tool to assist in design of electronic structures. • Agriculture • Education (GUIDON) Expert System Structure • Lets look at how an expert (say a doctor) solves a problem: – Focused area of expertise – Specialized Knowledge (Long-term Memory, LTM) – Case facts (Short-term Memory, STM) – Reasons with these to form new knowledge – Solves the given problem • Lets define the corresponding concepts in an Expert System. Expert System Structure Human Expert Expert System Focused Area of Expertise Domain
Specialized Knowledge Domain Knowledge (stored
(stored in LTM) in Knowledge Base) Case Facts (stored in Case/Inferred Facts(stored STM) in Working Memory) Reasoning Inference Engine
Solution Conclusions Expert System Structure Expert System
Working Memory Analogy: STM -Initial Case facts -Inferred facts
Inference USER Engine
Knowledge Base Analogy: LTM - Domain Knowedge Knowledge Base • Part of the expert system that contains the domain knowledge – Problem facts, Rules – Concepts – Relationships • One of the roles of the expert system designer is to act as a knowledge engineer. • Knowledge acquisition bottleneck • You have to get information from the expert and encode it in the knowledge base, using one of the knowledge representation techniques we discussed in KRR. • As discussed, one way of encoding that knowledge is in the form of IF-THEN rules. We saw that such representation is especially conducive to reasoning. Working Memory • ‘Part of the expert system that contains the problem facts that are discovered during the session’ Durkin • A session is one consultation. • During a consultation: – User presents some facts about the situation. – These are stored in the working memory. – Using these and the knowledge in the knowledge base, new information is inferred and also added to the working memory. Inference Engine • Processor in an expert system that matches the facts contained in the working memory with the domain knowledge contained in the knowledge base, to draw conclusions about the problem • The inference engine works with the knowledge base and the working memory, and draws on both to add new facts to the working memory. • If our knowledge is represented in the form of IF-THEN rules, the Inference Engine has the following mechanism
– Match given facts in working memory to the premises
of the rules in the knowledge base, if match found, ‘fire’ the conclusion of the rule, i.e. add the conclusion to the working memory. Expert System Example: Family Knowledge Base Working Memory Rule 1: father (M.Tariq, Ali) IF father (X, Y) father (M.Tariq, Ahmed) AND father (X, Z) THEN brother (Y, Z) brother (Ali, Ahmed) Rule 2: payTuition (M.Tariq, Ali) IF father (X, Y) payTuition (M.Tariq,Ahmed) THEN payTuition (X, Y) like (Ali, Ahmed) Rule 3: IF brother (X, Y) THEN like (X, Y) Expert System Example: Raining Knowledge Base Working Memory Rule 1: person (Ali) IF person(X) person (Ahmed) AND person(Y) cloudy () AND likes (X, Y) AND sameSchool(X,Y) likes(Ali, Ahmed) THEN sameSchool(Ali, Ahmed) friends(X, Y) weekend() Rule 2: IF friends (X, Y) friends(Ali, Ahmed) AND weekend() goToMovies(Ali) THEN goToMovies(Ahmed) goToMovies(X) carryUmbrella(Ali) goToMovies(Y) carryUmbrella(Ahmed) Rule 3: IF goToMovies(X) AND cloudy() THEN carryUmbrella(X) Summary • The main components of an ES are – Knowledge Base – Working Memory – Inference Engine
