# US 2001/0025369 A1 · Block based design methodology

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2001/0025369 A1
- Document ID: US20010025369A1
- Status: Published application
- Kind: A1
- Application number: 09/754,725
- Filed: 2001-01-04
- Published: 2001-09-27
- Earliest claimed: 1999-09-30
- Assignees: Cadence Design Systems, Inc.
- Inventors: Henry Chang; Larry Cooke; Merrill Hunt; Wuudiann Ke; Christopher K. Lennard; Grant Martin; Peter Paterson; Khoan Truong; Kumar Venkatramani
- Web page: https://patentgrep.com/patent/US20010025369A1

## CPC

- G06F 30/3308: using simulation
- G06F 30/30: Circuit design
- G06F 30/33: Design verification, e.g. functional simulation or model checking
- G06F 2115/08: Intellectual property [IP] blocks or IP cores
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A method and apparatus for designing a circuit system, including selecting a plurality of pre-designed circuit blocks to be used to design the circuit system, collecting data reflecting the experience of the designer regarding the pre-designed circuit blocks, the designer's experience being adaptable to a processing method, accepting or rejecting a design of the circuit system in a manner based on the designer's experience data and acceptable degree of risk, upon acceptance, forming block specifications containing criteria and modified constraints for each of the circuit blocks, upon acceptance, forming block specifications for deploying the circuit blocks on a floor plan of a chip, as a system on a chip, in compliance with the criteria and modified constraints, and substantially without changing the selected circuit block and the processing method.

## Claims

### Claim 1

A method for designing a circuit system, the method being executed by a designer, the method comprising the steps of:
(a) selecting a plurality of pre-designed circuit blocks to be used to design the circuit system;
(b) collecting designer's data (including experience data, estimation data, and/or implementation data) regarding the pre-designed circuit blocks, the designer's data being adaptable to a processing method;
(c) accepting or rejecting a design of the circuit system in a manner based on the designer's data and acceptable degree of risk;
(d) upon acceptance, forming block specifications containing criteria and modified constraints for each of the circuit blocks (FEA);
(e) upon acceptance, forming block specifications for deploying the circuit blocks on a floor plan of a chip, in compliance with the criteria and modified constraints without changing the selected circuit block and the processing method.

### Claim 2 (depends on 1)

The method of claim 1, wherein the specification includes bus identification information.

### Claim 3 (depends on 1)

The method of claim 1, wherein the specification includes test strategies.

### Claim 4 (depends on 1)

The method of claim 1, further comprising the step of:
(f) upon acceptance, deploying the circuit blocks on the floor plan of the chip by adding standard and system specific interface for the circuit blocks.

### Claim 5 (depends on 4)

The method of claim 4, further comprising the step of:
(g) forming glue circuits for interconnecting the circuit blocks.

### Claim 6 (depends on 1)

The method of claim 1, further comprising the step of:
(f) forming a top-level plan for fabricating the selected circuit blocks into the chip based on the circuit specifications.

### Claim 7 (depends on 5)

The method of claim 5, further comprising the step of:
(h) verifying the proper execution of each of steps (c), (d), (e), (f), and (g), before completing the process.

### Claim 8

A method for designing a circuit system, the method being executed by a one or more designer, the method comprising the steps of:
(a) selecting a plurality of pre-designed circuit blocks to be used to design the circuit system;
(b) collecting data reflecting the experience of the designer regarding the pre-designed and yet to be designed circuit blocks, the designer's experience being adaptable to a processing method;
(c) accepting or rejecting a design of the circuit system in a manner based on the designer's experience data and acceptable degree of risk;
(d) upon acceptance, forming block specifications containing criteria and modified constraints for each of the circuit blocks; and
(e) upon acceptance, creating forming block specifications and glue logic for clocks, power, and bus communication to for deploying the circuit blocks on a floor plan of a chip, in compliance with the criteria and modified constraints meet the design objectives without changing the selected circuit block and the processing method.

### Claim 9 (depends on 8)

