CS6659

ARTIFICIAL INTELLIGENCE

-
 SYLLABUS

• UNIT I INTRODUCTION TO Al AND PRODUCTION SYSTEMS 9

• UNIT II REPRESENTATION OF KNOWLEDGE 9

• UNIT III KNOWLEDGE INFERENCE
9
• UNIT IV PLANNING AND MACHINE LEARNING
9
• UNIT V EXPERT SYSTEMS 9
 UNIT V EXPERT SYSTEMS

Expert systems - Architecture of expert systems, Roles of

expert systems –

Knowledge Acquisition – Meta knowledge, Heuristics.

Typical expert systems - MYCIN, DART, XOON, Expert

systems shells.
Expert Systems
Introduction
 Reasoning by If-Then Rules

• Expert systems are designed to solve complex problems in a particular domain

– By reasoning about knowledge,

represented mainly as if–then rules

rather than through conventional procedural

code.
Characteristic Features of Expert System
Characteristic Features of Expert System
Architecture of Expert Systems

-
Rule-Based System Architecture
 Architecture of Expert Systems
USER EXPERT SYSTEM

Explanation
Module
Inference Case
Engine History File
Input
I/O
Interface
Output
Knowledge Working
Base Memory

KB Editor

Learning
Module
Major Components of Expert System
Defining Rules
 Defining Rules

• Action part can be

– An action (executed by interpreter) or

– An inference of new fact or assertion (added to the KB)

Inference Engine Knowledge
Base
Working
Memory

1 Match

Conflict Set

2 Select

3 Execute

Production System
Inference Cycle
Inference Engine Knowledge
Base
Working
Memory

1 Match

Conflict Set

2 Select

3 Execute

Production System
Inference Cycle
Inference Engine
Explanation Module (EM)
 Other Components

• Editor – Used by developers

– To create new rules for addition to the KB,

– To delete outdated rules, or

– To modify existing rules in some way.

• Case History File and Learning Module

– They are not common components of expert systems

– When they are provided, they are used to assist in building and refining the KB.
 Knowledge Base (KB)
• Knowledge Base (KB) contains the facts & rules of current domain-specific knowledge
– Necessary for understanding, formulating, and solving problems.

• Knowledge base of expert systems contains both factual and heuristic knowledge.
– Factual knowledge is the general knowledge from textbook of domain that everyone agrees on

– Heuristic knowledge is not from textbooks of domain; it is come from one's experience.

• It can be seen as
knowledge of judgment & logical reasoning based on factual knowledge.

• Knowledge representation
– It is the method used to organize and formalize the knowledge in the KB.

• Each fact and rule is identified with a name

– Ex: a1 : Bob is a male

r1 : IF Bob is more than 18 THEN Bob is adult

 Defining Rules
• Rules in Rule-based systems consist of condition-action pairs

IF <condition> THEN <action> or

C  A or

IF <antecedent> THEN <consequent>

– Condition part (C) determines when a given rule is applied, and
– Action part (A) determines what happens when it is applied.

• This pair define a condition which, if satisfied in a certain situation,

– Causes the production rule to "fire", i.e., the action to be carried out.

• Action part can be

– An action (executed by interpreter) or
– An inference of new fact or assertion (added to the KB)
 Knowledge Engineer
• Knowledge Acquisition

– KB is formed by readings from various experts, and Knowledge Engineers.

• Knowledge engineer have the qualities of empathy(understanding), quick

learning, & case analyzing skills.

• He acquires information from domain expert (human expert)

by recording, interviewing, and observing him at work, etc.

• He then categorizes and organizes the information in a meaningful way,

in the form of IF-THEN-ELSE rules, to be used by interference

machine.

• Knowledge engineer also monitors the development of the ES.

 Inference Engine Knowledge
Base
Working
Memory

• Inference process is carried out recursively in 3 stages

1 Match
1. Match, 2. Select, and 3. Execute
• During match stage,
Conflict Set
– Content of working memory are compared to facts and rules

contained in KB 2 Select
– When matches are found, the corresponding rules are
3 Execute
added to the conflict set
• In select stage,
– One of the rules in the conflict set is selected for execution Production System
– Criteria for selection may be Inference Cycle
• Most recent use, rule condition specificity, or the smallest rule number

• During execute stage,

– Selected rule is then executed and RHS or action part of the rule is carried out.
 Inference Engine
• Inference Engine can work in two modes

1. Forward chaining (Data-Driven Inference)

2. Backward chaining (Goal-Driven Inference)

• Forward Chaining starts with the initial or current state (with available facts)
– Apply rules one by one.
• Matching the premises of the rules (the IF parts), and

• Performing the corresponding actions (the THEN parts)

that usually update the knowledge base or working memory.

• Backward Chaining starts with the goal state (to be proved)

– And try to prove the goal using the given facts (works backward)
• Look at the WM to see if the sub-goal states already exist there.

• If not, identify the actions (THEN parts) of the rules that will establish the sub-goals.

• And new sub-goals are set up for achieving the premises of those rules (the IF parts).
 Explanation Module (EM)

• EM provides the user with an explanation of reasoning process when requested

– This is done in response to

• A how query or

• A why query

• To respond to a how query,

1. EM traces the chain of rules fired during a consultation with the user.

2. The sequence of rules that led to conclusion is then printed for the user.

– If user not agree with the reasoning steps presented

• They may changed using the editor.

 Explanation Module (EM)

• To respond to a why query,

– EM explain why certain information is needed by inference engine

to complete a step in reasoning process before it can be proceed.

– Example :

• In diagnosing a car that will not start,

a system might be asked why it needs to know the status of the distributor spark.

• In response, the system would reply that it needs this information

to determine if the problem can be isolated to the ignition system

 User Interface
• User interface provides interaction between user of the ES and the ES itself.

• It is generally Natural Language Processing

– So as to be used by the user who is well-versed in the task domain.

• User of the ES need not be necessarily an expert in Artificial Intelligence.

• It explains how the ES has arrived at a particular recommendation.

• Explanation may appear in the following forms

– Natural language displayed on screen.

– Verbal narrations in natural language.

– Listing of rule numbers displayed on the screen.

• The user interface makes it easy to trace the credibility of the deductions.
 Other Components

• Editor – Used by developers

– To create new rules for addition to the KB,

– To delete outmoded rules, or

– To modify existing rules in some way.

• Case History File and Learning Module

– They are not common components of expert systems

– When they are provided, they are used to assist in building and refining the KB.