JPH0844782A - Design data management device - Google Patents

Abstract

PURPOSE:To reduce unnecessary consistency storing operation by generating information on the reference dependency relation between a component information library and design data and matching the design data by using the information. CONSTITUTION:An alteration object library identifier and its item of alteration information inputted from a library alteration information input part 1 are inputted to a library reference design data extraction part 4, which uses them as a key to extracts a reference design data identifier for referring to the item of an alteration object library from a library reference design data information storage part 3. An update object design data selection part 5 is supplied with the item of the alteration object library and the reference design data identifier for referring to it from the library reference design data information storage part 3, searches for dependency relation information on the design data by using the reference design data identifier as a key, and further selects slave design data to be altered out of the library item information.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a design data management apparatus, and more particularly to designing in a design environment in which design data generated by each design tool has a mutual dependency relationship for designing by combining a plurality of design tools. The present invention relates to a data management device.

[0002]

2. Description of the Related Art A plurality of design tools (corresponding to a CAD program, such as a circuit design using a CAD in recent years, a circuit diagram editor is used to input a circuit diagram, and whether a circuit input in the circuit diagram operates as designed. When designing using a combination of a circuit simulator and the results of the circuit simulator as a graphical waveform or a waveform editor that edits the waveform for verification, the design data generated by each design tool is As they become related to each other, maintaining consistency between design data is an important issue.

The design data management device used for maintaining the consistency between the design data is conventionally designed in the case where the design data are hierarchical as described in Japanese Patent Laid-Open No. 2-36439. Saves reference dependencies between layers in the database, manages which layer of design data is affected when a part of the layered design data is updated, and identifies the affected design data. Then, the design data is updated to maintain the consistency.

[0004] Then, as a trigger for updating the affected design data, the first device which pays attention to the activation of the design tool used to create the design data and the first device which pays attention to the update date and time of the design data There are two devices.

The above will be described by taking as an example the case where circuit diagram data is created using a circuit diagram editor, and this circuit diagram data is input and a simulation result is created using a circuit simulator.

Since the simulation result is obtained by executing the circuit simulator with the circuit diagram data as an input, when the circuit diagram data is changed, it is necessary to execute the circuit simulator again to update the simulation result. However, in the above-mentioned first device, whether or not the circuit diagram editor is used to determine whether or not to recreate the simulation result is not directly determined by checking whether or not the circuit diagram data is updated and whether or not the circuit diagram editor is used. Judging from the information. This is because if the circuit diagram editor is used, the circuit diagram may have been rewritten, so the circuit simulation is executed again, and this operation always guarantees that the simulation results are consistent with the latest circuit diagram data. .

Since the circuit simulation is performed after the circuit diagram is created and the simulation result is output, the simulation result must be created after the circuit diagram. Therefore, in the above-described second device, when the circuit diagram data is changed by the circuit diagram editor, the creation date and time of the update of the circuit diagram data is later than the creation date and time of the simulation result. Rerun the circuit simulation.

[0008]

As described above, the conventional design data management apparatus performs the operation of maintaining the consistency of the design data based on the result of the start of the design tool and the comparison result of the design data update date and time. ing.

Therefore, even when a change that does not affect the creation of the subsequent design data is made, for example, when additional information such as a cautionary note or a comment is described, for the purpose of updating the subsequent design data. There is a problem that the design tool is re-executed, and a great amount of time is wasted for unnecessary consistency saving operation.

Further, in the above-mentioned first device which pays attention to the activation of the design tool, even if the design data is not changed, the subsequent reprocessing operation of the design data is performed every time the design tool is activated. However, this also has a problem that a large amount of time is wasted for unnecessary consistency saving operation.

It is an object of the present invention to create reference dependency relationship information between a component information library and design data based on at least the content of items in the component information library, and use this to ensure design data consistency. It is an object of the present invention to provide a design data management device capable of reducing the necessary consistency saving operation.

[0012]

A design data management apparatus according to a first aspect of the invention is to create an identifier of design data and an identifier of one or more child design data created based on the design data and the creation of the child design data. The design data dependency information storage means for storing, for each design data, the library item information including, for each item, the identifier of the child design data that is affected by the change in the contents of the component information library adopted at the time, and the component information library Library reference design data information storage means for storing, for each component information library, an identifier and item information including, for each item, an identifier of reference design data that directly refers to the identifier, and library change information for inputting change information of the component information library In response to the supply of the change information, the reference design data identifier corresponding thereto is input to the library reference setting unit. Library reference design data extraction means for extracting from the data information storage means, and an identifier of update target design data to be updated corresponding to the change information in response to supply of the change information and the corresponding reference design data identifier To be updated from the design data dependency relationship information storage means.

The design data management apparatus of the second invention is the first invention.
In addition to the above invention, it comprises an update target design data display means for displaying the identifier of the supplied update target design data.

[0014]

Embodiments of the present invention will now be described with reference to the drawings.

FIG. 1 is a block diagram showing an embodiment of the design data management apparatus of the present invention.

The design data management apparatus of FIG. 1 has a design data B when designing using a plurality of design data.
For each item of the component information library adopted at the time of creation, information indicating the design data dependency relationship (A is referred to as parent design data and B is referred to as child design data hereinafter) of which design data A is created The design data dependency information storage unit 2 that stores the affected child design data information for each parent design data, the component information library used to create the design data, and the library is directly referenced to change and update them. Library reference design data information storage unit 3 that stores design data information that directly affects each library item, library change information input unit 1 that inputs change information of the library, and library reference using the library change information as a key A line for searching and extracting design data referring to the changed library item from the design data information storage unit 3. Update reference design data extraction unit 4, an update target design data selection unit 5 that selects update target design data from the design data dependency relationship storage unit 2 in response to library change information and corresponding library reference design data information, and update An update target design data display unit 6 that receives and displays the target design data name is displayed.

The library reference design data extraction unit 4 and the update target design data selection unit 5 operate as a data processing unit 3 including a main memory and a central processing unit under program control.

FIG. 2 shows a design data dependency information storage unit 2
An example of the stored contents stored in FIG.

As described above, this stored content has, for each parent design data, information as to what the design data and the child design data created based on it are as information.
Further, child design data that is affected by updating the contents of the items of the library adopted at the time of creation is stored for each item.

That is, the design data dependency relationship information 21 shown in FIG. 2 includes a record identifier (DATA as an example in the case of design data) indicating that it is design data, and a design data identifier assigned to its parent design data (an example). Number), the name of the parent design data, the child design data identifiers (1) to (n) that are the identifiers of the n child design data created based on the design data, and the creation thereof. It is configured to have m pieces of library item information (1) to (m) which are child design data information affected by updating the contents of the library item adopted at that time.