The method of claim 8, further comprising the step of:
(f) upon acceptance, forming block specifications for deploying the circuit blocks on a floor plan of a chip, in compliance with the criteria and modified constraints without changing the selected circuit block and the processing method.

### Claim 10 (depends on 9)

The method of claim 9, the step (f) further comprising forming virtual circuit specifications for each of the circuit blocks, to deploy the circuit blocks on the floor plan of the chip.

### Claim 11 (depends on 8)

The method of claim 8, the designer's data experience including at least one member of the group consisting of: field of use, simulation, and partial or full implementation of at least one of the pre-designed blocks.

### Claim 12 (depends on 9)

The method of claim 9, further comprising the step of
(g) forming glue logic for interconnecting the circuit blocks.

### Claim 13 (depends on 9)

The method of claim 9, further comprising the step of
(g) forming collar interfaces for interconnecting the circuit blocks.

### Claim 14 (depends on 9)

The method of claim 9, the step (f) further comprising:
upon acceptance, forming a top-level plan for fabricating the selected circuit blocks into the chip based on the virtual circuit specifications.

### Claim 15 (depends on 9)

The method of claim 9, further comprising the step of: verifying the proper execution of each of steps (c), (d), (e), and (f) before completing the process.

### Claim 16 (depends on 14)

The method of claim 14, further comprising the step of: generating and verifying the resulting physical layout, mask and test data necessary to fabricate said chip.

### Claim 17

A method for expanding an existing methodology for assessing feasibility of a circuit design based on a predetermined type of parameter, the method comprising the steps of:
(a) selecting a plurality of circuit blocks to be used in the circuit design;
(b) receiving the predetermined type of parameter for the circuit blocks;
(c) assessing a first feasibility using the existing methodology based on the predetermined type of parameter, the first feasibility including a first risk indicator and first time/cost indicator;
(d) receiving at least a second type of parameter that has not been used in the existing methodology;
(e) processing the second type of parameter to accommodate the existing methodology; and
(f) assessing a second feasibility using the existing methodology based on the predetermined type of parameter and the second type of parameter, the second feasibility including a second risk indicator, and a second time/cost indicator, wherein the second risk indicator has not been substantially increased compared with the first risk factor due to the use of the existing methodology, and the second time/cost factor has been increased compared with the first time/cost factor due to the impact of the second type of parameter.

### Claim 18 (depends on 17)

The method of claim 17, wherein the predetermined type of parameter is field of use data, and the second type of parameter is either estimation data or implementation data.

### Claim 19

A method for expanding an existing methodology for assessing feasibility of a circuit design based on a predetermined type of parameter, the method comprising the steps of:
(a) selecting a plurality of circuit blocks to be used in the circuit design;
(b) receiving the predetermined type of parameter for the circuit blocks;
(c) assessing a first feasibility using the existing methodology based on the predetermined type of parameter, the first feasibility including a first risk indicator and first time/cost indicator;
(d) receiving at least a second type of parameter that has not been used in the existing methodology;
(e) changing the existing methodology to accommodate the second type of parameter; and
(f) assessing a second feasibility using the changed methodology based on the predetermined type of parameter and the second type of parameter, the second feasibility including a second risk indicator, and a second time/cost indicator, wherein the second risk indicator has been increased compared with the first risk factor due to the change of the existing methodology, and the second time/cost factor has not been substantially increased compared with the first time/cost factor due to the change of the existing methodology.

### Claim 20 (depends on 19)

The method of claim 19, wherein the predetermined type of parameter is field of use data, and the second type of parameter is either estimation data or implementation data.

### Claim 21

