Browse Prior Art Database

Method for Transferring Collected Data Between Rulebases of Expert Systems

IP.com Disclosure Number: IPCOM000059790D
Original Publication Date: 1986-Jan-01
Included in the Prior Art Database: 2005-Mar-08
Document File: 2 page(s) / 15K

Publishing Venue

IBM

Related People

Benignus, DM: AUTHOR [+4]

Abstract

An arrangement is described which permits the transfer of data in an Expert System (ES) between two separate rulebases during a continuous session and/or which allows information to be passed into the expert system when it is called. The knowledge base of ES may be segmented into multiple rulebases, each designed to diagnose, for example, a single component of a data processing system. Each rulebase could at any point in the consultation call another rulebase. Therefore, it is necessary to pass information between rulebases. The rulebase consists of a forest of n-ary trees with goals at the root of the tree and evidences and external nodes at the leaves of the tree. The evidence nodes refer to questions asked to the user. These questions are sometimes called classes.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 47% of the total text.

Page 1 of 2

Method for Transferring Collected Data Between Rulebases of Expert Systems

An arrangement is described which permits the transfer of data in an Expert System (ES) between two separate rulebases during a continuous session and/or which allows information to be passed into the expert system when it is called. The knowledge base of ES may be segmented into multiple rulebases, each designed to diagnose, for example, a single component of a data processing system. Each rulebase could at any point in the consultation call another rulebase. Therefore, it is necessary to pass information between rulebases. The rulebase consists of a forest of n-ary trees with goals at the root of the tree and evidences and external nodes at the leaves of the tree. The evidence nodes refer to questions asked to the user. These questions are sometimes called classes. The external nodes contain references to results obtained from running a test unit. The goal node contains a conclusion, such as "Install new printer element." ES selects a goal to pursue, and then the underlying tree is traced postorder until, for example, an evidence node that has not been asked is encountered. It is asked then to the user. When the user has responded, the node is updated true or false according to the answer it was expecting. All other evidence nodes in the rulebase containing a reference to this class are also updated true or false depending on the answer given. Similarly, if the node found is an external node, and the test unit it references has not been executed, the test unit is executed on the hardware. When the test unit has completed execution, the node is updated true or false according to the results it was expecting. All other external nodes in the rulebase containing a reference to the test unit are updated true or false depending on the results from the test. The node values are passed up the tree until a goal is either concluded or rejected. Because of multiple rulebases, it is sometimes necessary to retain values given to classes, procedures, and rule nodes. The present arrangement employs an attribute "GLOBAL" designed to allow passing of data between rulebases. A node in a rule tree, a procedure, a class, or a parameter may be assigned the GLOBAL attribute. As an example, suppose the first rulebase executed determines the hardware configuration of a data processing system by running some test units. If the user wanted to diagnose several components (printer, disk drive, keyboard, etc.), it is desirable to run the configuration test units only once for all components. If each component to be tested required a separate rulebase, the configuration information could be passed to all the rulebases using the GLOBAL attribute. The GLOBAL attribute is used to pass values between rulebases when multiple rulebases are executed. If a value, either for a class, parameter, or test unit result is needed between rulebases, then that class, test unit (procedure), or paramete...