The library item information is, as indicated by reference numeral 22 in FIG. 2, a record identifier indicating that it is library data (LIB data is an example of LIB), and a library identifier assigned to the library data. It has at least one piece of information including a set of an item name adopted in this library and a child design data identifier which is an identifier of one or more child design data affected by the item name.

The library itself can be registered in the design data stored in the design data dependency information storage unit 2.

Next, the storage contents stored in the library reference design data information storage unit 3 will be described.

As described above, the stored contents are the component information information library used to create the design data and the design data information that directly refers to the library, and are stored for each item of the library.

The parts information library is a collection of data such as names of electric parts used for designing a circuit, input / output terminal names, parts shape, power consumption, operation, manufacturer, price and the like. Since the required information differs for each design tool, that is, for each CAD program, there is a component information library for each design tool for the same component. For example, a circuit diagram library is prepared for the circuit diagram editor, a simulation library is prepared for the circuit simulator, and a layout library is prepared for the layout program.

FIG. 3 shows an example of storage contents stored in the library reference design data information storage unit 3, that is, an example of library reference design data information.

Library reference design data information 31 in FIG.
Is a record identifier indicating library data (LIB data is an example of LIB),
It is configured to include a library identifier assigned to this library data (a numeral as an example), the name of this library data, and one or more item information that is information for each item of this library.

The item information is, as indicated by reference numeral 32 in FIG. 3, a record identifier (for example, ITEM) indicating that it is item information, an item name, and an identifier of design data that directly refers to this item. And one or more of the reference design data identifiers.

The library change information input from the library change information input unit 1 is composed of a library identifier to be changed, its item name, and the changed contents of the item, and is input from a known keyboard or the like. . According to the change information, the library to be changed is updated by a predetermined change.

The change target library identifier and its item name of this change information are input to the library reference design data extracting section 4, and the library reference design data extracting section 4 uses the library reference design data extracting section 4 as a key for the library reference design data information storage section 3 A reference design data identifier that refers to the item of the change target library is extracted from.

The update target design data selection unit 5 receives the items of the change target library and the reference design data identifiers that refer to the items from the library reference design data information storage unit 3, and uses the reference design data identifiers as keys. The design data dependency information is searched, and the child design data to be changed is selected from the library item information using the item of the change target library as a key. Then, using the child design data as new reference design data, the above search and selection operation is continued until there is no child design data, and all the design data to be updated including the self design data are selected without omission.