A method for expanding an existing methodology for assessing feasibility of a circuit design based upon a predetermined set of design characteristics, the method comprising the steps of:
(a) determining to be the field of use a set of design characteristics for which design risk is known and acceptably small;
(b) selecting a plurality of circuit blocks to be used in the circuit design;
(c) receiving predetermined design characteristics for the circuit blocks;
(d) assessing a first feasibility using the existing methodology based upon the field of use characteristics, the first feasibility including a first risk indicator and first time/cost indicator;
(e) receiving at least a second design characteristic which has not been used in the existing methodology;
(f) processing the second design characteristic to accommodate the existing methodology; and
(g) assessing a second feasibility using the existing methodology based on the field of use characteristics and the second design characteristic, the second feasibility including a second risk indicator, and a second time/cost indicator, wherein the second risk indicator has not been substantially increased compared with the first risk factor due to the use of the existing methodology, and the second time/cost factor has been increased compared with the first time/cost factor due to the impact of the second design characteristic.

### Claim 22 (depends on 21)

The method of claim 21, where in the predetermined design characteristics are within the definition of the field of use data, and the error-risk associated with correct prediction of the second type of design characteristic being known from either estimation data or implementation data.

### Claim 23

A method for expanding an existing methodology for assessing feasibility of a circuit design based upon a predetermined set of design characteristics, the method comprising of:
(a) determining to be the field of use a set of design characteristics for which design risk is known and small;
(b) selecting a plurality of circuit blocks to be used in the circuit design;
(c) receiving predetermined design characteristics for the circuit blocks;
(d) assessing a first feasibility using the existing methodology based upon the field of use characteristics, the first feasibility including a first risk indicator and first time/cost indicator;
(e) receiving at least a second design characteristic which has not been used in the existing methodology;
(f) changing the existing methodology to accommodate the second type of design characteristic;
(g) assessing the second feasibility using the changed methodology based on the field of use design characteristics and the second type of design characteristic, the second feasibility including a second risk indicator, and a second time/cost indicator, wherein the second risk indicator has been increased compared with the first risk factor due to the change of the existing methodology, and the second time/cost factor has not been substantially increased compared with the first time/cost factor due to the change of the existing methodology.

### Claim 24 (depends on 23)

The-method of claim 23, where in the predetermined design characteristics are within the definition of the field of use data, and the error-risk associated with correct prediction of the second type of design characteristic being known from either estimation data or implementation data.

### Claim 25

A method for performing a feasibility assessment for a circuit design, comprising the steps of:
(a) receiving requirements and constraints for the circuit design;
(b) selecting a plurality of pre-designed circuit blocks to be used in the circuit design;
(c) collecting field of experience data for the circuit blocks;
(d) forming a first level decision rule using the field of experience data for the circuit blocks, the first level decision rule including an acceptance region, a rejecting region, and an uncertain region;
(e) making a first level predication using the requirements and constraints based on the first level decision rule;
(f) accepting the circuit design if the first level predication is within the acceptance region of the first level decision rule, and rejecting the circuit design if the first level predication is within the rejecting region of the first level decision rule; and
(g) forming a second level decision rule for making a second level predication for the circuit design, if the first level prediction is within the uncertain region of the first level decision rule.

### Claim 26 (depends on 25)

The method of claim 25, further comprising the steps of:
(h) collecting estimation data for the circuit blocks, wherein the second level decision rule in (g) is formed using the estimation data, the second level decision rule including an acceptance region, a rejecting region, and an uncertain region;
(i) making the second level predication using the requirements and constraints based on the second level decision rule;
(j) accepting the circuit design if the second level prediction is within the acceptance region of the second level decision rule, and rejecting the circuit design if the second level predication is within the rejecting region of the second level decision rule; and
(k) forming a third level decision rule for making a third level predication for the circuit design, if the second level prediction is within the uncertain region of the second level decision rule.

### Claim 27 (depends on 26)

The method of claim 26, further comprising the steps of:
(L) collecting implementation data for the circuit blocks, wherein the third level decision rule in (k) is formed using the implementation data, the third level decision rule including an acceptance region, a rejecting region, and an uncertain region;
(m) making the third level prediction using the requirements and constraints based on the third level decision rule;
(n) accepting the circuit design if the third level prediction is within the acceptance region of the third level decision rule, and rejecting the circuit design if the third level predication is within the rejecting region of the third level decision rule.

