JP2002251418A - Eda library management method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide an EDA library management method by which information about the update or the registration of EDA libraries can be obtained easily and the EDA libraries can be managed effectively. SOLUTION: In this method, when an existing EDA library is updated, a management section for managing the database of EDA libraries extracts the names of all of the users of the updated EDA library from a file in which historical information about the obtainment of the EDA libraries is written (S511), extracts the mail addresses of all of the users of the updated EDA library from a file in which information about the users of the EDA libraries is written (S516), and send an e-mail message indicating that the EDA library has been updated to each of the extracted mail addresses (S521). By this method, information about the update of an EDA library can be obtained easily.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION The present invention relates to a method for managing an EDA library.
The present invention relates to a method for managing an EDA library in a design environment.

[0002]

2. Description of the Related Art In recent years, databases and WWW (World)
A method of managing an EDA library by combining d Wide Web) is being put to practical use. Such an E
In the DA library management method, EDA library and E
By using WWW as an interface between the user and the EDA library database that holds the information attached to the DA library, the EDA library user has obtained the EDA library without directly accessing the EDA library database.

However, the conventional EDA as described above
In the library management method, the EDA existing in the EDA library database at the time of executing a process such as a search.
Information about the library is readily available, but ED
A constant search of the EDA library database was required to obtain information on A library updates.

Further, a required EDA library is under development, and a newly registered EDA library is waited until the development is completed.
When acquiring a library, it is necessary to always search the EDA library database and confirm that the library has been registered, as in the case of updating the EDA library.

[0005]

SUMMARY OF THE INVENTION The EDA library management method of the present invention solves the above-mentioned problems, makes it possible to easily obtain necessary EDA library update and registration information, and enables efficient EDA library management. It is an object of the present invention to provide a simple EDA library management method.

[0006]

In order to achieve the above object, an EDA library management method according to the first aspect of the present invention is a method for managing a file in which acquisition history information of an EDA library is described and information of a user of the EDA library. In the EDA library management method of obtaining information from the described file and managing the EDA library via the WWW server and the mail server, when updating the existing EDA library, the database management unit for managing the EDA library uses the existing EDA library. Receiving an instruction to update the library; information identifying the EDA library;
Obtaining a DA library, searching for an EDA library to be updated from the EDA library database by using the information specifying the EDA library, exchanging the EDA library to be updated with the new version of the EDA library, Storing the new version of the EDA library in a database; extracting all the user names of the EDA library to be updated from a file in which the acquisition history information of the EDA library is written; Notifying that the EDA library has been updated via a WWW server.

According to a second aspect of the present invention, in the EDA library management method according to the first aspect, when notifying that the EDA library has been updated, all of the EDA library information from the file in which the information of the user of the EDA library is described. Extracting a mail address corresponding to the user name of the EDA library, and transmitting a mail notifying the update of the EDA library to each mail address.

According to a third aspect of the present invention, in the EDA library management method, information is obtained from a file in which acquisition history information of the EDA library is described and a file in which information of a user of the EDA library is described, and the information is obtained via a WWW server and a mail server. In an EDA library management method for managing an EDA library, when a user reserves use of an EDA library required for design, a database management unit for managing the EDA library requires an EDA under development required by the user for design. Receiving an instruction to reserve the use of the library; adding information identifying a user who needs the EDA library to a file describing information of the user of the EDA library; EDA library under development required for design Extracting the information to be specified, and storing the information for specifying the user, the information for specifying the EDA library, and the information indicating that the EDA library is in a reserved state in a file that describes the acquisition history information of the EDA library. Steps to be described.

According to a fourth aspect of the present invention, in the EDA library management method according to the third aspect, the ED library in the information for specifying the EDA library is used.
Checking the registration status indicating whether or not the library A has been registered. If the registration status indicates that the library has been registered, cancel the reservation process. If the registration status indicates that the library is under development, continue the reservation process. Have.

According to a fifth aspect of the present invention, in the EDA library management method of the third and fourth aspects, when notifying the registration of the reserved EDA library, the acquisition history information of the EDA library is described. A step of specifying the users of all the EDA libraries whose use has been reserved from the set files, and a step of notifying the user of each EDA library that the EDA library whose use has been reserved has been registered.