The update target design data display unit 6 displays the update target design data name supplied from the update target design data selection unit 5.

Next, the operation of this embodiment will be described in detail by using an actual design data flow.

FIG. 4 shows a reference numeral 41 for the flow of design data generated in the design work from the circuit diagram preparation to the parts table preparation, and reference numeral 42 for the library used.

When creating the circuit diagram data, only the circuit diagram library is used, and when creating the netlist, no specific library is used. To create a simulator when executing a simulation, create it from the netlist data and the simulation library. The layout data is created from the netlist data and the layout library. The parts table data is created from the circuit diagram data.

FIG. 5 shows a specific example of the design data dependency relationship information defined by the flow of the design data in FIG. 4, and a record identifier is placed in the head field of the record.

When the record identifier is "DATA", the design data identifier is in the second field, the design data name is in the third field, and the child design data created based on this design data after the fourth field. The child design data identifier, which is the identifier of, is described.

The record having the record identifier "LIB" describes the item information of the library adopted when the child design data of the design data described immediately before is created. The library identifier used for the second field, the item name of the library for the third field,
The child design data identifier, which is the identifier of the child design data affected after the fourth field, is described.

By describing the library item information, it can be specified that the corresponding child design data is updated only for the change / update information of a specific item among the items of the library referred to by the parent design data. .

In FIG. 5, the circuit diagram data with the design data identifier 1 indicates that the netlist data with the design data identifier 2 and the parts table data with the design data identifier 6 are created based on this. There is. Further, there is library item information, and for the schematic data, the symbol name (symna) of the schematic library whose library identifier is 1.
me), pin name (pinname), and part name (BM-N)
When the AME) is changed, both the netlist data and the parts table data of the design data identifiers 2 and 6 are affected.

The netlist data having the design data identifier 2 indicates that the simulator having the design data identifier 3 and the layout data having the design data identifier 5 are created based on the netlist data. In addition, there is library item information, and the component name of the circuit diagram library whose library identifier is 1 for the netlist data (BM-NAME)
Is changed, only the layout data having the design data identifier 5 is affected, and the simulator data having the design data identifier 3 is not affected.

The simulator with the design data identifier 3 indicates that the simulation result data with the design data identifier 4 is created based on this.

The simulation result data with the design data identifier 4, the layout data with the design data identifier 5, and the parts table data with the design data identifier 6 indicate that there is no design data created based on these. .

The items whose design data identifiers are 7 to 9 define the library to which the design data defined on the design data flow refers, and it can be shown that the change of the library affects other libraries. I can do it.

FIG. 6 is a specific example of library reference design data information. A record starting with "LIB" defines a library identifier and a library name, and a record starting with "ITEM" is item information. For each information item in the defined library, this item is directly referenced to define a reference design data identifier which is an identifier of design data directly affected by the change.

A plurality of "ITEM" records can be specified.

The library identifier 1 is a circuit diagram library, and the symbol name (symna in the items of this library is
(me) is changed and the pin name (pinname) is changed, it is necessary to modify the circuit diagram data of the design data identifiers 1, 8 and 9 and the simulation library and the layout library. BM-N
AME) has changed, the design data identifier is 1
And 9, the circuit diagram data and the layout library need to be corrected, and when the shape is changed, the circuit diagram data having the design data identifier 1 needs to be corrected.

The library identifier 2 is a simulation library, and when the operation logic (logic) is changed, the simulation result data with the design data identifier 4 needs to be modified, and the symbol name (symna) is changed.
(me) and the pin name (pinname) are changed, the simulators of the design data identifiers 3 and 7 and the circuit diagram library need to be modified.

In the layout library with the library identifier of 3, when the layout information (layout) is changed, only the layout data with the design data identifier of 5 needs to be modified. The symbol name (symname) and the pin name ( If there is a change in the pinname), it is necessary to modify the circuit diagram data and the circuit diagram library having the design data identifiers 1 and 7.

The design data dependency relationship information and the library reference design data information have been described above with reference to FIGS. 5 and 6 for concrete examples. However, for convenience of explanation, only a part of the dependency relationship between the circuit diagram library and the circuit diagram data will be described. This is merely an example and illustration of other relationships is omitted.

A design data management device in which the design data dependency relationship information shown in FIG. 5 is stored in the design data dependency relationship information storage unit 2 and the library reference design data information shown in FIG. 6 is stored in the library reference design data information storage unit 3. On the other hand, the operation will be described by taking the first case where the component name of the circuit diagram library is changed and the second case where the shape is changed as an example.