### Claim 28 (depends on 27)

The method of claim 27, wherein:
the estimation data has a higher cost of collection and a higher accuracy than the field of experience data; and
the implementation data has a higher cost of collection and a higher accuracy than the estimation data.

### Claim 29

A method for refining a first decision rule for a circuit design, comprising the steps of:
(a) receiving requirements and constraints of a circuit design;
(b) selecting a plurality of pre-designed circuit blocks to be used in the design;
(c) identifying at least one of the circuit blocks as a critical circuit block and the rest of the circuit blocks as non-critical circuit blocks;
(d) collecting field of experience data for the non-critical circuit blocks, and collecting estimation data and/or implementation data for the critical circuit block; and
(e) forming a refined first decision rule by combining the field of experience data with the estimation data or implementation data.

### Claim 30 (depends on 29)

The method of claim 29, the decision rule including an acceptance region, a rejecting region, and an uncertain region, the method further comprising the steps of:
(f) making a prediction using the requirements and constraints based on the refined decision rule in (e); and
(g) accepting the circuit design if the predication is within the acceptance region, and rejecting the circuit design if the predication is within the rejecting region.

### Claim 31 (depends on 30)

The method of claim 30, wherein:
the estimation data has a higher cost of collection and a higher accuracy than the field experience data; and
the implementation data has a higher cost of collection and a higher accuracy than the estimation data.

### Claim 32

A method for forming a second decision rule for a circuit design, comprising the steps of:
(a) receiving requirements and constraints of the circuit design;
(b) selecting a plurality of pre-designed circuit blocks;
(c) identifying at least one of the circuit blocks as a critical block and the rest of the circuit blocks as non-critical circuit blocks;
(d) collecting estimation data for the non-critical circuit blocks, and collecting implementation data for the critical circuit block; and
(e) forming a refined second decision rule by using the estimation data and the implementation data.

### Claim 33 (depends on 32)

The method of claim 32, the decision rule including an acceptance region, a rejecting region, and an uncertain region, the method further comprising the steps of:
(f) making a predication using the requirements and constraints based on the refined decision rule in (e); and
(g) accepting the circuit design if the prediction is within the acceptance region, and rejecting the circuit design if the predication is within the rejecting region.

### Claim 34 (depends on 33)

The method of claim 33, wherein:
the implementation data has a higher cost of collection and a higher accuracy than the estimation data.

### Claim 35

A method for organizing experience data of a designer regarding a plurality of pre-designed circuit blocks to be used to design a circuit system, wherein the method is executed by the designer and the experience data is used to perform a feasibility assessment for the circuit system design, the method comprising the steps of:
(a) defining a set of parameters by which experience data can be measured;
(b) identifying experience data of the designer regarding the circuit blocks;
(c) classifying the identified designer's experience data into a plurality of classes, wherein the experience data classes correspond to the circuit blocks;
(d) using the designer's experience data to form a decision rule, the decision rule including an acceptance region, a rejecting region, and an uncertain region; and
(e) making a prediction using the requirements and constraints based on the decision rule.

### Claim 36 (depends on 35)

The method of claim 35, further comprising the step of:
(f) accepting the circuit system design if the estimation is within the acceptance region of the decision rule, and rejecting the circuit system design if the estimation is within the rejecting region of the decision rule.

### Claim 37 (depends on 35)

The method of claim 35, further comprising the step of:
(f) refining the classes of the experience data to minimize feasibility assessment error.

### Claim 38 (depends on 35)

The method of claim 35, further comprising the step of:
(f) certifying the experience data.

### Claim 39 (depends on 35)

The method of claim 35, wherein the identified experience data includes at least one of predicted experience data or collated experience data.

### Claim 40 (depends on 35)

The method of claim 35, further comprising the step of:
(f) building a model upon the identified designer's experience data to predict similar parameters of a similar design.

### Claim 41