According to a sixth aspect of the present invention, there is provided the EDA library management method according to the fifth aspect.
When notifying that the EDA library has been registered,
Extracting a mail address corresponding to the names of all the users who have reserved the use of the EDA library from a file in which information of the users of the EDA library is described; and sending an e-mail notifying the EDA library update to the mail address. Transmitting.

According to the above method, it is possible to easily obtain necessary EDA library update and registration information, and to provide an EDA library management method capable of efficiently managing the EDA library.

[0013]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a data flow diagram of the EDA library management method according to the embodiment of the present invention.

In FIG. 1, 100 is a database management unit, 110 is an EDA library database, 120 is a user information file, 130 is an EDA library acquisition history file, 140 is a WWW server, 150 is a mail server, 160 is a client, and 170 is a client. Network.

The database management unit 100 is a control unit for the entire system, and provides notification of EDA library update and EDA library update.
It registers the DA library, notifies the subscriber when the EDA library is registered, and registers information for the information stored in the EDA library database 110, the user information file 120, and the EDA library acquisition history file 130, respectively. Processing such as update, delete, search, reservation, etc. through the WWW server 14 through the network 170.
0 through the instruction from the client 160. Also, the results of the processing performed by the database management unit 100, such as the search results of the EDA library database, are output to the client 160 via the WWW server 140 or the mail server 150.

The EDA library database 110 includes:
This is a database that stores various information about the EDA library and the EDA library body. The user information file 120 is a file for storing information on users of the system.

EDA library acquisition history file 130
Is a file storing information for specifying the EDA library acquired by the user and information of the acquired user, and indicating the correspondence between the acquired EDA library and the acquirer.

The WWW server 140 transmits / receives data to / from the client 160 via the WWW via the network 170, and mediates between the database management unit 100 and the client 160.

The mail server 150 sends the information received from the database management unit 100 to the client 160 through the network 170 as electronic mail. The client 160 sends the WWW through the network 170
A terminal that obtains information about the EDA library obtained via the server 140 and instructs the database management unit 100 to perform processing related to the EDA library via the WWW server 140 via the network 170. Workstation or PDA (Personal
digital assistants) and the like.

Although only one client 160 is shown in FIG. 1, a plurality of clients may exist. The network 170 connects the WWW server 140 and the mail server 150 to the client 160, and indicates a network such as the so-called Internet or intranet.

FIG. 2 is a configuration diagram of the user information file. In FIG. 2, 200 is a user ID, 210 is a user name, 220 is a user's department name, 230 is a user's mail address, 240 is a user's contact telephone number, 250
Is an LSI product name using the EDA library.

As shown in FIG. 2, the user information file in the present embodiment describes each piece of information in association with each user. In the present embodiment, the user ID uses a four-digit numerical value in ascending order, such as 0001, 0002, and 0003, but may not be a four-digit numerical value as long as each piece of user information can be distinguished.

FIG. 3 is a configuration diagram of the EDA library acquisition history file. In FIG. 3, reference numeral 300 denotes an EDA library acquisition date; 310, an acquired EDA library semiconductor process name; 320, an acquired EDA library power supply voltage; 330, an EDA tool name using the acquired EDA library; The cell name of the EDA library, 350 is the version of the acquired EDA library, 360 is the acquirer name of the user who acquired the EDA library, and 370 is a flag indicating the type of history. EDA
Library semiconductor process name 310, EDA library power supply voltage 320, EDA tool name 330 using EDA library, EDA library cell name 340, ED
The A library version 350 is the EDA shown in FIG.
It is acquired from the library database 110 and recorded.

As shown in FIG. 3, in this embodiment, EDA
An acquisition history is described for each acquisition or reservation of one library. In the present embodiment, the EDA library acquisition history file is configured using the user name as the user information of the EDA library. However, the EDA library acquisition history file is not limited to the user name as long as the user can be specified. In the present embodiment,
As the flag 370 indicating the type of history, a character string of “acquisition” is used for the history at the time of acquisition of the EDA library, and “reservation” is used for the history of reservation of the EDA library. It is not limited to “acquisition” or “history”.

