JP2012173780A - File configuration management system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a file configuration management system capable of easily managing a parent-child relationship of files, an authorization state, and version.
A file configuration management system comprising a plurality of clients that edit a file and an Author that gives an authorization status to a stored file,
Each client and Author comprises means for visually displaying the file received from the management device in a display format that can identify the current state, and means for storing the edited file in the file storage device,
As the visual display means, the update history of the file is displayed in a tree structure so that the parent-child relationship can be identified, the authorization status is displayed, and arbitrary revisions of a plurality of files are grouped as one group. And the means for updating the meta information, transitioning the file to the authorized state, the waiting for authorization state, and the editing state, and allowing the certifier only to update the status. Features.
[Selection] Figure 9

Description

  The present invention relates to a file configuration management system that assists in joint development of program sources and other files.

  In recent years, in software development, the programs to be created have become huge, and the opportunities for multiple people to jointly develop programs and documents have increased. When creating a huge program, it is necessary to manage a large number of files, so the file configuration and version are often managed using a file configuration management system.

FIG. 14 is a block diagram of a conventional general configuration management system. Each client 1403 stores a file in the file storage device 1401 through the management device 1402 and manages its configuration.
The main processing of the management device 1402 is the check-out and commit shown in FIG. 16. The file storage device 1401 copies (checks out) a file to each client 1403, and the file updated by the client is stored in the file storage device 1401. (Commit).

The basic version management method is based on the premise that management is performed on a time axis as shown in a table 1501 in FIG. 15, and files committed in the past are stored as a history. In addition, by copying and managing an arbitrary file to another folder at the time of product release or the like, it is possible to manage at the time when the arbitrary file is released.
In addition, there exists the following patent document 1 as a prior art document relevant to this invention.

JP 2006-350829 A

By the way, for configuration management during development of source code and documents, using a conventional configuration management system, in order to achieve file management with a parent-child relationship with the version branched from the main body, manually link the parent-child relationship There was only. Therefore, it was unsuitable for managing the version branched from the main body. Further, there is a problem that the past history file display method can be displayed only on the time axis and cannot be displayed visually.
In addition, the conventional method has a problem that it is difficult to implement because it is necessary to perform checkout and file locking so that a shift due to the update timing does not occur.

  Therefore, the present invention automatically builds and manages file parent-child relationships, and further visually displays the file to the user, thereby facilitating the management of the version branched from the main body and checking it. It is an object of the present invention to provide a file configuration management system that can prevent a shift due to update timing without performing an out or lock, and that can be simply implemented.

In order to achieve the above object, a file configuration management system according to the present invention includes a management device including a file storage device, a plurality of clients that store files in the management device, and an authorization state for the stored files. A file configuration management system consisting of an author that gives the status of
The management device stores a file in the file storage device, an update unit that updates meta information of the file, a unit that reads a file from the file storage device, transfers the file to each client and the Author, and each client And means for notifying the author of meta information of the file,
Each of the clients includes a means for visually displaying the file received from the management apparatus in a display format in which the current state of the file can be identified, a means for editing the displayed file, and a file after editing Means for storing the file in the file storage device through the file management device,
The Author visually displays the file received from the management device in a display format that can identify the current state of the file, means for editing the displayed file, and the file through the management device. Means for updating the meta information, and means for storing the file in the file storage device through the management device,
The file storage device includes means for storing the file in a tree structure, and means for changing the state of the rewritten file with meta information,
As the means for visually displaying the client, the update history of the file is displayed in a tree structure so that the parent-child relationship can be identified, the authorization status is displayed, and arbitrary revisions of a plurality of files are grouped into one. As a group and display means,
The Author displays the update history of the file in a tree structure so that the parent-child relationship can be identified as the means for visually displaying, and means for indicating a file in an authorized state, and arbitrary revisions of a plurality of files And a means for updating the meta information, transitioning the file to the authorized state, waiting for authorization state, and editing state, and allowing the certifier only to update the status. It is characterized by.

  According to the file visual configuration management method and system of the present invention, management of past data is simplified, particularly the update history of a version of a file branched from the main body is visually displayed in a concise manner, and the relationship between each file is displayed. It becomes possible to assist in grasping easily. In addition, since exclusive control for preventing a file update shift is unnecessary, it is possible to implement a simpler implementation than in the prior art. Further, the file display method is visual, and there is an effect that the developer can easily specify an arbitrary update history.

1 is a system configuration diagram showing an embodiment of the present invention. It is a block diagram of the data stored in the file storage device. It is a state transition diagram of a file. It is a state transition diagram when a new revision is created. It is a data storage structure diagram of a release set and revision. 5 is a flowchart showing an outline of a file update process and an outline of a file authorization (or stripping) process. It is the flowchart which showed the file update process. 6 is a flowchart showing file authorization (or stripping) processing. It is an example of the file list and file tree display screen in the client. It is an example of the display screen of the release set in a client. It is an example of a file editing screen in the client. It is an example of the release set creation screen in Author. It is an example of the screen which performs authorization / deprivation in Author. It is a schematic block diagram of the whole system in a prior art. It is an example of the screen of the client in a prior art. It is the schematic about a checkout process and a commit process in a prior art.

