JPH04320549A - File access managing device - Google Patents

Abstract

PURPOSE:To attain flexible file accessing by controlling whether a common file is to be locked or not in accordance with an operator's request in the case of copying a file from the common file to a working area or overwriting a file in the working area to the common file at the time of correcting the common file. CONSTITUTION:A file storing device 101 stores the body of a common file. An access information managing device 102 manages the access information of the common file. A lock control device 104 locks or unlocks an individual common file. A copying control device 103 executes operation for copying the common file to a working area or operation for overwriting a file in the working area to the common file. An overall control device 105 receives an access instruction from an operator through an input line, controls whether a file is to be locked or not in accordance with an operator's request at the time of copying the file so as to consistently execute both of exclusive file access and parallel file access.

Description

[Detailed description of the invention]

0001

[Field of Industrial Application] The present invention relates to a file access management device that is effective in software development and has an exclusive file access control function and a parallel file access control function for modifying shared files. .

0002

[Background Art] When a single piece of software is developed by a development group consisting of multiple workers, the files that are the products of the software development are shared by the group. Allows multiple workers to perform correction work.

[0003] In this way, when multiple workers modify one or a group of shared files,
It is also possible to have multiple workers directly modify the shared file in question, but in this method, if you save the edited content to the shared file while it is being modified, the incomplete content that is being modified will be immediately removed. The problem arises that other workers can see the

[0004] Therefore, in order to prevent such inconvenience, modification work is not performed directly on the shared file, but rather
A common method is to copy a shared file to a work area for each worker, perform modification work on the copied file, and then overwrite the original shared file with the copy after modification.

[0005] However, even with this method, if another worker makes corrections and overwrites the shared file after copying it to the work area, the shared file will be overwritten by the file that he or she has modified. This causes a problem in that the modifications made by the previous worker become invalid.

[0006] In order to avoid this problem, one of the following two methods has conventionally been adopted.

[0007] The first method is to lock the shared file between copying it to the work area and overwriting the shared file, so that modification work can be done exclusively. That is what it is.

[0008] The second method allows copying to the work area to be performed freely without using locks, but when overwriting the original shared file, after copying to the work area, the shared file is The system checks whether it has been overwritten by another worker, and if it has been overwritten, the system merges the changes made by the other worker with your own changes, and then overwrites the shared file. That is what it is.

[0009]

[Problems to be Solved by the Invention] Conventionally, access management of shared files accompanying software development by a plurality of workers has been carried out as described above, but this still has the following drawbacks.

[0010] In the first method, since the modification work on the shared file is performed exclusively, the modification work on the shared file that is being modified by another worker must be done after waiting for the modification work to be completed. This becomes a major hindrance to progressing development work in parallel, and is inappropriate for file access control in software development.

[0011] In the second method, while a shared file is being copied to the work area and modified, other workers often perform similar work on the same file. When overwriting, it is often necessary to merge the changes made by other workers.
Prompt processing is hindered.

[0012] Furthermore, in the second method, it is impossible to exclusively perform modification work on a specific shared file.

[0013]Furthermore, during the merging process, the shared file may be modified by another worker, and in that case, when overwriting the file after the merging is complete, the merging process with the modified content by that worker is performed again. This is extremely troublesome.

The present invention has been proposed in view of the above points, and its purpose is to provide file access management that allows flexible access depending on the nature of individual files and the status of software development. The goal is to provide equipment.

[0015]

[Means for Solving the Problems] In order to achieve the above object, the present invention provides a file storage device that stores the entity of a shared file, an access information management device that manages access information for the shared file, and a a lock control device that locks and unlocks the system; a copy control device that performs operations to copy shared files to the work area and overwrite files in the work area to shared files; and a copy control device that controls the entire device. Checkout processing that copies shared files to the work area without locking them, Reserve processing that locks shared files and copies them to the work area, and Deposit processing that locks and overwrites files in the work area to shared files. The system is equipped with an overall control device that performs processing.

[0016]

