Declarative Product Data Base for a Design Verification Test Generation Expert System
Original Publication Date: 1991-Nov-01
Included in the Prior Art Database: 2005-Apr-04
One of the problems in developing an automated Design Verification Test Generation System for all computer-related products is the diversity of the representation of the product information.
Declarative Product Data Base for a Design Verification
One of the
problems in developing an automated Design
Verification Test Generation System for all computer-related products
is the diversity of the representation of the product information.
associated with every product there is certain
declarative or static knowledge that forms the basis for common
evaluation. A product's declarative knowledge consists of two parts:
(1) the product information data base, and (2) the product knowledge
information data base consists of the product's
instruction-set or command-set, and the associated instruction rule
names. Associated with each instruction are the rule name fields -
the relationship of the rule fields are: (1) Data Rule Name, (2)
Register Rule Name, (3) Load Rule Name, and (4) Check Rule Name.
instructions and the instruction rule name files are
free formatted and may be placed in any column. Furthermore, there
are no restrictions on the length of the instruction rule name, nor
are there any restrictions on the type of characters to be coded into
the name (e.g., Load Rule "RX" could be rewritten as "@$=S.5,A" if it
aided in the programmer's understanding).
Aside from an
instruction-set, all computer products have
certain rules which describe their behavior. There are two
classifications of rules which all product applications have: (1)
test rules, and (2) instruction rules.
pertain to the pre- and post-composition of the
application program or test. All programs have a "BEGINNING" and an
"END". "DEFINE CONSTANT or VARIABLE AREA", "SUBROUTINES", and
"CONTINUATION" rules are added options, which may or may not exist.
four classifications of instruction rules: (1) date
rules describe the formal representation of the instruction's data.
(2) register rules describe the number of registers that may be
associated with a given instruction. (3) load rules describe the
initialization requirements for a given instruction and (4) check
rules describe the checking procedure for evaluating the
instruction's result or answer.
(1) PRODUCT INFORMATION DATA BASE
- Instruction Set
- Instruction Rule Names
(2) PRODUCT KNOWLEDGE DATA BASE
- Preamble (Begin) Rules
List of instructions to set up the
base-register, PSW, MASK(s), SAVE Registers,
- Postamble (End) Rules
List of instructions to return SAVED
Registers, and return control.
- Continuation Rules
List of instructions to link two or more
tests or application program...