FIG. 1 is a system configuration diagram showing an embodiment of the present invention.
The file configuration management system of this embodiment includes a management device 2 including a file storage device 1, a plurality of clients 4a, 4b, 4c, and 4n that store files in the file storage device 1 through the management device 2, and file storage. It is composed of an Author 3 that can update / register meta information for a file stored in the device 1, and the clients 4a, 4b, 4c, 4n, and Author 3 are connected to the management device 2 via a network.
This configuration is the same as the configuration of a general client server system, and the portions corresponding to the clients of the general client server system are the clients 4a, 4b, 4c, 4n and Author3, and the portion corresponding to the server manages A device 2 and a file storage device 1.
The difference from a general client-server system is that it has Author3 with functions different from those of other clients, and has a vertical function distribution configuration.

FIG. 2 is a diagram showing file meta information 29 and data body 30 stored in the file storage device 1.
The meta information 29 is index information of the data body, the file PrimaryCode 21 is a code for uniquely recognizing the data, the Revision 23 is a revision number indicating a change of the file, and the Signature 24 is in an approved state. The authorization 25 is data indicating a user who has the right to update the signature 24, and the release set 26 indicates a group number for releasing a plurality of files collectively. The ParentNodePrimaryCode 27 is the PrimaryCode 21 of the file that is the copy source of itself, and the ChildNode1PrimaryCode 28 is composed of the PrimaryCode 21 of the file that has copied itself.
For example, when the client 4a updates FileA whose PrimaryCode 21 is “2314”, the management apparatus 2 creates a copy in which the Meta information 29 of FileA is empty, and holds the file as a temporary file. When saving, the management apparatus 2 automatically adds a new number to the revision 23 and data “waiting for authorization” to the signature 24. Further, the primary code 21 of the update file is added to the ChildNodenPrimaryCode 28 of the file corresponding to the parent.

FIG. 3 is a state transition diagram of a file.
When a file is generated from the initial state 31 with nothing, the file editing state 32 is entered. When file editing is completed and storage processing is performed, the file editing state 32 changes to the authorization waiting state 33. If authorization is given to this authorization waiting state 33, it will be in the authorization state 34, and conversely, if authorization is removed from the authorization state 34, it will shift to the authorization waiting state. The state transition of this file is realized by rewriting Signature24.

FIG. 4 is a state transition diagram showing a process of updating a file and managing the file in a tree shape for each revision.
The transition from the initial state 41 to the initial file creation state 42 is as shown in FIG.
In order to create the next new revision from the initial file creation state, a copy of the target file is created, and a transition is made to the state where the file is in the edit state diagram 32 (43). Further, a parent-child relationship is established with the copy source file as the parent of the tree structure and the copied file as a child of the tree structure. This parent-child relationship is realized by ParentNodePrimaryCode27 and ChildNode1PrimaryCode28. When one or a plurality of files are edited from the editing state 43 of one or a plurality of files and the saving process is performed, the saved files are put into an authorization waiting state (44). When one file is authorized from the authorization waiting state, the authorized child enters a state (46, 47) in which a tree is formed as the authorized state. Similarly, a grandchild file and a great-grandchild file are created and version management is performed in a tree structure.

FIG. 5 is a diagram showing the concept of a file storage structure.
Each file forms a tree structure 54 for each file. In addition, a group (release set) in which arbitrary revisions of a plurality of files are grouped together can be formed 55. In the tree structure, the file changes between three states: a file authorization state 51, a file editing state 52, and a file authorization waiting state 53.

FIG. 6 is a schematic flowchart of a file update process 601 performed through the management apparatus 2 from the clients 4a to 4n and an authorization / removal process 614 performed through the management apparatus 2 from the Author 3 in FIG.
6, the display unit 11 of the client 4n displays the file meta information through the reading unit 6 of the management device 2 (step 602).
Then, the editing unit 12 edits the file. When the file is being edited, the status of the file is indicated. When a new revision of the file is in an authorization waiting state or an authorized state, a notification is received from the management apparatus 2 and displayed on the screen (step 603).
When the save instructing unit 13 issues a save request, the data is written to the file saving device 1 through the writing / updating unit 5 of the management device 2, and further, the fact that the file has been saved and the file status are notified to each of the clients 4a to 4c and the Author Is done.

On the other hand, in the authorization / deprivation processing 614 in FIG. 6, display processing is performed in the same manner as the file update processing 601 (step 609).
Here, before the authorization / deprivation process, if you want to further edit the file that is waiting for authorization, or if you want to merge two or more files, edit the file and save it as a new revision file (step 610, 611).
When authorization / removal is performed on the file, the meta information is updated to the file storage device 1 through the writing / updating unit 5 of the management device 2 to authorize or remove the regular version (step 612).
The notification process 613 is performed in the same manner as the notification process 606 in the file update process.

