Académique Documents
Professionnel Documents
Culture Documents
Applications
Reservoir operations
High performance
Understandable
Reliable
Highly responsive
Advising
Demonstrating
Deriving a solution
Diagnosing
Explaining
Interpreting input
Predicting results
User
Working memory
User interface
Expert
User Interface :
It enables the users to enter instruction and information into the
expert system and to receive information from it. The information is in
the form of values assigned to certain variables. The user interface has
two parts –
1. Expert System Input: A user can use method for input command,
natural language and customize the interface.
2. Expert System Output: Expert systems are designed to provide
output or solution for a specific domain.
Knowledge Base:
It contains the fact that describes the problem area and knowledge
representation technique that describes manner. That means the knowledge
base contains a really high-quality and extraordinary knowledge in that
particular domain. The term problem domain is used to describe the problem.
Or basically, we can say that the knowledge base is the set of rules. The
rules in the knowledge base are usually coded in the form- if x, then y where
x is a condition, y is an action to be taken if the condition is true.
These kinds of rules are got from experience of human experts. The
knowledge of human experts is translated into the “if-then” statements. It is a
kind of job i.e. taking the knowledge from the experts and converting them
into such statements. A person who does this job is known as Knowledge
Engineer.
Inference Engine
Use of efficient procedures and rules by the Inference Engine is essential in deducting a
In case of knowledge-based ES, the Inference Engine acquires and manipulates the
knowledge from the knowledge base to arrive at a particular solution.
Applies rules repeatedly to the facts, which are obtained from earlier rule
application.
Resolves rules conflict when multiple rules are applicable to a particular case.
Backward Chaining
Forward Chaining
It is a strategy of an expert system to answer the question, “What can happen
next?”
Here, the Inference Engine follows the chain of conditions and derivations and finally
deduces the outcome. It considers all the facts and rules, and sorts them before
concluding to a solution.
This strategy is followed for working on conclusion, result, or effect. For example,
Backward Chaining
With this strategy, an expert system finds out the answer to the
question, “Why this happened?”
On the basis of what has already happened, the Inference Engine tries to
find out which conditions could have happened in the past for this result.
This strategy is followed for finding out cause or reason. For example,
diagnosis of blood cancer in humans.
Working memory
Working memory contains the data that is received from the user during the expert
system session. Values in working memory are used to evaluate antecedents in the
knowledge base. Consequences from rules in the knowledge base may create new
values in working memory, update old values, or remove existing values.
Knowledge Acquisition
Knowledge acquisition is the accumulation, transfer and transformation of problem-
solving expertise from experts and/or documented knowledge sources to a computer
program for constructing or expanding the knowledge base. It is a subsystem which
helps experts to build knowledge bases. For knowledge acquisition, techniques used
are protocol analysis, interviews, and observation.
Explanation Facility
It is a subsystem that explains the system's actions. The explanation can range from
how the final or intermediate solutions were arrived at to justifying the need for
additional data. Here user would like to ask the basic questions why and how and
serves as a tutor in sharing the system’s knowledge with the user.
Conceptualization
The second stage of ES development, conceptualization, involves designing the proposed
program to ensure that specific interactions and relationships in the problem domain are
understood and defined. The key concepts, relationships between objects and processes and
control mechanisms are determined. This is the initial stage of knowledge acquisition. It
involves the specific characterization of the situation and determines the expertise needed for
the solution of problem.
Formalization
Formalization involves organizing the key concepts, subproblems and information
flow into formal representations. In effect, the program logic is designed at this
stage. It is often useful to group or modularize the knowledge collected, perhaps
even attempting to display the problem solving steps graphically.
In effect, it is the job of the knowledge engineers to build a set of interrelated tree
structures for representing the knowledge base. They must decide the attributes to
be determined to solve the problem and then which of these attributes should be
asked of the user or represented by an internal set of decision trees.
Implementation
During the next stage, implementation, the formalized knowledge is mapped or
coded into the framework of the development tool to build a working prototype.
The contents of knowledge structures, inference rules and control strategies
established in the previous stages are organized into suitable format. Often,
knowledge engineers will have been using the program development tool to build a
working prototype to document and organize information collected during the
formalization stage, so that implementation is completed at this point. If not, the
notes from the earlier phases are coded at this time.