[Operation] In the file access management device of the present invention, the overall control device includes a file storage device that stores the entity of the shared file, an access information management device that manages access information for the shared file, and an access information management device that manages the access information for the shared file. By controlling the lock control device that locks and unlocks the shared file, and the copy control device that performs the operation of copying the shared file to the work area and overwriting the shared file with the file in the work area, The checkout process copies the file to the work area without locking it, the reserve process copies the shared file to the work area while locking it, and the deposit process locks and overwrites the file in the work area to the shared file. Perform according to worker's request.

[0017]

Embodiments Hereinafter, embodiments of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of a file access management device of the present invention.

In FIG. 1, this embodiment includes a file storage device 101, an access information management device 102, a copy control device 103, a lock control device 104, and an overall control device 10.
It consists of 5.

An overview of the functions of each part is as follows.

File storage device 101: This is a device that stores the entities of all shared files shared by the development group.

Access information management device 102: This is a device that manages the following access information for each shared file stored in the file storage device 101. - The worker who is copying the shared file - The time of copying - The contents of the shared file at the time of copying - The worker who has locked the shared file - The time of locking - The last time the shared file was overwritten

002
2] Copy control device 103; searches the file storage device 101 for the entity of the shared file specified by the operator,
This device performs an operation of making a copy of the file in a designated work area (not shown) and an operation of overwriting a shared file stored in the file storage device 101 with the file in the work area.

Lock control device 104: A device that performs locking and unlocking operations for a shared file designated by an operator. Here, the lock succeeds only if the shared file is not locked.

Overall control device 105: This is a device that receives access commands from a worker to a shared file via an input line, and controls other devices to perform processing in accordance with each command. Here, the main processes are checkout processing that copies the shared file to the work area without locking it, reserve processing that locks the shared file and copies it to the work area, and copying the file in the work area to the shared file. Three processes are used: a deposit process that locks and overwrites the file. Note that in the deposit process, if the shared file has already been overwritten by another worker, a merge process is performed. The merge process copies the contents of the shared file at the time of copying to the work area and the contents of the current shared file to the work area, and merges the modified contents with the files currently in the work area while referring to them. This is the process to be performed.

Each process of the above embodiment will be explained below.

(1) Checkout process This process is shown in FIG.
This is done as shown in the flowchart.

First, the worker specifies the shared file to be checked out and the work area to be checked out,
A checkout command is given to the overall control device 105 (step 201).

The overall control device 105 inquires of the access information management device 102 about the copy status of the target shared file (step 202).

Then, it is checked whether the target shared file has already been copied to the worker's work area (step 203), and if it has been copied (YE of step 203).
In step S), the process is ended without copying.

On the other hand, if the copy has not been completed (step 2
03 NO), the overall control device 105 is the copy control device 1
03 to copy the target shared file to the work area (step 204).

Next, after the copy is completed, the access information management device 1 records the copy status of the target shared file.
02 for management (step 205).

(2) Reserve processing This processing is performed as shown in the flowchart of FIG.

First, the operator specifies the shared file to be reserved and the work area to be reserved, and gives a reserve command to the overall control device 105 (step 301).

The overall control device 105 inquires of the access information management device 102 about the copy status of the target shared file (step 302).

Then, it is checked whether the target shared file has already been copied to the worker's work area (step 303), and if it has been copied (YE of step 303).
In step S), the process is ended without copying.

On the other hand, if the copy has not been completed (step 3
03), the overall control device 105 inquires of the access information management device 102 about the lock state of the target file (step 304).

[0037] Then, it is checked whether the operator or another person has already locked the lock (step 305), and if it has already been locked (YES in step 305), the process ends without making a reservation.

On the other hand, if it is not locked (NO in step 305), the lock control device 104 is called to lock the target shared file (step 306).

Next, the copy control device 103 is called and the target shared file is copied to the work area (
Step 307).

After the copying is completed, the copy status of the target file is registered and managed by the access information management device 102 (step 308).

