JP6217231B2 - Software configuration management system - Google Patents

Description

  The present invention relates to a technique for managing software.

  There is a software configuration management system for managing the software configuration such as the directory configuration and version number of software assets (source files, documents, etc.) of products (including those under development) in software development (for example, Patent Document 1). See).

  FIG. 1 is a diagram showing an example of processing in a conventional configuration management system.

  In FIG. 1, a client PC (Personal Computer) used by a user acquires the latest software configuration information from the configuration management server via a network (step S11), and arranges it on a workspace (work area).

  When editing a desired file, the user declares (checks out) editing (step S12) and performs editing (step S13).

  After that, when the workspace is updated (step S14), if the other user's change is confirmed for the checked-out file and it is confirmed that it has not been changed by the other user, the changed file is registered by editing. (Commit) is performed (step S15). These tasks are repeated in the software development scene.

  Although the normal file editing flow in the conventional software configuration management system is performed as described above, the existence of a “problem file” that is performed without being checked out is pointed out.

  That is, the user may make a change to a file on the workspace without performing checkout for personal confirmation work or the like. For example, there is a case where code for log output for debugging is inserted into a file. FIG. 2 illustrates such a situation.

  In FIG. 2, the client PC used by the user acquires the latest software configuration information from the configuration management server (step S21) and places it on the workspace.

  When editing a desired file, the user declares (checks out) the edit (step S22) and performs an edit operation (step S23). At this time, a file that has not been checked out may be edited. Such a file becomes a problem file.

  Such a problem file needs to be registered in the configuration management server after the part edited for personal confirmation is deleted. If it is registered as it is (step S24), inconvenience arises.

  FIG. 3 shows an example of conventional measures for such a problem file.

  In FIG. 3, when an update is performed to synchronize the state of the workspace and the configuration management server after the problem file is generated (step S31), the problem file is detected due to a difference in update date or file size, and the problem file is dealt with. The user is notified to do this (step S32).

  The user will respond to each problem file on the spot, but if you are editing a large number of files, you will not be able to know why you made the change, so However, it is difficult to determine what action should be taken on the spot, and the solution may be wrong.

  In addition, since the problem file is checked only at the time of update, it is difficult to later find a file for which correspondence has been suspended, and it may be registered in the configuration management server in a state of lack of correspondence (step S33). ).

  The present invention has been proposed in view of the above-described conventional problems, and the object of the present invention is to a file (problem file) that has been changed without a declaration for regular editing by the user. It is to provide effective support to deal with it appropriately.

In order to solve the above-described problems, the present invention provides a software configuration management system for managing the software configuration of software assets including product source files and documents in software development, without performing a checkout by the user. A means for detecting a changed file as a problem file, a means for associating problem information with a file detected as a problem file and saving it in workspace management information, and a problem in which problem information is saved in workspace management information Workspace management for files that maintain the status at the time of detection of the file, means for returning the changed problem file to the status at the time of detection according to the user's instructions, and the problem file for which the user has declared completion In addition to canceling the problem information of the information, when the problem file is detected So that and means for releasing the status.

  According to the present invention, it is possible to effectively provide support for appropriately dealing with a problem file that has been changed without making a declaration for regular editing by the user.

It is FIG. (1) which shows the process example in the conventional configuration management system. It is FIG. (2) which shows the process example in the conventional configuration management system. It is FIG. (3) which shows the process example in the conventional configuration management system. It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the data structure example of various information. It is a flowchart (the 1) which shows the process example of embodiment. It is a figure which shows the example of preservation | save of problem information. It is a figure which shows the example of the notification of a problem file. It is a flowchart (the 2) which shows the process example of embodiment. It is a figure which shows the example of a search of a problem file. It is a figure which shows the example of presentation of a solution. It is a figure which shows the example of the declaration of completion. It is a flowchart (the 3) which shows the process example of embodiment. It is a figure which shows the example of a commit refusal.

  Hereinafter, preferred embodiments of the present invention will be described.

