 |
Step 1 (continued):
The exact format should be influenced by the way the expert system shell
you are using requires you to
define attributes. This documentation will be helpful when you are
implementing the knowledge base and must
declare the attributes and define the user interface.
| Name: | the result of trying the starter |
| Goal attribute?__ Max values 1 CF input? X |
| Type: | Text X Logical__ Numeric__ |
| Input prompt: | What happens when you try the starter? |
| Value range: | _______________ to _______________ |
(or)
Legal values: | nothing happens |
| cranks normally |
| cranks slowly |
| Default value: | |
|
|
In this example format, you would check the Goal attribute block if the
attribute represents a goal for the consultation. Max values defines
the maximum number of values the expert system is allowed to store for this
attribute (usually one).
Attributes that are not goals and whose values will be elicited from the
expert system's user will require user interface definition in the shell.
Typically, this involves specifying the Type of data stored in the
attribute and the question the user will be
asked (the Input prompt). A
Value range or list of Legal values allows the shell to display
data input boxes or a menu of responses and to validate input data.
Check CF input if you will allow the user to specify a confidence
factor for the attribute. Some shells allow specification of a Default value
that will be assigned to the attribute if it is not input or determined by the rules.
|