For execution in an integrated circuit device design scheme, wherein a device design comprises a plurality of pre-existing design blocks, a method of increasing glue logic distribution efficiency, the method comprising the steps of:
copying a selected glue logic element, thereby creating a duplicate element set including said selected element and its copy;
distributing said duplicate element set to the plurality of design blocks.

### Claim 42

For execution in an integrated circuit device design scheme, wherein a device design comprises a plurality of pre-existing design blocks, a method of distributing a plurality of glue logic elements among the design blocks, the method comprising the steps of:
if a first glue logic element includes an output net driving a plurality of loads, splitting the first element into a plurality of derivative glue logic elements; and
distributing said derivative elements to the plurality of design blocks.

### Claim 43 (depends on 42)

The method of claim 42, wherein each derivative element includes only a single output load.

### Claim 44 (depends on 42)

The method of claim 42, wherein if a first glue logic element includes a plurality of inputs, the split element is the first element.

### Claim 45 (depends on 42)

The method of claim 42, wherein a derivative element includes only two-inputs.

### Claim 46

For execution in an integrated circuit device design scheme, wherein a device design comprises a plurality of pre-existing design blocks, a method of distributing a plurality of glue logic elements among the design blocks, the method comprising the steps of:
analyzing the plurality of elements for a selected quality;
merging a selected glue logic element into a selected block in a manner based upon the analysis.

### Claim 47 (depends on 46)

The method of claim 46, wherein the selected block is selected in a manner based upon its functional affinity to the selected element.

### Claim 48 (depends on 47)

The method of claim 47, wherein said functional affinity comprises whether the merger would reduce the number of physical I/O elements required for the proper function of said circuit device design.

### Claim 49 (depends on 46)

The method of claim 46, wherein if two or more design blocks are equal candidates for the merger, the block having the lowest pin density is chosen.

### Claim 50 (depends on 47)

The method of claim 47, wherein said functional affinity comprises whether a selected element and a selected block together have improved chip level timing characteristics.

### Claim 51

For execution in an integrated circuit device design scheme, wherein a device design comprises a plurality of pre-existing design blocks, a method of distributing glue logic, the method comprising the steps of:
identifying a plurality of elements that can be neither copied and distributed among the design blocks or merged with the design blocks;
clustering the identified plurality of elements.

### Claim 52 (depends on 51)

The method of claim 51, wherein each of the clustered elements includes multiple loads on input nets and multiple loads on output nets.

### Claim 53 (depends on 51)

The method of claim 51, wherein the plurality of elements include inputs having similar function.

### Claim 54

For execution in an integrated circuit device design scheme, wherein a device design comprises a plurality of pre-existing design blocks, a method of distributing glue logic among the design blocks, the method comprising the steps of:
identifying a first feature of a first glue logic element;
identifying a second glue logic element having a second feature making the second glue logic element compatible with the first glue logic element;
merging said first glue logic element with the identified second glue logic element.

### Claim 55 (depends on 54)

The method of claim 54 wherein said first feature comprises the number of pins required by said first glue logic element.

### Claim 56 (depends on 54)

The method of claim 54 wherein said first feature comprises the input structure of said first glue logic element.

### Claim 57 (depends on 54)

The method of claim 54 wherein said first feature comprises the output structure of said first glue logic element.

### Claim 58 (depends on 54)

The method of claim 54 wherein the second glue logic element is a design block.

### Claim 59

A method for converting a specific interface of a circuit block, the method comprising the steps of:
(a) defining a standard interface; and
(b) connecting a collar interface to the circuit block, the interface having a first portion connectable to the circuit block, a second portion in compliance with the standard interface, and a third portion for converting the specific interface into the standard interface.

### Claim 60 (depends on 59)

The method of claim 59, wherein the collar interface can be in hard, soft, or firm format.

### Claim 61 (depends on 59)

The method of claim 59, wherein the circuit block is a memory, a processor, a random logic, or an analog/mixed signal.

### Claim 62 (depends on 59)