<Configuration>
FIG. 4 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 4, a plurality of client PCs 3 are connected to the configuration management server 1 via a network 2. The network 2 is often a LAN (Local Area Network), but is not limited thereto. Moreover, it is not limited to a wired / wireless connection form.

  The configuration management server 1 includes a configuration management unit 11 and a storage unit 12. The configuration management unit 11 is realized by a computer program executed on hardware resources such as a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory) of a computer that configures the configuration management server 1. Is. The storage unit 12 is realized by a storage medium such as an HDD (Hard Disk Drive) in the configuration management server 1.

  The client PC 3 includes a workspace management unit 31, a problem information storage unit 32, a problem file search unit 33, a solution navigation unit 34, a problem state storage unit 35, a registration reconfirmation unit 36, a file creation / editing unit 37, and various tools. 38 and a storage unit 39.

  The workspace management unit 31, the problem information storage unit 32, the problem file search unit 33, the solution navigation unit 34, the problem state holding unit 35, the reconfirmation unit 36 during registration, the file creation / editing unit 37, and various tools 38 The present invention is realized by a computer program executed on hardware resources such as a CPU, a ROM, and a RAM of a computer constituting the PC 3. The storage unit 39 is realized by a storage medium such as an HDD in the client PC 3.

  The configuration management server 1 has a function of holding and managing the version number, creation date, update date, and the like of a file created, edited, and committed by each client PC 3 in the configuration management information 121 of the storage unit 12. . The storage unit 12 also holds the old version of the file except when it is explicitly removed.

  FIG. 5A shows an example of the data structure of the configuration management information 121. “ID” “parent ID” “file / folder type” “icon ID” “file name / folder name” “version number” “creation date / time” -It has items (fields) such as "Update date and time" and "Checked out".

  “ID” is information for identifying a record. “Parent ID” is information for identifying a parent record located in a hierarchy above the record. “File / folder type” is information for identifying whether the target of the record is a file or a folder. The “icon ID” is information for identifying an icon image when the file or folder indicated by the record is displayed.

  “File name / folder name” is the name of the file or folder indicated by the record. “Version number” is information indicating the version of the file indicated by the record. The “creation date / update date / time” is information indicating the date / time when the file indicated by the record was created or updated. “Checking out” is information indicating whether or not the file indicated by the record is being checked out.

  Returning to FIG. 4, the configuration management unit 11 of the configuration management server 1 has a function of providing hierarchical information (configuration management information) of files to be managed in response to a request from the workspace management unit 31 of the client PC 3. Yes. In addition, the configuration management unit 11 has a checkout management function that exists conventionally.

  The client PC 3 is an information processing apparatus operated by a user (developer) who develops software.

  The workspace management unit 31 performs configuration management of the configuration management server 1 when the display function of the file hierarchy is activated or when an update instruction is received from the user in the already activated state or when a periodic automatic update is performed. It has a function of acquiring the latest configuration management information from the unit 11 and updating and displaying the work space management information 391 in the storage unit 39 indicating the directory of the storage area on the client PC 3. The workspace management unit 31 also has a function of notifying the user of a file that does not match the configuration information of the configuration management server 1 when the workspace is updated.

  FIG. 5B shows an example of the data structure of the work space management information 391. “ID” “parent ID” “file / folder type” “icon ID” “file name / folder name” “version number” “creation” Items such as “date / time / update date / time”, “during checkout”, “question type” are included. The difference from the configuration management information 121 shown in FIG. 5A is that “question type” is added. “Problem type” is information indicating the type of problem when the file indicated by the record is detected as a problem file.

  Returning to FIG. 4, when updating the workspace, the problem information storage unit 32 detects a file that has been changed without being checked out as a problem file, and sets the problem type in the information of the corresponding file in the workspace management information 391. It has a recording function.

  The problem file search unit 33 has a function of searching the work space management information 391 and acquiring and displaying problem file specific information when an operation of searching for a problem file is performed by a user.

  The solution navigation unit 34 refers to the solution information 392 in the storage unit 39 when the user performs a solution presentation operation on the problem file displayed by the problem file search unit 33, and the solution (Problem content, means for confirming problem status (presentation of various tools), solution options) are provided, and the selected solution is automatically executed. Further, the solution navigation unit 34 has a function of deleting the problem type and changing the status to a status other than the problem file when receiving a declaration of completion of the countermeasure for the problem file from the user.

  FIG. 5C shows an example of the data structure of the solution information 392, which includes items such as “problem type”, “problem content”, “link to means for solving the problem state”, and “solution option”. Yes. “Problem type” is information indicating the type of problem attached to the problem file. “Problem content” is information of an explanatory character string indicating the content of the problem. “Link to means for solving problem state” is link information for starting various tools 38 for solving the problem state. The “solution option” is information on options that the user can take. This option includes a script or the like for automatically executing the solution.

  Returning to FIG. 4, the problem state holding unit 35 records the state of the file recorded as a problem file in the work space management information 391 (the file content itself when the problem file is detected) as the problem file information 393. It has a function to do.

  FIG. 5D shows an example of the data structure of the problem file information 393, and has items such as “contents of problem file”.

  Returning to FIG. 4, the registration reconfirmation unit 36 performs a commit operation when a user performs a commit (registration to the server) operation on a file recorded as a problem file in the workspace management information 391. Has the function to reject.

  The file creation / editing unit 37 has a function of creating a new file on the workspace or editing a created file.

  The various tools 38 are a tool for analyzing and displaying a difference between two files, a tool for displaying a history, and the like.