FIG. 4 is a configuration diagram of the EDA library database. In FIG. 4, reference numeral 400 denotes a cell name of the EDA library, and 410 denotes an ED using the EDA library.
A tool name, 420 is EDA library version,
430 is the semiconductor process name of the EDA library, 440
Is the power supply voltage of the EDA library, 450 is the registration status of the EDA library, and 460 is the storage location of the EDA library body.

Hereinafter, as Embodiment 1 of the present invention, E
An EDA library update notification method in the DA library management method will be described with reference to the drawings. 5 and 8
9 is a flowchart of a program for notifying an EDA library update. FIG. 5 is a flowchart of the update notification process, and FIG. 8 is a flowchart of the EDA library update process.

In FIG. 8, upon receiving an EDA library update instruction 801 from the client, the database management unit firstly obtains a semiconductor process name, a power supply voltage, and an EDA.
ED for which tool name, cell name, version, etc. are to be updated
The information specifying the A library and the new version of the EDA library main body 803 are acquired (S802). Next, it is checked whether there is any information in the EDA library to be updated and the new EDA library main body 803 (S80).
4) If there is any deficiency, information specifying the EDA library to be updated again and the new edition of the EDA library body 803
To get. Next, data of the EDA library to be updated in the EDA library database is searched based on the information identifying the EDA library to be updated acquired in S802 (S805), and the data of the EDA library to be updated exists. If not, the process ends. If there is EDA library data to be updated (S806), the storage location of the EDA library body (FIG. 4)
460) is extracted (S807), and the EDA library main body 813 to be updated stored in the storage location extracted in S807 is extracted (S808). Next, the EDA library main body 813 to be updated and the EDA library main body 803 of the new version are replaced, and the new version of the ED
The A library main body 803 is stored in the storage location (460 in FIG. 4) of the EDA library main body (S809). next,
EDA for which the EDA library database is to be updated
The version (420 in FIG. 4) of the EDA library to be updated is extracted from the library data (S81).
0). Next, a version obtained by adding one to the version extracted in the process 810 is stored as a new version (S8).
11). Finally, an EDA library update notification process is performed (S812), and the EDA library update process ends.

Next, the EDA library update notification processing in S812 will be described with reference to the flowchart shown in FIG.
In FIG. 5, first, the semiconductor process name (S501) and the power supply voltage (S50) are obtained from the information specifying the EDA library to be updated acquired in the process 802 in FIG.
2) Extract the EDA tool name (S503) and cell name (S504). Next, the EDA library acquisition history file is read (S505), and the following processing is performed for all acquisition histories.

First, the flag indicating the type of history is "acquired".
(S506), and if "acquisition", it is checked whether the semiconductor process name described in the acquisition history of interest at present matches the semiconductor process name extracted in S501 (S507). If the semiconductor process names match, it is checked whether the power supply voltage described in the acquisition history of interest at present matches the power supply voltage extracted in S502 (S508), and if the power supply voltages match. It is checked whether the EDA tool name described in the currently focused acquisition history matches the EDA tool name extracted in S503 (S509). If the EDA tool names match, the acquisition currently focused on is checked. The cell name described in the history is S5
It is checked whether the cell name matches the cell name extracted in step S04 (S51).
0) If the cell names match, the user name described in the acquisition history of interest at present is stored in the user name array for storing the user name (S511). Next, it is checked whether there is an acquisition history to be read from the EDA library acquisition history file. If there is an acquisition history to be read, the process returns to S505 (S512). Also, if the result of each survey does not match the content described in the acquisition history of interest in S506 to S510, the process also proceeds to S512. After reading all the histories, the user information file is read for each user data (S513), and the following processing is performed for all the user data.

