Chapter 1 Introduction To KBS
Chapter 1 Introduction To KBS
Introduction to knowledge-based
systems
Motivation
• Domain
– some area of interest
banking, food industry, photocopiers, car manufacturing
• Task
– something that needs to be done by an agent
monitor a process; create a plan; analyze deviant behavior
• Agent
– the executor of a task in a domain
typically either a human or some software system
Terminology
• Application
– The context provided by the combination of a task
and a domain in which this task is carried out by
agents
Parts of a Knowledge Base System
Knowledge Base systems consist of a varied number of
components;
•The Knowledge Base,
•The User =>Knowledge Engineer, Knowledge Expert,
Application User
•The Inference Engine
•The I/O User Interfaces
•Working Memory
•Learner
•The Explainer (Explanation Facility)
•Knowledge Acquisition Module
KBS architecture (2)
Applications of Knowledge Base
systems
• Knowledge Base systems have been applied to many diverse
problem domains, such as the following.
• Diagnostic Aids such as MYCIN, [Shortliffe '76, Davis '76],
which diagnoses bacterial blood infections and PUFF, [Kunz
et al '78], which diagnose pulmonary disorders.
• MYCIN was a joint venture between Dept. of Computer
Science and the Medical School of Stanford University.
• Much of the work took place in the 1970's.
• Mycin was designed to solve the problem of diagnosing and
recommending treatments for meningitis and bacteremia,
(blood infections).
• Aids to Design and Manufacture such as R1,
[McDermott '82], which configures
computers.
• Teaching Aids such as SCHOLAR [Carbonell
'70] which gives Geography Tutorials and
SOPHIE, [Brown et al '82], which teaches how
to detect breakdown in electrical circuits.
• Problem Solving
• Recognition of forms, e.g. DENDRAL, [Buchanan and
Feigenbaum '78, Lindsay et al '80], which recognizes
the structures of chemical compounds.
• Robotics e.g. SHDRLU, [Winograd '73], which
manipulates polygons in a restricted environment.
• Game playing systems such as Waterman's Poker
Player, [Waterman '70], and
• Automatic theorem Provers such as AM, [Lenat '82].
• [Hayes-Roth et al '83, Handbook A.I. '82, Waterman
'86], describe some more categories than those
mentioned above. These include Planning systems
such as NOAH, [Sacerdoti '75] and MOLGEN,
[Friedland '75] and
• Prediction systems such as Political Forecasting
Systems, [Schrodt '86] based on the Holland
Classifier, [Holland '86].
Choosing a KBS project
• Because of cost, and the danger of failure, it
is important that KBS projects are carefully
chosen.
Choosing aKBS project
– The expense must be justified, in the light of
the possible benefits.
– KBS technology must be appropriate
• the right kind of knowledge is available
• it isn’t a problem which conventional
programming could do better.
– Management, and the participants, must
support the project fully.
The phone call test
• A rather simpler approach to answering the
question which domains are worth building
into a KBS?
• “Any problem that can be and frequently is
solved by your in-house expert in a 10-30
minute phone call can be automated as an
expert system.” Prof.Morris Firebaugh
ES Tools
• ES languages
– higher-level languages specifically designed for
knowledge representation and reasoning
– SAIL, KRL, KQML, DAML, OWL (Web Ontology
Language)
• ES shells
– an ES development tool/environment where the user
provides the knowledge base
– CLIPS, JESS, Mycin, Babylon, G2, ...
Possible expert systems - case histories
• For discussion.
• The following seven problem areas may, or
may not, be suitable for computerisation as
KBS.
Possible KBSs - case histories