 |
Books by Holsapple and Whinston, 1986,
Mockler, 1989
and others introduce the knowledge
engineering applications of
dependency diagrams. These represent the alternative
sequences of facts that could be
combined to lead to a conclusion. They help the knowledge engineer structure
additional layers of rules for all or part of a knowledge base. Here's an
example from the automobile diagnosis expert system:
The process for developing dependency diagrams is similar to the process
we've recommended for defining goals, attributes and rules. Begin with a goal
attribute, then define attributes that are relevant to determining the
value of the goal. Continue the process treating each of these attributes
as subgoals. After the diagrams are constructed, rules are suggested by examining
the diagram from right to left looking for combinations of attributes to
combine into logical expressions that
determine the value of a subgoal or goal attribute. Slides 11
and 13
show some rules that are suggested by the example diagram.
|