First, the user name is extracted from the user name array (S514). Next, a user name is extracted from the data of the currently focused user information file, and it is checked whether the user name matches the user name extracted in S514 (S515).
If the user names do not match, the process proceeds to S517 described below. If the user names match, the mail address is extracted from the data of the user information file of interest at present, the mail address is stored in the mail address array for storing the mail address, and the process proceeds to S518 described later (S516). If the user names do not match in S515, it is checked whether the user name to be extracted still exists in the user name array, and if there is a user name to be extracted, the process returns to S514 (S517). S51
After saving the e-mail address in the e-mail address array in 6 and if there is no user name to be taken out from the user name array in S517, it is checked whether there is user data to be read from the user information file, S if there is user data to be read from the user information file
The process returns to 513 (S518). After reading the data of all users, a message indicating that the EDA library has been updated is created (S519), and one mail address is extracted from the mail address array (S520). Next, the message created in S519 is transmitted by e-mail to the e-mail address extracted in S520 (S521).
Next, it is checked whether there is an e-mail address to be taken out from the e-mail address array. And if there is no mail address to be taken out, the process is terminated.

Here, the update processing of the EDA library is defined as replacing the EDA library main body stored in the storage location 460 of the EDA library main body. It may be defined as changing.

As described above, Embodiment 1 of the present invention
According to this, an EDA library management method of automatically notifying a user of the EDA library of an update at the time of updating the EDA library can be realized, and update information of the EDA library in use can be easily obtained.

Next, as a second embodiment of the present invention, the ED
A method for reserving an EDA library in the A library management method will be described with reference to the drawings. FIG.
It is a flowchart of the reservation process of A library.

In FIG. 6, upon receiving a reservation instruction 601 for reserving the use of an EDA library under development as soon as it is registered, the database management unit first receives a semiconductor process name, a power supply voltage, an EDA tool name, Information specifying the EDA library to be reserved, such as the cell name and the version of the EDA library to be updated, is acquired (S602). Next, it is checked whether there is any deficiency in the information for specifying the EDA library to be reserved (S603). If there is any deficiency, information for specifying the EDA library to be reserved again is obtained. Next, data of the EDA library to be reserved in the EDA library database is searched based on the information specifying the EDA library acquired in S602 (S60).
4) It is checked whether the EDA library to be reserved does not yet exist and can be reserved (S605). If reservation is not possible, the process is terminated. ED to make a reservation as a result of investigation in S605
If the A library can be reserved, user information is obtained from the client (S606). Next, it is checked whether the user information acquired in S606 is complete (S60).
7) If there is any deficiency, return to S606. If there is no defect,
The user information file is opened (S608), and S60
It is checked whether the user information acquired in step 6 already exists in the user information file (S609). If it does not exist, it is added (S610), and the user information file is closed (S611). Next, a user name is extracted from the user information acquired in S606 (S612). Next, the EDA library acquisition history file is opened (S613), and S
Information (S) for specifying the EDA library acquired in 602
614) and a character string "reservation" (S615) as a flag indicating the history type and the user name extracted in S612 (S616). Next, the EDA library acquisition history file is closed, and the process ends (S617).

As described above, Embodiment 2 of the present invention
According to the described EDA library management method, when a required EDA library is under development, the use of the EDA library under development can be reserved as soon as the development is completed.

Next, as a third embodiment of the present invention, the ED
An EDA library reservation notification method in the A library management method will be described with reference to the drawings. 7 and 9
FIG. 9 is a flowchart of a program for notifying a reservation of an EDA library. FIG. 7 is a flowchart of the reservation notification process, and FIG. 9 is a flowchart of the EDA library registration process.

In FIG. 9, upon receiving an EDA library registration instruction 901 from a client, the database management unit firstly obtains a semiconductor process name, a power supply voltage, and an EDA.
The information which specifies the EDA library to register, such as a tool name and a cell name, and the EDA library main body 903 are acquired (S
902). Next, it is checked whether the information for specifying the EDA library to be registered and the EDA library main body 903 are not defective (S904).
Library identification information and EDA library body 90
Acquire 3. If there is no defect, the EDA library database is searched based on the information specifying the EDA library received in S902 (S905), and the EDA to be registered is registered.
It is checked whether the library already exists in the EDA library database (S906), and if it exists, the process is terminated. If the EDA library does not exist in S906, an area for storing the EDA library information and the EDA library main body 903 is secured in the EDA library database (S908). Next, the information identifying the EDA library received in S902 is stored in S908.
(S909). Next, S90
The EDA library main body 903 acquired in 2 is stored in the area for storing the EDA library main body 903 secured in S908 (S910). Next, 1.0 is set as the initial value of the version of the EDA library, and stored in the area secured in S908 (S911). Next, EDA library reservation notification processing is performed (S912), and the EDA library registration processing ends.