The method of claim 59, wherein the collar interface includes multiple layers, including a block-specific standard layer and a system-specific layer.

### Claim 63

A method for connecting a first circuit block and a second circuit block, the first circuit block having a first specific interface and the second circuit block having a second specific interface, the method comprising the steps of:
(a) defining a standard interface for connecting the first and second circuit blocks;
(b) connecting a first collar interface to the first circuit block, the first interface having a first portion connectable to the first circuit block, a second portion in compliance with the standard interface, and a third portion for converting the first specific interface into the standard interface;
(c) connecting a second collar interface to the second circuit block, the second collar interface having a first portion being able to be connected to the second circuit block, a second portion in compliance with the standard interface, and a third portion for converting the second specific interface into the standard interface; and
(d) connecting the first and second circuit blocks using the standard interface.

### Claim 64 (depends on 63)

The method of claim 63, wherein the first and second collar interfaces can be in hard, soft, or firm format.

### Claim 65 (depends on 63)

The method of claim 63, wherein the first and second circuit block is a memory, a processor, a random logic, or an analog/mixed signal.

### Claim 66 (depends on 63)

The method of claim 63, wherein the first and second collar interfaces include multiple layers, including a block-specific standard layer and a system-specific layer.

### Claim 67

A collar interface for converting a specific interface of a circuit block into a standard interface the collar interface comprising:
(a) a first portion containing components connectable to the specific interface of the circuit block;
(b) a second portion in compliance with the standard interface; and
(c) a third portion for converting the specific interface into the standard interface.

### Claim 68 (depends on 67)

The collar interface of claim 67, wherein the apparatus can be in hard, soft, or firm format.

### Claim 69 (depends on 67)

The collar interface of claim 67, wherein the circuit block is a memory, a processor, a random logic, or an analog/mixed signal.

### Claim 70 (depends on 67)

The collar interface of claim 67, wherein the collar includes multiple layers, including a block-specific standard layer and a systemspecific layer.

### Claim 71

An interface system for connecting a first circuit block and a second circuit block through a standard interface, the first circuit block having a first specific interface and the second circuit block having a second specific interface, the interface system comprising:
(a) a first collar interface connected to the first circuit block, the first collar interface including (1) a first portion containing components connectable to the specific interface of the first circuit block, (2) a second portion in compliance with the standard interface, and (3) a third portion containing components for converting the first specific interface into the standard interface; and
(b) a second collar interface connected to the second circuit block, the second collar interface including (10) a first portion containing components connectable to the specific interface of the second circuit block, (2) a second portion in compliance with the standard interface, and (3) a third portion containing components for converting the second specific interface into the standard interface.

### Claim 72 (depends on 71)

The interface system of claim 71, wherein the first and second collar interfaces can be in hard, soft, or firm format.

### Claim 73 (depends on 71)

The interface system of claim 71, wherein the first and second circuit block is a memory, a processor, a random logic, or an analog/mixed signal.

### Claim 74 (depends on 71)

The interface system of claim 71, wherein the first and second collar interfaces include multiple layers, including a block-specific standard layer and a system-specific layer.

### Claim 75

In a circuit design method, wherein a circuit under design comprises a plurality of pre-existing design blocks, a method of selecting a circuit bus, the method comprising the steps of:
observing data transactional behavior between the plurality of design blocks;
deriving from the observed transactional behavior a plurality of bus criteria;
selecting a bus structure from a library of available bus design blocks in a manner based upon said plurality of bus criteria;
integrating said selected bus structure into said circuit.

### Claim 76 (depends on 75)

The method of claim 75, wherein said plurality of bus criteria comprise at least one member of the group consisting of bus size, bus bandwidth, bus performance level, and signal latency.

### Claim 77 (depends on 75)

The method of claim 75 further comprising, before selecting a bus, clustering the plurality of design blocks according to a plurality of communication requirements between the blocks, thereby forming a plurality of block clusters.

### Claim 78 (depends on 77)

