JPH03113674A - Design data control system - Google Patents

Abstract

PURPOSE:To prevent an error that plural users simultanesouly executes update work against the same data by controlling a flag meaning 'in the middle of updating work' as information on design data and the name of a worker and using them as the exclusive locks. CONSTITUTION:A control data base 5 recording the shared design data, a data state decision processing block 2 deciding whether the other user is in the middle of updating or not at the time of executing updating work, a check out processing block 3 which exclusively locks data to be updated and which copies the shared data in a work place and a check in a processing block 4 which rewrites the work data into the shared data and which unlocks the exclusive lock when updating or new generation is terminated are provided. Then, a processing result can be confirmed in an input/output screen device 1. Thus, the error that plural users simultaneously execute updating work on the shared design data and the other user uses incomplete data.

Description

DETAILED DESCRIPTION OF THE INVENTION [Field of Industrial Application] The present invention relates to a design data management system, and particularly to a design data management system for a plurality of users to carry out designs.

[Conventional technology]

Conventionally, in this type of design environment where multiple users share a database and design, the burden of the design data management system for design data and its update work is on the user, and it is difficult to know who owns individual data. Information such as whether an update is in progress or whether it has been completed or not has been communicated in writing or by word of mouth.

[Problem to be solved by the invention]

The conventional manual design data management system described above is
Since the management method is left up to the individual user, there is a possibility that multiple users may update shared design data at the same time, or there may be errors in the process of updating without being informed that an update is in progress. This method has the disadvantage that errors may occur if the completed data is used by another user.

An object of the present invention is to provide a design data management system that can prevent such simultaneous updating of design data and erroneous use of incomplete data.

[Means to solve the problem]

The design data management system of the present invention includes a management database in which shared data is registered, a data status determination processing block that determines whether another user is in the process of updating data, and an update process block. A checkout processing block that places an exclusive lock on the data that you want to perform and copies the shared data to a temporary work area, and a checkout processing block that copies the shared data to a temporary work area, and the work data that has been updated or newly created to the storage location of the shared data. It has a check-in processing block that performs write-back and releases exclusive locks, and is characterized by preventing other users from referencing or simultaneously updating unfinished data.

〔Example〕

Next, embodiments of the present invention will be described with reference to the drawings.

FIG. 1 is a block diagram of a design data management system for explaining a first embodiment of the present invention.

As shown in FIG. 1, this embodiment distinguishes between a management database 5 that records shared design data, this shared design data, and temporary design data for work, and when updating a data status determination processing block 2 that determines whether the user is updating or not; a checkout processing block 3 that places an exclusive lock on the data that the user wants to update and copies the shared data to a work location; The check-in processing block 4 includes a check-in processing block 4 that writes back the work data to the shared data when new creation is completed and releases the exclusive lock set by the above-mentioned check-out processing block 3, and the check-out processing block 3 and the check-in processing block 4 can be checked on the input/output screen device 1.

In such a design data management system, an input/output screen device 1 is provided so that a user can interactively update or create new design data or interact with the design data management system. In addition, data status determination processing block 2 checks the status of the corresponding data in the management database when the user requests to update data or requests to write back a series of updated or newly created data to the shared area. This is a processing function that extracts from 5 and determines whether or not a request should be executed.

On the other hand, the checkout processing block 3 inputs the information that the corresponding data is to be updated into the management database 5 as a data state, stores it on the shared area, and copies the corresponding data to the user's work area. It is a processing function. In addition, the check-in processing block 4 copies (overwrites) a series of data that has been updated or newly created in the user's work area to the shared area, and marks the completion of the work on the data as the data state. This is a processing function for inputting data into the management database 5. The management database 5 described above stores management items to be controlled by the design data management system in a table format.

FIG. 2 is a diagram of a design data information management table stored in the management database shown in FIG. 1.

As shown in FIG. 2, this management table 6 is applied to design data for LSI design, and one row of this table 6 stores information regarding one piece of LSI design data. If it is for update work, that is, if it has been checked out, a flag is set in the checkout column 10, and the name of the user who checked out is written in the operator column 11. First, when a user requests update work for one cell, the data status determination processing block 2 searches for the corresponding data in the design data information table 6, and checks whether the data has been checked out by another user. It is determined whether or not. In this example, since flags have already been set in all design data checkout fields 10 for cell 2, updating cannot be performed, but for cell 1, it is possible.