Next, the EDA library reservation notification processing in S913 will be described with reference to the flowchart of the EDA library reservation processing shown in FIG. 7, first, a semiconductor process name (S701), a power supply voltage (S702), an EDA tool name (S703), and a cell name are extracted from the information specifying the EDA library acquired in S902 in FIG. 9 (S704). Next, the EDA library acquisition history file is read (S705), and the following processing is performed for all histories.

First, the flag indicating the type of history is "reserved".
(S706), and if "reserved", it is checked whether the semiconductor process name described in the currently focused history matches the semiconductor process name extracted in S701 (S707). If the process names match, it is checked whether or not the power supply voltage described in the currently focused history matches the power supply voltage extracted in S702 (S708). The EDA tool name described in the history of interest is S703
It is checked whether it matches the EDA tool name extracted in step (S70).
9) If the EDA tool names match, it is checked whether the cell name described in the currently focused history matches the cell name extracted in S704 (S710), and the cell names match. If so, the user name described in the history of interest at present is stored in the user name array for storing the user names (S711). Next, it is checked whether there is a history to be read from the EDA library acquisition history file. If there is a history to be read, the process returns to S705 (S712). Also S7
Even when the results of the investigation do not match the contents described in the history of interest from 06 to S710, the process proceeds to S712 to investigate whether there is a history to be read from the EDA library acquisition history file.

Next, the user information file is read (S
713) The following processing is performed for all pieces of user information. First, the user name is extracted from the user name array (S7).
14). Next, a user name is extracted from the currently focused user information file, and it is checked whether the user name matches the user name extracted in S714 (S715). If the user name does not match, the process proceeds to S717 described later. move on. If the user names match, the e-mail address is extracted from the currently focused user information file, stored in the e-mail address array for storing the e-mail address, and the process proceeds to S718 described later (S7).
16). If the user names do not match in S715,
It is checked whether or not the user name to be extracted exists in the user name array (S717).
Return to 714. After saving the mail address in the mail address array in S716, and when there is no user name to be extracted from the user name array in S717, it is checked whether there is user information to be read from the user information file (S718). If the user information to be read from the user information file exists, the process returns to S713. If there is no user information to be read from the user information file,
A message indicating that the EDA library has been registered is created (S719), and one mail address is extracted from the mail address array (S720). Next, the message created in S719 is transmitted by e-mail to the e-mail address extracted in S720 (S721). Next, it is checked whether there is a mail address to be taken out from the mail address array (S722). If there is a mail address to be taken out, the process returns to S720, and if there is no mail address to be taken out, the process is ended.

As described above, the ED according to the third embodiment of the present invention
According to the A-library management method, a reservation notification for notifying a user who has made a reservation of the EDA library at the time of registration of the EDA library can be made, so that the EDA library can be registered easily and efficiently.

The EDA according to the embodiment of the present invention
In the library management method, a message indicating that the EDA library has been updated is transmitted by e-mail as an EDA library update notification, but the updated EDA library body may be transmitted. Also, ED
Although the message indicating that the A library has been registered has been transmitted by e-mail, it goes without saying that the registered EDA library body may be transmitted.

The EDA according to the embodiment of the present invention
In the library management method, the reservation of the EDA library is made E
The DA library acquisition history file was provided with a flag for the history type. However, an EDA library reservation file was provided separately from the EDA library acquisition history file, and information on the reservation was described in this EDA library reservation file. In the EDA library reservation notifying process, the EDA library reservation file may be used.

The EDA according to the embodiment of the present invention
In the library management method, the user name is used as information on the user in the EDA library acquisition history file, but other information may be used as long as the information can identify the user. In particular, if the user's mail address is used as the information for identifying the user, the user's mail address can be obtained without going to the user information file in the EDA library update notification processing and reservation notification processing. It is possible to send mail easily.

[0045]

As described above, according to the EDA library management method of the present invention, the user of the EDA library can use the EDA library.
Since the necessary update and registration of the EDA library can be known without constantly searching the library database, the update and registration of the EDA library can be performed easily and efficiently. In other words, the use of an EDA library of an incorrect version in the LSI design leads to a reduction in design errors.