The method of claim 77, wherein assigned to each formed cluster is a bus selection criteria comprising at least one member of the group consisting of bus size, bus bandwidth, bus performance level, and signal latency.

### Claim 79 (depends on 75)

The method of claim 75, wherein the deriving step comprises deriving requirements for communications between at least one of the blocks and an I/O structure within the circuit.

### Claim 80 (depends on 75)

The method of claim 75, further comprising mapping the selected bus structure into the circuit by modifying its bus interface logic.

### Claim 81 (depends on 75)

The method of claim 75, wherein said deriving step comprises:creafing a data transfer matrix, including a plurality of data transfer count entries; and
organizing the data transfer matrix by moving the largest of the counts toward a central axis in the matrix;

### Claim 82 (depends on 81)

The method of claim 81, wherein said deriving step further comprises:
weighting the count entries according to a selected weighting criteria.

### Claim 83 (depends on 77)

The method of claim 77, wherein said deriving step comprises creating a cluster value matrix, including a plurality of data representing distribution of data flow within the bus to be selected;
optimizing data flow within the bus to be selected by selectively reorganizing said distribution data.

### Claim 84 (depends on 75)

The method of claim 75, wherein the step of observing data transactional behavior is performed on a behavioral model.

### Claim 85 (depends on 84)

The method of claim 84, wherein the behavioral model includes a plurality of design blocks and an I/O structure.

### Claim 86 (depends on 84)

The method of claim 84, wherein the behavioral model is modified to collect transaction data.

### Claim 87

In a block based design methodology for realizing a circuit design, the design comprising a plurality of pre-existing design blocks, a method of designing a device embodying the design and enabling testing of the device after manufacture, the method comprising the steps of:
establishing a test development framework;
developing, in compliance with the framework, a plurality of test blocks for testing the design blocks;
mapping the plurality of test blocks to develop, in compliance with the framework, a test for the circuit design.

### Claim 88 (depends on 87)

The method of claim 87, wherein the establishing step comprises identifying the plurality of pre-existing design blocks according to a set of qualifiers, said qualifiers comprising at least one entry from the group consisting of a test model, a test method, a test data, and a test interface.

### Claim 89 (depends on 88)

The method of claim 88, wherein the set of qualifiers comprises an abstraction of the design blocks, enabling top-down test planning.

### Claim 90 (depends on 87)

The method of claim 87, wherein the framework comprises a test budget for each of the blocks.

### Claim 91 (depends on 87)

The method of claim 87, further comprising enabling concurrent testing on more than one of the blocks.

### Claim 92 (depends on 91)

The method of claim 91, wherein said enabling step comprises expanding a device-level test interface.

### Claim 93 (depends on 91)

The method of claim 91, wherein said enabling step comprises manipulating a tester timeset to minimize tester setup time between test blocks.

### Claim 94 (depends on 87)

The method of claim 87, further comprising packaging the framework and a block test as a test-ready design block for test re-usability.

### Claim 95

A method of designing an integrated circuit device for post-manufacturing testability, the circuit comprising a plurality of pre-existing design blocks, the method comprising the steps of:
abstracting each of the pre-existing blocks to establish a circuit test development framework;
formulating a design scheme, including a plurality of tests, for the device while maintaining a predictable estimation of the overall testability of the circuit design.

### Claim 96 (depends on 95)

The method of claim 95, wherein the circuit testing framework is optimized for a plurality of test objectives.

### Claim 97 (depends on 95)

The method of claim 95, wherein the circuit testing framework will be rejected if a risk level of reaching a pre-determined block testability level is greater than an acceptable level.

### Claim 98 (depends on 95)

The method of claim 95, wherein the framework comprises test cost budgeting criteria.

### Claim 99 (depends on 98)

The method of claim 98, further comprising the execution of test efficacy exchanges by adding a test to the design scheme.

### Claim 100 (depends on 98)

The method of claim 98, further comprising the execution of test efficacy exchanges by removing a test from the design scheme.

### Claim 101 (depends on 95)