Further, if the data state determination processing block 2 determines that work is possible, the checkout processing block 3 is entered. Here, first, if the corresponding data goes to cell 1 in the design data information table 6, a flag is set in the checkout column 10 (part 13 in FIG. 2), and the user's name is written in the worker column 11. Next, the storage location of the design data in the shared area is extracted from the shared data storage location column 9, and the data is copied from the shared area to the user's work area. Furthermore, the data storage location in the work area is written in the work data storage location column 12. This field is never referenced except during check-in processing.

After the above checkout process is completed, the user can update the design data on the work area. At this time, the incomplete data being updated remains in the work area, and the complete data before the update remains in the shared area.

When the user completes the update work or the new creation work and requests writing back to the shared area (check-in), the data state determination processing block 2 searches the design data information table 6.

As a result, it is determined whether the corresponding data is new or data that has been previously checked out by the same user. If the previous check-out process was performed by another user, or if the check-out process itself has not been performed, the next check-in process will not be performed. If it is determined that such check-in processing is possible, the process proceeds to check-in processing block 4. Here, the shared data storage location I! is selected from the storage locations indicated in the work data storage location column 12 of the design data information table 6. The data is copied to the storage location indicated by 19, and the columns checkout flag column 101, worker column 11, and work data storage location column 12 of table 6 are cleared. As a result, the design data is written back from the work area to the shared area and released to other users. On the other hand, when checking in new work data, add a new row to table 6, write in cell column 7 and design data column 8, and copy the data specified by the user to the shared area.
Write the storage location in the shared data storage location column 9.

In short, according to this embodiment, by inputting update work information that has been transmitted on paper or orally into the system, data can be protected from update work that occurs at the same time. By clearly separating data from setting data, it is possible to prevent other users from mistakenly using incomplete data that is currently being updated.

FIG. 3 is a design data management table diagram in a design data management system for explaining a second embodiment of the present invention.

As shown in FIG. 3, this embodiment can be applied as a design data management system in software design by replacing the management of LSI design data in the first embodiment described above with software design and reconfiguring the management database 5. This is an example. That is, by replacing the cell name field 7 and design data field 8 in the first embodiment with the module name field 14 and file field 15, respectively, a design data information table for software design can be formed. This embodiment can be used for software design projects designed by multiple users.

〔Effect of the invention〕

As explained above, the design data management system of the present invention manages the flag indicating that updating is in progress and the name of the worker as design data information in an environment where multiple users collaborate to design. Moreover, by using it as an exclusive lock, it is possible to prevent the mistake of multiple users updating the same data at the same time.

In addition, the present invention applies an exclusive lock and at the same time copies data from the shared area to the user's work area to prevent unfinished data being worked on from being placed in the shared area. This has the effect of preventing the mistake of referencing incomplete data that is in the process of being updated.

[Brief explanation of drawings]

FIG. 1 is a block diagram of a design data management system for explaining the first embodiment of the present invention, FIG. 2 is a diagram of a design data information management table stored in the management database shown in FIG. 1, and FIG. The figure is a diagram of a design data information management table in a design data management system for explaining a second embodiment of the present invention. 1... Input/output screen device, 2... Data status determination processing block, 3... Checkout processing block, 4.
... Check-in processing block, 5... Management database, 6... Design data information management table, 7...
Cell name field, 8... Design data name type, 9... Shared data storage location field, 10... Checkout flag field, 1
1...Each worker column, 12...Work data storage location column, 13...Cell 1 corresponding line, 14...Module name type, 5...File type column.

Claims (1)

[Claims] A management database in which shared data is registered, a data status determination processing block that determines whether another user is updating data when updating data, and an exclusive lock on the data that you want to update. A check-out processing block that copies the shared data to a temporary work area, and a check-in that writes back the work data that has been updated or newly created to the storage location of the shared data and removes the exclusive lock. A design data management system comprising a processing block and preventing other users from referencing or simultaneously updating unfinished data.