Lecture 12 - Expert Systems
Lecture 12 - Expert Systems
What is an Expert ?
• What characterizes an ‘Expert’
• Specialized knowledge in a certain area
• Experience in the given area
• Explanation of decisions
• A skill set that enables the expert to translate the specilized knowledge
gained through experience into solutions.
• e.g. Skin specialist, heart specialist, car mechanic, architect, software
designer.
What is an expert system?
• “A computer program designed to model the problem solving ability
of a human expert” Durkin
• Aspects of the human expert that we wish to model
• Knowledge
• Reasoning
Comparison of a Human
Expert and an Expert
System
• Example: medical ES modelling a doctor, discuss each
of the following issues in that context.
• The ES outperforms the ‘average’ doctor and is
available in regions where people may not have
access to any medical care at all otherwise.
Comparison
Issues Human Expert Expert System
Availability Limited Always
Geographic location Locally available Anywhere
• Diagnosis
• Interpretation
• Prescription
• Design
• Planning
• Control
• Instruction
• Prediction
• Simulation
Control Applications
• Adaptively govern/regulate the behavior of a system
• E.g. controlling a manufacturing process, or medical treatment
• Obtain data about current system state, reason and predict future
state, recommend/execute adjustments
• Example: VM (device to monitor patient)
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
Solution Conclusions
Expert System Structure
Expert System
Working Memory
Analogy: STM
-Initial Case facts
-Inferred facts
Knowledge Base
Analogy: LTM
- Domain Knowedge
User Interface
• The user interface is the screen in to which the user types in
the query and it has 2 functions:
• Accept input in from the user,
• Output advice to the user.
• Depending on the system the user interface might involve a
touch screen, keyboard or even just a simple keypad ( for
example car diagnostic systems)
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