Method and apparatus for rule-based operations

• US 7,222,114 B1
• Filed: 08/20/2003
• Issued: 05/22/2007
• Est. Priority Date: 08/20/2003
• Status: Expired due to Fees

• Current Assignee: Xilinx, Inc. (Advanced Micro Devices, Inc.)
• Original Assignee: Xilinx, Inc. (Advanced Micro Devices, Inc.)
• Inventors: Chan, Vi Chi
• Primary Examiner(s): Hirl; Joseph P
• Application Number:
  US10/644,161
• Time in Patent Office: 1,371 Days
• Field of Search: 706/47, 706/46, 706/14, 716/5
• US Class Current: 706/47
• CPC Class Codes: G06N 5/025 Extracting rules from data

Abstract

A method of a rule-based operation can include the steps of dividing a design rule into at least one of three components including an application criteria, a rule condition, and an action. The method can further include the steps of expressing the design rule as a datafile or source code and binding the three components together to form a rule object at runtime.

Claims

1. A processor-implemented method of generating design rules for use in validating an electronic design, comprising the steps of:

establishing for each of a plurality of design rules for the electronic circuit design, a respective set of first, second, and third components;

wherein application of a design rule determines whether the electronic circuit design satisfies a requirement specified by the design rule;

wherein the first component of a design rule specifies triggering criteria that specify whether the design rule is applicable to the electronic design, the second component of the design rule specifies a condition, and the third component of the design rule specifies an action performed in response to the design rule being applicable based on the triggering criteria of the first component and the condition of the second component being satisfied;

wherein for each first, second, and third components of the plurality of design rules, the component is one of a datafile and source code, and the first, second, and third components are separate files;

for each first, second, and third component specified as a datafile, storing the datafile in a database;

for each first, second, and third component specified as source code, compiling the source code into object code;

and

binding each set of first, second, and third components together to form a rule object at runtime.

2. The method of claim 1, further comprising, entering at least one among a new design rule and a change to an existing design rule at runtime using a runtime plug-in, wherein the step of entering is done without compiling.

3. The method of claim 2, wherein the step of entering at least one among the new design rule and the change to the existing design rule comprises the step of changing at least a portion of one component.

4. The method of claim 1, wherein the method further comprises forming a common object interface to a rule checker program to form an interface between the three components.

5. The method of claim 1, wherein the datafile includes an XML statement and the source code includes a C or C++ instruction.

6. A machine readable storage, having stored thereon a computer program having a plurality of code sections executable by a machine for causing the machine to perform the steps of:

establishing for each of a plurality of design rules for the electronic circuit design, a respective set of first, second, and third components;

wherein application of a design rule determines whether the electronic circuit design satisfies a requirement specified by the design rule;

wherein the first component of a design rule specifies triggering criteria that specify whether the design rule is applicable to the electronic design, the second component of the design rule specifies a condition, and the third component of the design rule specifies an action performed in response to the design rule being applicable based on the triggering criteria of the first component and the condition of the second component being satisfied;

wherein for each first, second, and third components of the plurality of design rules, the component is one of a datafile and source code, and the first, second, and third components are separate files;

for each first, second, and third component specified as a datafile, storing the datafile in a database;

for each first, second, and third component specified as source code, compiling the source code into object code; and

binding each set of first, second, and third components together to form a rule object at runtime.

7. The machine readable storage of claim 6, wherein said step of binding is done without compiling.

8. The machine readable storage of claim 6, wherein the plurality of code sections further cause a machine to form a common object interface to a rule checker program to form an interface between the three components.

9. A apparatus for generating design rules for use in validating an electronic design, comprising:

means for establishing for each of a plurality of design rules for the electronic circuit design, a respective set of first, second, and third components;

wherein application of a design rule determines whether the electronic circuit design satisfies a requirement specified by the design rule;

wherein the first component of a design rule specifies triggering criteria that specify whether the design rule is applicable to the electronic design, the second component of the design rule specifies a condition, and the third component of the design rule specifies an action performed in response to the design rule being applicable based on the triggering criteria of the first component and the condition of the second component being satisfied;

wherein for each first, second, and third components of the plurality of design rules, the component is one of a datafile and source code, and the first, second, and third components are separate files;

means, responsive to each first, second, and third component specified as a datafile, for storing the datafile in a database;

means, responsive to each first, second, and third component specified as source code, for compiling the source code into object code;

and

means for binding each set of first, second, and third components together to form a rule object at runtime.

10. The apparatus of claim 9, further comprising means for entering at least one among a new design rule and a change to an existing design rule at runtime using a runtime plug-in.

11. The apparatus of claim 9, further comprising means for interfacing with a rule object formed from the first component, the second component, and the third component at runtime.

12. The apparatus of claim 9, further comprising means for building a rule repository from at least one among a datafile and program objects.

13. The apparatus of claim 12, further comprising means for searching for specified directories for user specified rule additions.