FIG. 7 is a detailed flowchart for performing a file update process performed from the client 4n in FIG. 6 through the management apparatus 2.
First, a file display method is selected, and a file tree display or a release set display is selected (steps 701, 702, and 703). A display example of the file list and file tree is shown in FIG. 9, and a display example of the release set is shown in FIG. The file list, file tree display, and release set display can be switched (step 704).
Next, if the file is newly created, a new file is created. If the file is updated, the update source file is copied and saved as a file editing state. When a file is opened for editing, the file status is also displayed (FIG. 11) (steps 705, 706, and 707).
When the editing is completed and a save request is issued, the file is saved in the file saving device 1 according to the configuration of the file tree in an authorization waiting state. At this time, the client 4a to 4n and the Author 3 are notified that the data has been saved, and are immediately reflected on the status screen as shown in FIG. 11 (steps 711, 712, and 713).

FIG. 8 is a detailed flowchart of file authorization / removal processing performed from the client 4n in FIG. 6 through the management apparatus 2.
First, a file display method is selected, and a file list and tree display (FIG. 13) or a release set is displayed (steps 801, 802, 803, and 804).
If the file needs to be edited or merged, the file is created as a new revision and edited or merged (steps 805, 811 and 812).
If a file attribute update request is issued, the file is saved in an authorization waiting state or an authorization state, and then the release set is registered (steps 806, 807, 808, and 809).
Next, when the attribute information is updated, the clients 4a to 4n and the Author 3 are notified of this (step 810).

FIG. 9 shows an example of a file list and file tree display screen in the client 4n.
A block 91 showing the folder and file structure and a file tree 92 showing the selected history are shown. Further, a file status screen is displayed from the file context menu 93. In FIG. 9, a file whose name is displayed in a black frame indicates that the file is in an approved state, and a file whose name is displayed in a white frame indicates that the file is in a waiting state. ing.

FIG. 10 is a diagram showing an example of a release set display screen and a process of switching from the context menu 93 in FIG. 9 to the release set screen.
When ReleaseSet55 is selected from the file context menu 93, a release set screen 1002 is displayed. The release set screen 1002 displays file names (File A to D) and revision numbers (006 to 018) constituting the release set (1002).

FIG. 11 shows an example of a status display screen 1101 during file editing.
Here, the file tree and the status of each revision are displayed, and the latest status is always displayed. The right side 1102 of the screen 1101 displays the editing state of the file File [] being edited.

FIG. 12 is a diagram showing an example of a function for registering a release set, which is an example of a screen for adding a new revision to a release set, and a screen 1201 when a file of an arbitrary revision is added to the release set. Only Author3 is allowed to add files of any revision to the release set.
When a new revision is added to the release set, the number of the release set to be added is input to the screen 1201, and the add button is operated to add it.
In addition, when adding a file of an arbitrary revision to the release set, the file name to be added is input to the screen 1202, and the add button is operated to add it.

FIG. 13 is a diagram showing an example of a screen 1300 for rewriting file meta-information in Author3, in which file authorization / removal, author setting, and release set registration are performed.
For example, when one of the files, for example, FileA is selected on the screen 1201, the branch or state of FileA is displayed on the screen 1203, and the meta information of File [003] in the file 1203 is rewritten, the current meta on the screen 1202 is displayed. The information is displayed, so rewrite it. Meta information can be rewritten only from Author3.

DESCRIPTION OF SYMBOLS 1 ... File storage apparatus, 2 ... Management apparatus, 3 ... Client terminal with authority of update of meta information, 4a, 4b, 4n ... Client terminal.

Claims (1)

A file configuration management system comprising a management device having a file storage device, a plurality of clients that store files in the management device, and an Author that gives an authorized status to the stored file,
The management device stores a file in the file storage device, an update unit that updates meta information of the file, a unit that reads a file from the file storage device, transfers the file to each client and the Author, and each client And means for notifying the author of meta information of the file,
Each of the clients includes a means for visually displaying the file received from the management apparatus in a display format in which the current state of the file can be identified, a means for editing the displayed file, and a file after editing Means for storing the file in the file storage device through the file management device,
The Author visually displays the file received from the management device in a display format that can identify the current state of the file, means for editing the displayed file, and the file through the management device. Means for updating the meta information, and means for storing the file in the file storage device through the management device,
The file storage device includes means for storing the file in a tree structure, and means for changing the state of the rewritten file with meta information,
As the means for visually displaying the client, the update history of the file is displayed in a tree structure so that the parent-child relationship can be identified, the authorization status is displayed, and arbitrary revisions of a plurality of files are grouped into one. As a group and display means,
The Author displays the update history of the file in a tree structure so that the parent-child relationship can be identified as the means for visually displaying, and means for indicating a file in an authorized state, and arbitrary revisions of a plurality of files And a means for updating the meta information, transitioning the file to the authorized state, waiting for authorization state, and editing state, and allowing the certifier only to update the status. File configuration management system.

Images