<Operation>
FIG. 6 is a flowchart showing an example of processing in the above embodiment, and shows an example of processing when updating the workspace.

  In FIG. 6, under the control of the work space management unit 31 of the client PC 3, when a work space is updated (including initial display) in accordance with a user operation or by periodic processing or the like (step S101), The problem information storage unit 32 determines whether there is a problem file (step S102). Whether the file is a problem file is determined by, for example, whether or not a change has been made without being checked out.

  If it is determined that the problem file does not exist (Yes in step S102), the process ends without performing any particular processing. Thereafter, countermeasures for the problem file, file editing work, commit, etc. are performed as necessary (step S107).

  If it is determined that the problem file exists (No in step S102), the basic function of the workspace management unit 31 notifies that the file has been changed (step S103).

  Further, the problem information storage unit 32 stores (sets) the problem type in the workspace management information 391 for each file determined to be a problem file (step S104).

  Further, the problem state (the file content itself at the time when it is detected as the problem file) is held in the problem file information 393 (step S105), and the process ends (step S106). Thereafter, countermeasures for the problem file, file editing work, commit, etc. are performed as necessary (step S107).

  FIG. 7 is a diagram showing an example of saving problem information. By updating the workspace (step S101), a notification is made about the changed file (step S103), and the problem information is saved (step S104). This indicates that the state is maintained (step S105).

  FIG. 8 is a diagram showing an example of notification of a problem file. As shown by a broken line in the lower column of the screen, the problem file is displayed as a warning.

  In this way, the fact that the file is a problem file is saved and the state of the problem is retained, so that the user does not need to take immediate action when a change is notified, and then take action at a desired later time. (Step S107 in FIGS. 6 and 7) may be performed.

  FIG. 9 is a flowchart showing another processing example of the above-described embodiment, and shows a processing example when a user performs a solution work.

  In FIG. 9, when the user starts the solution work (step S111), the problem file search unit 33 of the client PC 3 searches for the problem file in response to the user's search request operation (step S112).

  FIG. 10 is a diagram showing an example of searching for a problem file. As shown in the lower left of the screen, the search is executed by selecting “search problem” from the pop-up menu displayed by right-clicking the mouse or the like. The search result of the problem file is displayed in a list as indicated by a broken line at the top of the screen.

  Returning to FIG. 9, the solution navigation unit 34 presents a solution in response to the user's solution presentation request operation (step S <b> 113).

  FIG. 11 is a diagram showing an example of presenting a solution. As shown by a broken line on the left side of the screen, the problem type, the date and time of occurrence, the problem content, and the like are displayed. Further, as shown by a broken line in the center on the right side of the screen, various tools that can be used are displayed as confirmation of the problem, and the corresponding tool can be activated by selecting it. In addition, as shown by the broken line at the lower right center of the screen, the choices that the user can take are displayed as selections of the solution, and the selection is made by using the radio button, and the “Execute Solution” button at the upper right of the screen is selected. The selected solution can then be implemented.

  Returning to FIG. 9, when the solution navigation unit 34 receives selection of a solution (step S114), the solution navigation unit 34 executes the solution (step S115).

  Next, when a declaration of completion of countermeasures for the problem file is received from the user (step S116), the problem type of the workspace management information 391 is deleted (step S117), and the corresponding contents of the problem file information 393 are released (step S117). Step S117), the process is terminated (Step S118).

  FIG. 12 is a diagram showing an example of a completion declaration. When a problem solving operation (measure) is performed, it can be restored to the original state based on the problem file information 393 before the completion declaration is made. Is shown. As a result, even if an erroneous measure is taken, it is possible to return to the original state and start the problem solving work from the beginning.

  FIG. 13 is a flowchart showing another processing example of the above-described embodiment, and shows a processing example when the user commits.

  In FIG. 13, when the user performs a commit operation (step S121) and the work space management unit 31 of the client PC 3 accepts the commit operation (step S122), the re-confirmation unit 36 at registration registers the work space management information for the corresponding file. The question type 391 is referred to and it is determined whether it is a question file (step S123).

  When it is determined that the file is not a problem file (Yes in step S123), commit is performed (step S124). If it is determined that the file is a problem file (No in step S123), the commit is rejected (step S125). Then, the process ends (step S126).

  FIG. 14 is a diagram showing an example of commit refusal. When a commit is requested for a file (problem file) for which problem solving work (measure) is suspended and the problem is not solved, the commit is rejected (step S125) is shown. As a result, registration to the server cannot be performed in a state where problem solving has not been completed, and it is possible to prevent a problem file from being erroneously registered in the server due to a lack of user response.