The method of claim 95, further comprising refining the design scheme within designated tolerances.

### Claim 102 (depends on 95)

The method of claim 95, further comprising enabling concurrent test development as part of the design scheme, by allowing each block to be tested with a selected suitable test method.

### Claim 103 (depends on 95)

The method of claim 95, wherein the design scheme includes a test interface and the interface is compatible with a plurality of dissimilar test protocols.

### Claim 104 (depends on 95)

The method of claim 95, further comprising simplifying a test scheduling portion of the design scheme by concurrently executing more than one block test.

### Claim 105 (depends on 95)

The method of claim 95, further comprising duplicating test vectors among design blocks, thereby reducing the elapsed time between test blocks with the design scheme.

### Claim 106 (depends on 95)

The method of claim 95, wherein a plurality of similar test blocks are executed consecutively, thereby reducing elapsed test time.

### Claim 107 (depends on 95)

The method of claim 95, further comprising using designer feedback to update the design scheme for adaptation to a plurality of circuit designs.

### Claim 108

A method of verifying the proper function of a circuit design, the design comprising a plurality of pre-existing design blocks, the method comprising the steps of:
obtaining a circuit design model and a circuit test bench;
partitioning the circuit design model into a plurality of block models;
creating a bus model interconnecting the plurality of block models;
creating a plurality of test benches for verifying the plurality of block models and bus model;
using the test benches to verify the function of the plurality of block models and the bus model.

### Claim 109 (depends on 108)

The method of claim 108, wherein the circuit design model includes a top level.

### Claim 110 (depends on 108)

The method of claim 108, wherein the bus model comprises glue logic circuitry from the block models.

### Claim 111 (depends on 108)

The method of claim 108, wherein verifying the function of a block model comprises register transfer language verification.

### Claim 112 (depends on 108)

The method of claim 108, wherein verifying the function of a block model comprises pre-layout netlist verification.

### Claim 113 (depends on 108)

The method of claim 108, wherein verifying the function of a block model comprises post-layout netlist verification.

### Claim 114 (depends on 108)

The method of claim 108, wherein after attempting to verify the plurality of block models, the plurality of block models are modified for cycle accuracy.

### Claim 115 (depends on 108)

The method of claim 108, further comprising the steps of:
developing a test bench for the circuit design; and
attempting to verify the function of the circuit design.

### Claim 116 (depends on 115)

The method of claim 115, wherein verifying the function of the circuit design comprises register transfer language verification.

### Claim 117 (depends on 115)

The method of claim 115, wherein verifying the function of the circuit design comprises pre-layout netlist verification.

### Claim 118 (depends on 115)

The method of claim 115, wherein verifying the function of the circuit design comprises post-layout netlist verification.

### Claim 119 (depends on 108)

The method of claim 108, wherein after attempting to verify the circuit design, the circuit test bench is modified for cycle accuracy.

### Claim 120

A method for evolving an initial behavioral level test bench with no timing content into a cycle accurate test bench suitable for functional verification of all timing accurate views of the design, the method comprising the steps of:
determining invariant output of execution of the design on the test bench;
modifying the test bench to include clocks;
executing the modified test bench on a timing accurate model; and
comparing the invariant output of the test bench.

### Claim 121

A method of verifying the proper function of a circuit design, the design comprising a plurality of pre-existing design blocks, the method comprising the steps of:
obtaining a circuit design model including a top level and a plurality of block models;
obtaining circuit test bench;
creating a bus model interconnecting the plurality of block models;
creating a plurality of test benches for verifying the plurality of block models and bus model;
using the test benches to verify the function of the plurality of block models and the bus model.

### Claim 122

A method for evolving an initial behavioral level test bench without timing content into a cycle accurate test bench suitable for functional verification of substantially timing-accurate views of a design, the method comprising the steps of:
determining an invariant output of execution of the design on the test bench;
modifying the test bench to include clocks;
executing the modified test bench on a substantially timing-accurate model; and
comparing the invariant output of the testbenches.