[Brief description of the drawings]

FIG. 1 is a data flow diagram of an EDA library management method according to an embodiment of the present invention.

FIG. 2 is a configuration diagram of a user information file.

FIG. 3 is a configuration diagram of an EDA library acquisition history file.

FIG. 4 is a configuration diagram of an EDA library database.

FIG. 5 is a flowchart of an update notification process according to the first embodiment of the present invention.

FIG. 6 is a flowchart of an EDA library reservation process according to the second embodiment of the present invention.

FIG. 7 is a flowchart of EDA library reservation notification processing according to Embodiment 3 of the present invention;

FIG. 8 is a flowchart of an EDA library update process according to the first embodiment of the present invention.

FIG. 9 is a flowchart of an EDA library registration process according to the third embodiment of the present invention.

[Explanation of symbols]

 Reference Signs List 100 database management unit 110 EDA library database 120 user information file 130 EDA library acquisition history file 140 WWW server 150 mail server 160 client 170 network 200 user ID 210 user name 220 department name 230 email address 240 telephone number 250 LSI product name 300 Acquisition date 310 Process name 320 Power supply voltage 330 Tool name 340 Cell name 350 Version 360 Acquirer name 370 Flag 400 Cell name 410 EDA tool name 420 Version 430 Process name 440 Power supply voltage 450 Registration status 460 EDA library main body storage location 601 Reserved Instruction 801 Update instruction 803 New EDA library body 813 EDA library to be updated 901 registration instruction 903 EDA library body

Claims (6)

[Claims] 1. An EDA library management method for acquiring information from a file describing EDA library acquisition history information and a file describing user information of an EDA library, and managing the EDA library via a WWW server and a mail server. In updating the existing EDA library, the database management unit that manages the EDA library receives an instruction to update the existing EDA library, and obtains information specifying the EDA library and a new EDA library. Searching for an EDA library to be updated from the EDA library database based on the information specifying the EDA library; and updating the new version of the EDA library and the ED to be updated.
Replacing the A library and storing the new version of the EDA library in the database; and extracting all the user names of the EDA library to be updated from a file in which the acquisition history information of the EDA library is written; Notifying, via a WWW server, each user of the EDA library that the EDA library has been updated. 2. The EDA library management method according to claim 1, wherein, when notifying that the EDA library has been updated, the EDA library user name is changed from a file in which information of the EDA library user is described to the EDA library user names. An EDA library management method, comprising: extracting a corresponding e-mail address; and transmitting an e-mail notifying the update of the EDA library to each e-mail address. 3. An EDA library management method for acquiring information from a file describing EDA library acquisition history information and a file describing EDA library user information, and managing the EDA library via a WWW server and a mail server. In the above, when the user reserves the use of the EDA library required for the design, the database management unit that manages the EDA library receives an instruction to reserve the use of the EDA library under development required for the design by the user. A step of adding information specifying a user who needs the EDA library to a file describing information of the user of the EDA library; and an EDA under development required by the user for design from the EDA library database. Extracting information identifying a library; EDA library management method and a step described information identifying the information specifying the EDA libraries, and the EDA library describing the acquisition history information of EDA library information indicating the reserved state file's. 4. The EDA library management method according to claim 3, wherein a registration status indicating whether the EDA library is registered in the information for specifying the EDA library is confirmed, and the registration status indicates that the EDA library has been registered. The EDA library management method includes a step of terminating the reservation processing when the registration status is in progress and continuing the reservation processing when the registration status indicates that the registration is under development. 5. The EDA library management method according to claim 3, wherein when notifying the registration of the reserved EDA library, all of the files whose use has been reserved from the file in which the acquisition history information of the EDA library is described. A step of identifying a user of the EDA library, and an ED reserved for use by the user of each of the EDA libraries
Notifying that the A library has been registered. 6. The EDA library management method according to claim 5, wherein when notifying that the EDA library has been registered, use of all the EDA libraries is reserved from a file in which information of the EDA library user is described. An EDA library management method, comprising: a step of extracting a mail address corresponding to a user name; and a step of transmitting a mail for notifying an update of the EDA library to each mail address.