(3) Deposit Processing This processing is performed as shown in the flowchart of FIG.

First, the operator specifies the shared file to be deposited and issues a deposit command to the overall control device 10.
5 (step 401).

The overall control device 105 inquires of the access information management device 102 about the copy status of the target shared file (step 402).

Then, it is checked whether the target shared file has been copied to the worker's work area (step 4).
03), if the copy has not been completed (NO in step 403)
), the process ends without making a deposit. The fact that it has not been copied means that no modification work has been done.

On the other hand, if the copy has been completed (step 403
YES), the overall control device 105 inquires of the access information management device 102 about the lock state of the target shared file (step 404).

[0046] Then, it is checked whether or not another worker has locked it (step 405), and if it has been locked by another worker (YES in step 405), the process is terminated without making a deposit. .

Furthermore, if the lock has not been locked by another worker (NO in step 405), it is checked whether the requesting worker has locked it (step 406), and if it has not been locked (step 406) If NO), the lock control device 104 is called to lock the device (step 4).
07), if locked (YES in step 406)
Then proceed to the next process.

Next, the overall control device 105 inquires of the access information management device 102 about the time when the target shared file was last overwritten (step 40).
8).

Then, from the obtained time, it is determined whether the shared file has been overwritten after being copied to the worker's work area (step 409), and if it has been overwritten (YES in step 409), the shared file is calls a merge process to merge the data (step 410), and if the data has not been overwritten (NO in step 409), the process directly proceeds to the next process.

Next, the copy control device 103 is called to overwrite the target shared file with the file in the work area (step 411).

Then, the lock control device 104 is called to unlock the target shared file (step 412), and the access information management device 102 is called to make it uncopied (step 413).

[0052] Of the above-mentioned processes, if everyone uses only the checkout process and deposit process, it is possible to proceed with the work in parallel, and overwriting the shared file is exclusive during the merge process. Therefore, even if a merge operation is required during deposit processing, it can be done only once at most.

On the other hand, if you perform reserve processing, you can prohibit other workers from making deposits until you complete the deposit processing, so if everyone uses only reserve processing and deposit processing, it will be completely It is possible to proceed with the work exclusively, and there is no need for merging work during the deposit process.

[0054] Therefore, among shared files, everyone uses reserve processing and deposit processing for shared files that should be managed exclusively, and everyone uses checkout processing and deposit processing for other shared files. Development work can be done more efficiently by using the following.

[0055] Also, if we consider a situation in which checkout processing, reserve processing, and deposit processing are freely mixed and used for one shared file, if you perform reserve processing, other users will not be able to perform the deposit processing until you perform the deposit processing. It is possible to prohibit the deposit processing of the following workers, and there is no longer a need for merging at the time of deposit processing.

On the other hand, other workers cannot perform reserve processing but are able to perform checkout processing, so they can proceed with modification work on the file in parallel.

[0057]

[Effects of the Invention] As explained above, in the file access management device of the present invention, when modifying a shared file, it is possible to achieve both exclusive file access and parallel file access without contradiction. becomes possible,
The effect is that software development by a group can proceed more efficiently and safely by using them properly according to individual files and the software development situation.

[Brief explanation of drawings]

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

FIG. 2 is a flowchart showing details of checkout processing.

FIG. 3 is a flowchart showing details of reserve processing.

FIG. 4 is a flowchart showing details of deposit processing.

[Explanation of symbols]

101...File storage device 102...Access information management device 103...Copy control device 104...Lock control device 105...Overall control device

Claims (1)

[Claims] Claim 1: A file storage device that stores the entity of a shared file; an access information management device that manages access information for the shared file; a lock control device that locks and unlocks each shared file; A copy control device that copies files to the work area and overwrites files in the work area to shared files, and a checkout that controls the entire device and copies shared files to the work area without locking them. The system is characterized by comprising an overall control device that performs processing, a reserve process that locks a shared file and copies it to a work area, and a deposit process that locks and overwrites a file in the work area to the shared file. File access management device.