When the change target library name and the change target item name are supplied to the library reference design data extraction unit 4 via the library change information input unit 1, the library reference design data extraction unit 4 uses them as keys. Library reference design data is extracted from the library reference design data information storage unit 3.

Referring to FIG. 6, in the first case where the component name of the circuit diagram library is changed, the reference design data identifiers 1 and 9 are extracted. Therefore, the library reference design data extraction unit 4 supplies the reference design data identifiers 1 and 9 and the component name of the circuit diagram library that is the change target item to the update target design data selection unit 5.

The update target design data selecting unit 5 updates from the design data dependency information storage unit 2 by using the supplied reference design data identifiers 1 and 9 and the component name of the circuit diagram library which is the change target item as a key. Select the target design data. That is, referring to FIG. 5, first, the circuit diagram data and the layout library are selected from the reference design data identifiers 1 and 9. Further, the child design data identifiers 2 and 6 are obtained from the library item information of the circuit diagram data. That is, the netlist data and the parts table are obtained. Further, the layout data of the child design data identifier 5 is obtained from the library item information of the netlist data, and as a result, the update target design data selection unit 5 design data identifiers 1, 2, 5, 6 and 9 as the update target design data.
Output schematic diagram data, netlist data, layout data, parts list and layout library,
The update target design data display unit 6 displays these.

Next, in the second case where the shape is changed, referring to FIG. 6, the library reference design data extraction unit 4
Supplies the reference design data identifier 1 and the shape of the circuit diagram library that is the change target item to the update target design data selection unit 5.

Next, the update target design data selecting unit 5 uses the supplied reference design data identifier 1 and the shape of the circuit diagram library which is the change target item as keys to update from the design data dependency information storage unit 2. Select design data. Referring to FIG. 5, first, circuit diagram data is obtained from the related design data identifier 1. Since this circuit diagram data does not have the library item information regarding the shape, the child design data created based on this circuit diagram does not become the update target design data, and the output of the update target design data selection unit 5 in the second case As a result, only the circuit diagram data is displayed, and the update target design data display unit 6 displays it.

Considering the second case, conventionally, if the circuit diagram library is updated and the circuit diagram is updated by the circuit diagram editor, the subsequent data, that is, the netlist, is simply used because the circuit diagram editor is used. The data of the simulator, the simulation result, the layout, and the parts table have been reconstructed, but in the present embodiment, only the circuit diagram is reconstructed, and unnecessary matching operation is not necessary.

Even in the first case, design data identifiers 3 and 4
There is no need to perform the simulator and the reconstruction operation of the simulation result.

[0059]

As described above, the design data management device of the present invention creates reference dependency information between the component information library and the design data based on at least the item contents of the component information library and uses it. By making the design data consistent with each other, it is possible to reduce an unnecessary consistency saving operation.

[Brief description of drawings]

FIG. 1 is a configuration diagram showing an embodiment of a design data management device of the present invention.

FIG. 2 is a data storage diagram of a design data dependency relationship information storage unit.

FIG. 3 is a data storage diagram of a library reference design data information storage unit.

FIG. 4 is a data flow diagram showing the relationship between design data and each library.

FIG. 5 is a data structure diagram showing an example of design data dependency relationship information.

FIG. 6 is a data structure diagram showing an example of library reference design data information.

[Explanation of symbols]

 1 Library Change Information Input Section 2 Design Data Dependency Information Storage Section 3 Library Reference Design Data Information Storage Section 4 Library Reference Design Data Extraction Section 5 Update Target Design Data Selection Section 6 Update Target Design Data Display Section 7 Data Processing Section 21 Design Data Dependency information 22 Library item information 31 Library reference design data information 32 Item information

Claims (2)

[Claims] 1. An identifier of design data, an identifier of one or more child design data created based on the design data, and an effect of changing the contents of an item of a component information library adopted when the child design data is created. A design data dependency relationship information storage unit for storing, for each design data, library item information including an identifier of child design data for each item, an identifier of the component information library and an identifier of a reference design data for directly referencing the component information library. And the item information included in each component information library are stored in the library reference design data information storage unit, the change information of the component information library is input, and the change information is supplied in response to the supply of the change information. Library reference design for extracting a corresponding reference design data identifier from the library reference design data information storage means From the design data dependency information storage means, an identifier of update target design data to be updated corresponding to the change information in response to the supply of the data extraction means, the change information and the corresponding reference design data identifier. An update target design data selecting unit for selecting the design data management device. 2. The design data management device according to claim 1, further comprising update target design data display means for displaying an identifier of the supplied update target design data.