Browse Prior Art Database

Synchronization Between IVGEN And the Rule System

IP.com Disclosure Number: IPCOM000102594D
Original Publication Date: 1990-Dec-01
Included in the Prior Art Database: 2005-Mar-17
Document File: 1 page(s) / 49K

Publishing Venue

IBM

Related People

Dingankar, AT: AUTHOR [+2]

Abstract

Disclosed is a method for IVGEN to communicate with the rule system.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 63% of the total text.

Synchronization Between IVGEN And the Rule System

       Disclosed is a method for IVGEN to communicate with the
rule system.

      The rule system contains rules of the form:
           IF   <premises>
           THEN <conclusions>
The rules are "tickled" when one of its premises becomes true.  The
tickled rule "matches" if ALL the premises are true.  The conclusions
are then evaluated, which are usually in the form of assertions of
facts or LISP function evaluations.  Thus, procedural knowledge can
be incorporated into the rules by including function calls in the
conclusions.

      As IVGEN (Implementation Verification GENerator) generates test
cases, it needs to tell the rule system somehow what it is currently
generating, in particular if it is a function or a fault.  This
information is needed since the rules will not be tickled (or
subsequently fired) until at least one of its premises is evaluated
to true.

      Create a CURFUN_TC and CURFAULT_TC slots in the MACHINE_INFO
unit in the GENERAL_KNOWLEDGE knowledge base. The current function
name is asserted as the value of the CURFUN_TC slot and the current
fault name is asserted as the value of the CURFAULT_TC slot.  As soon
as IVGEN reaches the stage of triggering a function X, it assigns the
name X to CURFUN_TC and uses the ASSERT command to kick off the
forward chaining process throughout the entire rule system. Any rule
that has a premise that matches the fact of X bei...