<Summary>
As described above, according to the present embodiment, it is possible to effectively provide support for appropriately dealing with a problem file that has been changed without making a declaration for regular editing by the user.

  The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to these embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

DESCRIPTION OF SYMBOLS 1 Configuration management server 11 Configuration management part 12 Storage part 121 Configuration management information 2 Network 3 Client PC
31 workspace management unit 32 problem information storage unit 33 problem file search unit 34 solution navigation unit 35 problem state holding unit 36 reconfirmation unit upon registration 37 file creation / editing unit 38 various tools 39 storage unit 391 workspace management information 392 solution Measure information 393 Problem file information

Japanese Patent No. 5078679

Claims (4)

A software configuration management system for managing the software configuration of software assets including product source files and documents in software development,
Means for detecting as a problem file a file that has been modified without a checkout by the user;
Means for associating problem information with a file detected as a problem file and storing it in workspace management information ;
Means for holding a state at the time of detection of a problem file in which problem information is stored in the workspace management information;
According to the user's instructions, a means to return the changed problem file to the state at the time of detection,
Means for canceling the problem information of the workspace management information and releasing the state at the time of detection of the problem file for the problem file for which the completion is declared by the user. Software configuration management system. In the software configuration management system according to claim 1,
A software configuration management system comprising means for searching problem information in the workspace management information and extracting a problem file in accordance with a user instruction. In the software configuration management system according to claim 2,
A software configuration management system comprising means for presenting a solution to an extracted problem file. In the software configuration management system according to any one of claims 1 to 3 ,
Means for detecting a registration request for a problem file in which problem information is stored in the workspace management information;
A software configuration management system comprising means for rejecting a registration request.