JP5661505B2 - Parallel development management device - Google Patents

Description

  The present invention relates to a parallel development management apparatus and method for managing the development of a computer program.

  In recent years, as business systems become more complex and sophisticated, the number of computer programs (hereinafter simply referred to as programs) for constructing the business systems has become enormous, and the contents of the programs have become sophisticated. In order to suitably manage such new development and modification of such a program, the present applicant has proposed a program development management apparatus in Patent Document 1.

This program development management device refers to a theme-specific program table for managing a program to be developed and a release condition for each development theme, and a theme-specific program table, and programs having the same release condition as one release unit. A directory generation unit that extracts and generates a release unit directory, and stores the extracted release unit program in the directory.
According to the program development management device described in Patent Document 1, it is possible to greatly reduce the program release omission and release mistake at the time of release.

JP 2009-244974 A

  In the program development management technique represented by Patent Document 1, there can be a so-called parallel development state in which two or more development themes specify one program. In the parallel development state, mistakes in program management are likely to occur due to lack of cooperation between persons in charge.

  The present invention has been made in view of these problems, and an object thereof is to provide a management technique capable of reducing mistakes in parallel development of programs.

  One embodiment of the present invention relates to a parallel development management apparatus. The parallel development management device includes a storage area for storing a computer program, a reception unit that receives designation of a computer program to be changed for each development theme, a reading unit that reads the specified computer program from the storage area, and a reading unit When a change according to the theme is made to the computer program read out by, an overwriting unit that overwrites the computer program stored in the storage area by the changed computer program and a notification destination associated with the theme are predetermined. A notification unit for notifying the information. When the receiving unit receives the designation of one computer program for the first and second themes, the reading unit reads one computer program for the first theme from the storage area as the first computer program. Then, one computer program for the second theme is read from the storage area as the second computer program. When the overwriting unit overwrites one computer program stored in the storage area by the second computer program prior to the first computer program, the notifying unit displays information on one computer program and information on the second theme. Notification is made to the notification destination associated with the first theme.

  According to this aspect, when the overwriting unit overwrites one computer program stored in the storage area by the second computer program prior to the first computer program, the notification destination associated with the first theme is: Information on one computer program and information on the second theme can be known.

  Another aspect of the present invention is also a parallel development management apparatus. The apparatus receives a designation of the first computer program for the first theme of development and a storage area for storing the first computer program and the second computer program related to each other, and the second theme for the development. A receiving unit that receives the designation of the second computer program, and a reading unit that reads the first computer program from the storage area for the first theme and reads the second computer program from the storage area for the second theme; A notification unit for notifying information on the second theme to a notification destination associated with the first theme.

  According to this aspect, when the first theme and the second theme respectively specify the first computer program and the second computer program related to each other, the notification destination associated with the first theme is the second theme. You can know the information.

  It should be noted that any combination of the above-described constituent elements, and those in which constituent elements and expressions of the present invention are mutually replaced between apparatuses, methods, systems, programs, recording media storing programs, and the like are also aspects of the present invention. It is effective as

  According to the present invention, mistakes can be reduced in parallel development of programs.

It is explanatory drawing which shows typically the program development system which has the parallel development management apparatus which concerns on embodiment. It is a flowchart which shows an exemplary series of processes in the parallel development management apparatus of FIG. It is a block diagram which shows the function and structure of the parallel development management apparatus which concerns on embodiment. FIG. 4 is a schematic diagram illustrating an example of a directory configuration of the storage device in FIG. 3. It is a data structure figure which shows an example of the parallel development management table of FIG. It is a data structure figure which shows an example of the development theme management table of FIG. FIG. 5 is a data structure diagram illustrating an example of a first dependency relationship table in FIG. 4. FIG. 5 is a data structure diagram illustrating an example of a second dependency relationship table in FIG. 4. 4 is a chart showing an exemplary series of processes in the parallel development management device of FIG. 3 along a time series. 4 is a chart showing an exemplary series of processes in the parallel development management device of FIG. 3 along a time series. 4 is a chart showing an exemplary series of processes in the parallel development management device of FIG. 3 along a time series. It is a representative screen figure of a 1st notification screen. It is a typical screen figure of an inquiry information input screen. It is a representative screen figure of a 3rd notification screen. It is a representative screen figure of a 4th notification screen.

  The present invention will be described below based on preferred embodiments with reference to the drawings. The same or equivalent components, members, and processes shown in the drawings are denoted by the same reference numerals, and repeated descriptions are omitted as appropriate.

  FIG. 1 is an explanatory diagram schematically showing a program development system 2 having a parallel development management apparatus 100 according to an embodiment. The program development system 2 manages a program that constitutes an application functioning on the production environment server 116 that is a server installed in the customer's system. The program development system 2 corrects, updates, adds, etc. the program based on the development theme (hereinafter referred to as the development theme) and reflects it on the production environment server 116. The development theme is for the purpose of changing an application, for example. For example, in the development theme “bug correction”, the program development system 2 applies the correction corresponding to the found bug to the program and distributes it to the production environment server 116. For example, in the development theme “add new function”, the program development system 2 distributes a new program corresponding to the new function of the developed application to the production environment server 116.

  The program development system 2 includes a parallel development management apparatus 100 according to the embodiment, a plurality of (three in FIG. 1) user terminals 102, a development environment server 110, a test environment server 112, and a production gateway 114. Those members of the program development system 2 are connected to each other by a network 108 such as the Internet. The production gateway 114 is connected to the production environment server 116 through a network (not shown) or the like, and serves as a gateway to the production environment server 116.

  The user of the program development system 2 is, for example, a developer who develops a program, a development leader who determines the development theme and takes charge of development, a development manager who manages development, and distribution (ie, release) of the program to the production environment server Including the release person in charge.

  Hereinafter, a case will be described in which the program development system 2 and the parallel development management apparatus 100 handle programs individually. However, the technical idea according to the present embodiment can be applied to a case where a set or group of related programs such as a program archive unit may be treated as a unit. It will be obvious to those skilled in the art.

  FIG. 2 is a flowchart showing an exemplary series of processes in the parallel development management apparatus 100 of FIG. The development leader accesses the parallel development management device 100 from his / her user terminal, and associates the development theme ID for specifying the development theme, the name of the development theme, and the name of the person responsible for the development theme in association with each other. Register with. The parallel development management device 100 accepts the registration (S202). A developer engaged in a registered development theme accesses the parallel development management apparatus 100 from his / her user terminal, and designates a program that needs to be changed in the registered development theme as a program to be changed. The program specified here is a program stored in a production system storage area (described later) of the parallel development management apparatus 100 in principle.

  The parallel development management apparatus 100 accepts the designation, reads the designated program from the production system storage area, and copies it to the development system storage area (described later). The program duplicated in the development system storage area in this way is called a program A. The parallel development management device 100 transmits the program A to the development environment server 110 (S204). The developer accesses the development environment server 110 from his / her user terminal via the parallel development management apparatus 100 and makes necessary changes to the program A. The program A after the change is completed is called a program B. The developer performs a unit test on the program B in the development environment server 110 after completion of the change. When the program B passes this unit test, the developer transmits the program B from the development environment server 110 to the parallel development management apparatus 100. The parallel development management apparatus 100 receives the program B transmitted in this way, and overwrites the program A stored in the development storage area with the received program B (S206).

  When a connection / integrated test is required in the development theme, the parallel development management apparatus 100 transmits the program B to the test environment server 112 (S208). The developer accesses the test environment server 112 from his / her user terminal via the parallel development management apparatus 100, and performs a connected / integrated test including the program B. If the connection / integration test is passed, the developer accesses the parallel development management apparatus 100 from his / her user terminal and registers the fact in the parallel development management apparatus 100. The parallel development management apparatus 100 accepts the registration (S210).

  When the development leader determines that necessary changes have been made to the development theme and the release preparation is complete, the development leader accesses the parallel development management device 100 from his / her user terminal, specifies the development theme ID and the program to be released, and releases the release. Apply. The parallel development management apparatus 100 accepts this release application (S212). When receiving the release application, the parallel development management apparatus 100 extracts the parallel development status of the program designated as the release target, and outputs the result using a printer (not shown) or the like. The person in charge discusses whether or not to approve the release at the release confirmation meeting based on the information printed in this way. When the release is approved at the conference, the development leader or another user accesses the parallel development management apparatus 100 from his / her user terminal and approves the release. The parallel development management apparatus 100 accepts the release approval (S214). Upon receiving the release approval, the parallel development management apparatus 100 transmits the program B to the production gateway 114 (S216) and overwrites the read source program stored in the production storage area by the program B. Hereinafter, the completion of release is defined as the read source program stored in the production storage area is overwritten.

  FIG. 3 is a block diagram showing the function and configuration of the parallel development management apparatus 100 according to the embodiment. Each block shown here can be realized in hardware by an element or a mechanical device such as a CPU (central processing unit) of a computer, and is realized by a program in software. Describes functional blocks realized by collaboration. Therefore, it is understood by those skilled in the art who have touched this specification that these functional blocks can be realized in various forms by a combination of hardware and software.

  The parallel development management device 100 includes an input / output interface unit 10, a reception unit 20, a reading unit 30, a test / release management unit 40, a production environment distribution unit 50, an overwrite unit 60, a notification unit 70, and a storage device 90.

  FIG. 4 is a schematic diagram showing an example of the directory configuration of the storage device 90 of FIG. The storage device 90 includes a production system storage area 92, a development system storage area 94, and a management system storage area 96. The production system storage area 92 stores the same program as that running on the production environment server 116 in a directory configuration similar to that of the production environment server 116. Hereinafter, “the two programs are the same” means that the content of one program is the same as the content of the other program. That is, even if two programs are held in different servers, the same is true if the contents are the same.

  The development storage area 94 stores a program generated by duplicating a program designated as a change target for each development theme. The development system storage area 94 has a directory whose name can identify the development theme for each development theme received by the parallel development management apparatus 100. A program generated by duplicating a program designated as a change target in each development theme is placed in the directory of the development theme.

  The management system storage area 96 stores a parallel development management table 302, a development theme management table 304, a first dependency relationship table 306, and a second dependency relationship table 308.

FIG. 5 is a data structure diagram showing an example of the parallel development management table 302. The parallel development management table 302 stores a development theme ID 312, a status ID 314, a start date 316, an end date 318, and a release application date 320 in association with each management target ID 310.
The management target ID is an ID for identifying a target managed by the parallel development management apparatus 100 in the parallel development management apparatus 100. As described above, in the present embodiment, a case where a program is handled individually will be described. Therefore, the management target ID is an ID for identifying a program such as a program name or a path in the parallel development management apparatus 100 for the program. In particular, the management target ID is an ID that identifies a program stored in the production system storage area 92.

  The status ID is an ID that specifies a state in the development theme of the program specified by the management target ID. This state includes a development state where the program has been changed and tested, a release application state after the release is requested until the release is completed, a released state where the release has been completed, There is. In FIG. 5, the status ID “S1” corresponds to the developing state, the status ID “S2” corresponds to the release application state, and the status ID “S3” corresponds to the released state.

  Each state can be subdivided with reference to FIG. The development state includes a changing state in which a modification or the like has been made in the development environment server 110, a unit test completion state in which the unit test has been completed in the development environment server 110, and a connection test in which the connection test has been completed in the test environment server 112. It can be divided into a completed state and a comprehensive test completion state in which the comprehensive test is completed in the test environment server 112. The release requesting state is divided into a release approval waiting state waiting for release approval and a release approval completed state from when the release is approved until the release is actually completed.

The start date is the start date of the development theme, and in particular is the date when the program specified by the management target ID is designated as the program to be changed.
The end date is the end date of the development theme, and in particular, the date when the release of the program specified by the management target ID is completed.
The release application date is the date when the release of the program specified by the management target ID is applied.

  FIG. 6 is a data structure diagram showing an example of the development theme management table 304. The development theme management table 304 is scheduled to be released for each development theme ID 322. The development theme name 324 briefly indicates the contents of the development theme, the management target ID 326 of the program designated as a change target by the development theme, and the development theme. And the scheduled release date 328 that is a date to be stored.

There are cases where a plurality of different programs are related, such as a case where a program calls or references another program, or a source program and an execution program generated by compiling it. The association of two programs includes the dependency of two programs, that is, one program depends on the other program. This is the case, for example, when one program is necessarily changed when the other program is changed. For convenience, the dependent program is described as “child”, and the dependent program is described as “parent”.
In the present embodiment, it is assumed that only one parent program can be set for one child program. However, for example, it is obvious to those skilled in the art who have touched this specification that the technical idea according to the present embodiment can be applied even when the parent program and the child program are many-to-many.

  FIG. 7 is a data structure diagram illustrating an example of the first dependency relationship table 306. The first dependency relationship table 306 stores a dependency relationship ID 334 that specifies a dependency relationship between programs and a parent management target ID 336 that is a management target ID of the parent program in the dependency relationship in association with each other.

  FIG. 8 is a data structure diagram illustrating an example of the second dependency relationship table 308. The second dependency relationship table 308 stores a child management target ID 330 that is a management target ID of a child program in the dependency relationship and a dependency relationship ID 332 that specifies the dependency relationship in association with each other.

  In parallel development management apparatus 100 according to the present embodiment, instead of preparing a table that directly associates a child program with a parent program, a dependency relationship ID that links the child program is used and the dependency relationship is managed by two different tables. . Although the former is also possible in other embodiments, the reason for adopting the latter in this embodiment is as follows.

An exemplary procedure in which a user of the parallel development management apparatus 100 newly registers a parent program, a child program, and their dependencies in the parallel development management apparatus 100 is as follows.
(1) The user registers the parent program in the production storage area 92 of the parallel development management device 100.
(2) The user assigns a dependency ID of the dependency and inputs it to the parallel development management apparatus 100 together with the parent management target ID of the parent program. The receiving unit 20 of the parallel development management apparatus 100 registers the input dependency relationship ID and the parent management target ID in the first dependency relationship table 306 in association with each other.
(3) The user registers the child program in the production system storage area 92 of the parallel development management apparatus 100 and inputs the numbered dependency ID and the child management target ID of the child program to the parallel development management apparatus 100. The receiving unit 20 of the parallel development management apparatus 100 registers the input child management target ID and the dependency relationship ID in the second dependency relationship table 308 in association with each other.

  In this case, since the child program is registered in (3) after the dependency ID is assigned in (2), the parent program and the child program cannot be registered at the same time. Further, in order to register the dependency relationship, the parent program must be registered in the production storage area 92. Therefore, since the child program is registered after it is determined that the parent program exists, erroneous registration can be suppressed.

Returning to FIG.
The input / output interface unit 10 is connected to the network 108 and controls communication between the parallel development management device 100 and an external device. The external devices are, for example, a plurality of user terminals 102, a development environment server 110, a test environment server 112, and a production gateway 114. The input / output interface unit 10 is configured using a known communication technology for exchanging data and the like between devices via the network 108, for example, a technology for performing communication according to the TCP / IP protocol.

The accepting unit 20 accepts designation of a program to be changed for each development theme. The reception unit 20 includes a login unit 22, a development theme reception unit 24, a change target designation reception unit 26, a dependency relationship reference unit 28, and a management table registration unit 29.
The login unit 22 determines whether or not to allow login from the user. When the login unit 22 acquires a login request from the user terminal via the input / output interface unit 10, the login unit 22 transmits information for displaying a screen for prompting input of a user ID and a password to the user terminal. . The login unit 22 acquires and authenticates the user ID and password input by the user to the user terminal via the input / output interface unit 10. If the authentication is successful, the login unit 22 allows the user to log in and starts a session.

  The user ID is an ID that identifies a user of the parallel development management apparatus 100. The user ID is set so as to be able to identify the type of user, that is, whether it is a developer, a development leader, a development manager, or a release manager.

  The development theme reception unit 24 receives the development theme ID, the development theme name, and the scheduled release date from the user terminal of the development leader via the input / output interface unit 10 and registers them in the development theme management table 304. The development theme ID may be determined by the development theme reception unit 24. Hereinafter, the development theme ID received by the development theme reception unit 24 is referred to as a received development theme ID.

  The change target designation receiving unit 26 is designated as needing to be changed in accordance with the development theme from the user terminal of the developer engaged in the development theme specified by the received development theme ID via the input / output interface unit 10. The management target ID of the acquired program is acquired. The change target designation receiving unit 26 receives the acquired management target ID and registers it in the development theme management table 304 in association with the development theme ID. Hereinafter, the management target ID acquired by the change target specification receiving unit 26 is referred to as a specified management target ID, and the program specified by the specified management target ID is referred to as a specified program.

  The dependency relationship reference unit 28 refers to the first dependency relationship table 306 and the second dependency relationship table 308 to determine whether there is a program having a dependency relationship with the designated program. When such a program exists, the dependency relationship reference unit 28 additionally receives a management target ID of such a program and registers it in the development theme management table 304 in association with the development theme ID. That is, the development theme management table 304 stores, for each development theme ID of the development theme, a management target ID of a program specified as a change target in the development theme and a management target ID of a program that is dependent on the program.

In particular, the dependency relationship reference unit 28 first refers to the second dependency relationship table 308 and extracts the dependency relationship ID corresponding to the designated management target ID, if any. Next, the dependency relationship reference unit 28 refers to the first dependency relationship table 306 and extracts a parent management target ID corresponding to the extracted dependency relationship ID. Further, the dependency relationship reference unit 28 refers to the second dependency relationship table 308 and extracts the corresponding parent relationship ID when there is a corresponding dependency relationship ID as the child management target ID. Hereinafter, the dependency reference unit 28 refers to the process of alternately referencing the first dependency relationship table 306 and the second dependency relationship table 308, and the corresponding dependency relationship when the extracted parent management target ID is used as the child management target ID. Repeat until there are no IDs.
The dependency relationship reference unit 28 registers all the parent management target IDs extracted by the above processing in the development theme management table 304 in association with the received development theme ID.

For example, consider a case where the accepted development theme ID is “T1” and the designated management target ID is “A100_1.pco”.
The dependency relationship reference unit 28 refers to the second dependency relationship table 308 illustrated in FIG. 8 and extracts the dependency relationship ID “x1”. The dependency relationship reference unit 28 refers to the first dependency relationship table 306 shown in FIG. 7 and extracts the parent management target ID “MAKEFILE”. Next, the dependency relationship reference unit 28 refers to the second dependency relationship table 308 illustrated in FIG. 8 and extracts the dependency relationship ID “x2” corresponding to the extracted parent management target ID “MAKEFILE”. The dependency relationship reference unit 28 refers to the first dependency relationship table 306 shown in FIG. 7 and extracts the parent management target ID “A100.exe”. The dependency relationship reference unit 28 refers to the second dependency relationship table 308 illustrated in FIG. 8 and determines that there is no dependency relationship ID corresponding to the extracted parent management target ID “A100.exe”. The dependency relationship reference unit 28 accepts the extracted parent management target IDs “MAKEFILE” and “A100.exe” and additionally registers them in the development theme management table 304 in association with the development theme ID “T1”.
Hereinafter, the parent management target ID extracted by the dependency relationship reference unit 28 is referred to as a dependency management target ID, and the program specified by the dependency management target ID is referred to as a dependency program.

  The management table registration unit 29 correlates the designated management target ID, the accepted development theme ID, “S1” as the status ID, and the date when the designated management target ID is acquired as the start date, in association with each other. Register with. In addition, the management table registration unit 29 associates the dependency management target ID, the accepted development theme ID, “S1” as the status ID, and the date when the specified management target ID is acquired as the start date, in association with each other. 302 is registered.

The reading unit 30 reads the designated program from the production system storage area 92. The reading unit 30 includes a development theme directory generation unit 32, a change target replication unit 34, and a change target transmission unit 36.
The development theme directory generation unit 32 generates a directory corresponding to the received development theme ID in the development system storage area 94.

  The change target duplicating unit 34 reads the designated program and the dependent program from the production storage area 92 and duplicates them. Hereinafter, a program duplicated from a designated program is referred to as a designated duplicate program, and a program duplicated from a dependent program is referred to as a dependent duplicate program. The change target duplication unit 34 puts the designated duplication program and the dependent duplication program into the directory generated by the development theme directory generation unit 32. An example of processing in the change target duplication unit 34 is indicated by a dashed arrow or a one-dot chain arrow in FIG.

  The change target transmission unit 36 transmits the designated replication program and the dependent replication program to the development environment server 110 via the input / output interface unit 10.

  In the development environment server 110, the developer accepts the designated duplication program and the dependent duplication program, changes the correction according to the development theme specified by the development theme ID, and performs the unit test. Hereinafter, the designated replication program that has completed the change and passed the unit test is referred to as a post-change program, and the dependent replication program that has been changed and passed the unit test is referred to as a post-dependency change program.

  The test / release management unit 40 manages the concatenation / integrated test and release of the program that has completed the change according to the development theme and passed the unit test. The test / release management unit 40 includes a post-change program acquisition unit 42, a test environment distribution unit 44, a release application reception unit 46, a release approval / disapproval determination unit 80, and a release approval reception unit 48.

  The post-change program acquisition unit 42 acquires the designated post-change program and the post-dependency change program from the development environment server 110 via the input / output interface unit 10. The post-change program acquisition unit 42 overwrites the specified replication program and the dependent replication program stored in the directory corresponding to the received development theme ID in the development storage area 94 with the acquired post-specification change program and dependency post-change program, respectively. To do.

  When the development theme specified by the received development theme ID requires a connection / general test, the test environment distribution unit 44 sends the designated and changed program to the test environment server 112 via the input / output interface unit 10. Send.

  The release application receiving unit 46, from the user terminal of the development leader via the input / output interface unit 10, releases a release development theme ID that identifies a development theme to be released and a release management target ID that identifies a program designated as the release target. Accept. Here, the release application accepting unit 46 refers to the first dependency relationship table 306 and the second dependency relationship table 308 in the same manner as the dependency relationship reference unit 28, and releases a program having a dependency relationship with the program designated as the release target. It may be determined whether or not it is a target, and if it is not, it may be added to the release target. In this case, release leakage can be suppressed.

  The release application reception unit 46 accesses the parallel development management table 302, rewrites the received release management target ID and the status ID corresponding to the release development theme ID to “S2,” and registers the release application date.

Hereinafter, a case where the release application receiving unit 46 receives a received development theme ID as a release development theme ID and a designated management target ID and a dependency management target ID as release management target IDs will be considered.
The release approval / disapproval determination unit 80 determines whether the release is approved for the designated program and the dependent program. Details will be described later.
The release approval receiving unit 48 receives release approval for the development theme specified by the received development theme ID from the development leader or other user's user terminal via the input / output interface unit 10.

  When the release approval reception unit 48 receives the release approval, the production environment distribution unit 50 transmits the designated change program and the dependency change program to the production gateway 114 via the input / output interface unit 10.

When the release approval is received by the release approval receiving unit 48, the overwriting unit 60 overwrites the designated program and the dependent program stored in the production storage area 92 by the designated change program and the dependency changed program, respectively.
The overwriting unit 60 accesses the parallel development management table 302, rewrites the status ID corresponding to the designated management target ID and the accepted development theme ID to “S3”, and registers the end date. The same applies to the dependency management target ID.

The notification unit 70 notifies predetermined information to a notification destination associated with the development theme. For example, the notification unit 70 transmits screen information for displaying a screen presenting predetermined information on the display of the user terminal to the user terminal via the input / output interface unit 10. For example, the notification unit 70 transmits an e-mail including predetermined information to the e-mail address of the development leader or developer via the input / output interface unit 10.
The notification unit 70 includes a determination result output unit 71, an inquiry request reception unit 72, a designation detection unit 74, a parallel development information extraction unit 75, a catch-up necessity determination unit 76, and a parallel development status presentation unit 77. Details of each part will be described later.

  In the operation of the parallel development management apparatus 100, one program stored in the production storage area 92 may be specified by a plurality of different development themes. In addition, two related programs stored in the production system storage area 92 may be designated by different development themes. These are all parallel developments of programs.

The parallel development management table 302 includes, for each management target ID, a development theme ID of a development theme that specifies a program specified by the management target ID and a program that is dependent on the program specified by the management target ID (in particular, A development theme ID of a development theme that designates a child program whose parent program is a program specified by the management target ID is stored.
When the parallel development management table 302 stores a management target ID and a plurality of development theme IDs in association with each other, the parallel development management apparatus 100 has a program specified by the management target ID in a state of parallel development. Recognize. Therefore, the parallel development management apparatus 100 can recognize a program that becomes parallel development because of the dependency relationship as a program that is in the state of parallel development.

  For example, when the parent program and the child program are designated by different development themes, the parallel development management table 302 stores the development theme IDs of both development themes in association with the management target ID that identifies the parent program. When two child programs having the same parent program are designated by different development themes, the parallel development management table 302 associates the development theme IDs of both development themes with the management target ID that identifies the parent program. Remember.

More detailed processing of the parallel development management apparatus 100 regarding parallel development will be described.
Hereinafter, a parallel development program is designated as a program that is stored in the production system storage area 92 and is in a parallel development state according to two different development themes, a parallel development management target ID that designates the parallel development program is designated, and a parallel development program is designated. One development theme is referred to as a first development theme, the development theme ID is referred to as a first development theme ID, the other development theme is referred to as a second development theme, and the development theme ID is referred to as a second development theme ID. The parallel development management table 302 stores a parallel development management target ID, a first development theme ID, and a second development theme ID in association with each other. The following description applies to both the case where the parallel development program enters the parallel development state by the two development themes specifying the program directly and the case where the parallel development program enters the parallel development state due to the dependency.

FIG. 9 is a chart showing an exemplary series of processes in the parallel development management apparatus 100 in chronological order. FIG. 9 shows exemplary processing when a parallel development program is designated.
The developer engaged in the first development theme designates a parallel development program or a child program of the parallel development program (S402). The receiving unit 20 registers the parallel development management target ID, the first development theme ID, and the status ID “S1” in association with each other in the parallel development management table 302 (S404).

  The development theme directory generation unit 32 generates a first directory corresponding to the first development theme ID in the development storage area 94 (S406). The change target duplication unit 34 reads the parallel development program from the production storage area 92 and duplicates it, thereby generating a first duplication program. The change target duplicating unit 34 stores the first duplicating program in the first directory (S408). The change target transmission unit 36 transmits the first replication program to the development environment server 110 via the input / output interface unit 10 (S410).

  Thereafter, the developer engaged in the second development theme designates a parallel development program or a child program of the parallel development program (S412). The management table registration unit 29 accesses the parallel development management table 302 for registration, and detects that the parallel development management target ID is already registered in the parallel development management table 302. The management table registration unit 29 passes the parallel development management target ID and the second development theme ID to the designation detection unit 74. Upon receiving such information, the designation detection unit 74 detects parallel development for the parallel development program (S414).

When the designation detection unit 74 detects parallel development, the parallel development information extraction unit 75 refers to the parallel development management table 302 and first development theme ID corresponding to the parallel development management target ID as the development theme ID of the partner of parallel development. And the status ID are extracted (S416).
When the status ID extracted by the parallel development information extraction unit 75 is “S1” or “S2”, that is, when the status is not released, the parallel development status presentation unit 77 determines the parallel development management target ID and the first development theme. Screen information for displaying a first notification screen 500 (described later in FIG. 12) including the ID in the form of text on the display of the user terminal is generated. The parallel development status presentation unit 77 transmits the generated screen information to the user terminal of the developer engaged in the second development theme via the input / output interface unit 10 (S418).

  The parallel development status presentation unit 77 generates screen information for displaying a second notification screen including the parallel development management object ID and the second development theme ID in the form of text on the display of the user terminal. If the developer engaged in the first development theme is in a session of the developer who is engaged in the first development theme, the parallel development status presentation unit 77 generates a screen after logging in again if the developer engaged in the first development theme is logged out. Information is transmitted to the user terminal of the developer engaged in the first development theme via the input / output interface unit 10 (S420).

The receiving unit 20 registers the parallel development management target ID and the second development theme ID in the parallel development management table 302 in association with each other (S422).
The development theme directory generation unit 32 generates a second directory corresponding to the second development theme ID in the development storage area 94 (S424).
The change target duplication unit 34 reads the parallel development program from the production storage area 92 and duplicates it, thereby generating a second duplication program. The change target replication unit 34 stores the second replication program in the second directory (S426).
The change target transmission unit 36 transmits the second replication program to the development environment server 110 via the input / output interface unit 10 (S428).

After the first change, the first replication program that passed the unit test after the change according to the first development theme was completed, and after the second change, the second replication program that completed the change according to the second development theme and passed the unit test This is called a program.
When the release of the second development theme is completed prior to the first development theme, the first development theme “catch up with” the second development theme to incorporate the change according to the second development theme into the first changed program. ".

FIG. 10 is a chart showing an exemplary series of processes in the parallel development management device 100 in chronological order. In FIG. 10, an exemplary process when the status of parallel development is queried is shown.
The user terminal of the developer engaged in the first development theme transmits a parallel development inquiry request for inquiring the status of parallel development to the parallel development management apparatus 100 via the network 108 (S430). When receiving the parallel development inquiry request, the inquiry request receiving unit 72 requests the developer engaged in the first development theme for information such as the development theme ID (S432). In particular, the inquiry request accepting unit 72 displays screen information for displaying an inquiry information input screen 506 (described later in FIG. 13) on the display of the user terminal that prompts the user to input inquiry information using the user ID or development theme ID as an essential input item. Is generated. The inquiry request reception unit 72 transmits this screen information to the user terminal of the developer engaged in the first development theme via the input / output interface unit 10.

  The user terminal of the developer engaged in the first development theme provides the requested information including the first development theme ID to the inquiry request reception unit 72 (S434). In particular, the inquiry request receiving unit 72 acquires information input to the inquiry information input screen 506 displayed on the display of the user terminal from the user terminal via the input / output interface unit 10. The inquiry request receiving unit 72 extracts the first development theme ID from the acquired information (S436).

  The parallel development information extraction unit 75 refers to the development theme management table 304 and extracts a management target ID corresponding to the extracted first development theme ID. The management target ID extracted in this way includes a parallel development management target ID. The parallel development information extracting unit 75 refers to the parallel development management table 302 and selects a management target ID associated with a development theme ID other than the first development theme ID from the extracted management target IDs. In particular, since the first development theme ID and the second development theme ID are associated with the parallel development management object ID in the parallel development management table 302, the parallel development information extraction unit 75 selects the parallel development management object ID ( S438).

  The catch-up necessity determination unit 76 determines whether or not the first development theme needs to catch up with the second development theme for the parallel development program (S440). When the overwriting unit 60 overwrites the parallel development program stored in the production storage area 92 by the second changed program prior to the first changed program, the catch-up necessity determination unit 76 sets the first development theme as the first 2 Judge that it is necessary to catch up with the development theme. Otherwise, the catch-up necessity determination unit 76 determines that it is not necessary to catch up.

  In particular, the catch-up necessity determination unit 76 refers to the parallel development management table 302, and for the parallel development management target ID, the status ID corresponding to the second development theme ID is “S3” and the second development theme ID. If the end date corresponding to is after the start date corresponding to the first development theme ID, it is determined that the first development theme needs to catch up with the second development theme. Further, the catch-up necessity determination unit 76 determines that it is not necessary to catch up when the status ID corresponding to the second development theme ID is “S1”, for example.

  The parallel development status presentation unit 77 associates the management target ID selected by the parallel development information extraction unit 75 with the development theme ID of the partner for parallel development and the determination result in the catch-up necessity determination unit 76 and notifies the inquiry source of the association. . In particular, the parallel development status presentation unit 77 displays a third notification screen 508 (described later in FIG. 14) including the parallel development management target ID, the necessity of catching up, and the second development theme ID on the display of the user terminal. Generate information. The parallel development status presentation unit 77 transmits the screen information to the user terminal of the developer engaged in the first development theme via the input / output interface unit 10 (S442).

  Note that the inquiry request reception unit 72 may start an inquiry about the parallel development status triggered by the login of the developer engaged in the first development theme instead of the parallel development inquiry request.

FIG. 11 is a chart showing an exemplary series of processes in the parallel development management apparatus 100 in time series. In FIG. 11, an exemplary process during release is shown.
When the first changed program is transmitted from the development environment server 110 to the parallel development management apparatus 100 and the connection / integration test is completed, the development leader of the first development theme applies for the release of the parallel development program (S444). The release application receiving unit 46 receives this release application.

When a release application is received by the release application receiving unit 46, the release approval / disapproval determination unit 80 determines whether the parallel development program is approved for release.
The release approval / disapproval determination unit 80 refers to the parallel development management table 302, and (i) whether the parallel development program has been in the state of parallel development between the start date of the first development theme and the release application date. Or (b) If the second development theme has not been applied for release and the catch-up for the second development theme has been completed, or (v) the release application has been filed by the second development theme If it is not necessary to catch up with the second development theme, it is determined that the parallel development program may be released.

  More specifically, the release approval / disapproval determination unit 80 refers to the parallel development management table 302 and extracts the status ID of the second development theme ID associated with the parallel development management target ID. When the extracted status ID is “S2”, the release approval / disapproval determination unit 80 notifies the developer engaged in the first development theme that there is a second development theme for which a release application is being applied for the parallel development program. The release approval / disapproval determination unit 80 may prohibit the release of the parallel development program based on the first development theme. The release approval / disapproval determination unit 80 may access the parallel development management table 302, return the status ID corresponding to the first development theme ID to “S1”, and delete the release application date.

  When the extracted status ID is “S3”, that is, when the release by the second development theme is completed before the release application by the first development theme, the release approval / disapproval determination unit 80 performs the second development on the parallel development program. It is determined that it is necessary to catch up with the theme (S446). The release approval / disapproval determination unit 80 determines whether or not the change according to the second development theme is reflected in the first changed program (S448). The release approval / disapproval determination unit 80 may make this determination based on a report from the user. Alternatively, the release approval / disapproval determination unit 80 performs this determination by comparing the parallel development program stored in the production storage area 92 and reflecting the change according to the second development theme with the first changed program. Also good. If it is reflected, the release approval / disapproval determination unit 80 determines that the catch-up for the second development theme has been completed.

  More specifically, regarding (ii), the release approval / disapproval determination unit 80 determines whether the concurrent development program is in the case where the extracted status ID is “S1”, that is, when neither the release nor the release application has been made by the second development theme. 2 Judge that it is not necessary to keep up with the development theme.

  When it is determined in the release approval / disapproval determination unit 80 that the parallel development program may be released, the determination result output unit 71 reports the catch-up status of the parallel development program as a document from a predetermined printer via the input / output interface unit 10. Output (S450). This document may be used as a reference for catch-up confirmation at release meetings.

  If the release approval / disapproval determination unit 80 determines that the parallel development program may be released, and the release approval reception unit 48 receives the release approval, the overwriting unit 60 performs the actual storage by the first changed program. The parallel development program stored in the area 92 is overwritten (S452).

  FIG. 12 is a representative screen diagram of the first notification screen 500. The first notification screen 500 includes a parallel development management object ID 502 and a first development theme ID 504 in the form of text. The second notification screen has a similar configuration.

  FIG. 13 is a representative screen diagram of the inquiry information input screen 506. The inquiry information input screen 506 includes a user ID input area 510, a development theme ID input area 512, an input area 514 for other information, an execution button 516, and a return button 518. The screen information for displaying the inquiry information input screen 506 on the display of the user terminal indicates an error if neither the user ID input area 510 nor the development theme ID input area 512 is input when the execution button 516 is pressed. Configured to return.

  FIG. 14 is a representative screen diagram of the third notification screen 508. The third notification screen 508 includes the parallel development management target ID 520, the catch-up necessity determination result 522 in the catch-up necessity determination unit 76, the own development theme ID 524, the own user ID 526, and the development theme of the partner of the parallel development. The ID 528 and the counterpart user ID 530 are displayed in a table format.

The operation of the parallel development management apparatus 100 having the above configuration will be described.
For example, when a long-term development theme for performance improvement is already set for an application, a bug is found in the application. Then, a new short-term development theme is set to fix the bug. In such a situation, a program having the same program or a dependency relationship between the long-term development theme and the short-term development theme may be designated as a correction target. When such a program enters a parallel development state between a long-term development theme and a short-term development theme, the parallel development management device 100 responds to login, program designation, or inquiry request. Notify users of the status of parallel development, including the need for catch-up.

  Assume that a program in a state of parallel development by two development themes is released by one development theme before the other development theme. If one development theme is released without one development theme catching up with the other development theme, the change according to the other development theme disappears. As a result, for example, a failure after the release such as the function released last time may not work.

  On the other hand, according to the parallel development management apparatus 100 according to the present embodiment, the status of the parallel development including the necessity of catching up is notified to the user of the development theme specifying the program related to the parallel development. Therefore, it is possible to alert the user by notifying the user that the program is in the state of parallel development, the partner of parallel development, the necessity of catching up, and the like. The user can execute catch-up as appropriate based on the notification content. As a result, it is possible to reduce the possibility of a failure occurring after release.

  Further, in the parallel development management apparatus 100 according to the present embodiment, when a program specified by an existing development theme is in a state of parallel development afterwards, the information of the program and the development theme of the partner of the parallel development This information is sent to the development theme notification destination. Therefore, a developer engaged in a certain development theme can know that the program is in the state of parallel development and the partner of parallel development.

  For a program that is in the state of parallel development by multiple (for example, two) development themes, the release is approved after the application for one development theme is applied, and it usually takes several hours to several days to complete the release. There is a time lag. If the release of the program by the other development theme is completed during this time, the change according to the other development theme may disappear due to the completion of the release by the one development theme.

  Therefore, in the parallel development management apparatus 100 according to the present embodiment, when a program that has been applied for release under a certain development theme is under application for release under another development theme, the release approval / rejection determination unit 80 releases the program. Therefore, the release of the program by a certain development theme is restricted. That is, other overwrites on the program are restricted until the release approval / disapproval determination unit 80 determines that the program may be released until the overwriting unit 60 executes the corresponding overwriting. As a result, the possibility of the disappearance of the change due to the overwrite during the release application as described above is reduced.

  In the above-described embodiment, examples of the storage device 90 are a hard disk and a memory. Based on the description in this specification, each unit is realized by a CPU (not shown), an installed application program module, a system program module, a memory that temporarily stores the contents of data read from the hard disk, and the like. It is understood by those skilled in the art who have touched this specification that they can do this.

  The configuration and operation of the parallel development management apparatus 100 according to the embodiment have been described above. This embodiment is an exemplification, and it is understood by those skilled in the art that various modifications can be made to each component and combination of processes, and such modifications are within the scope of the present invention.

  In the embodiment, a program having a dependency relationship with a program specified based on the dependency relationship in which the dependency relationship reference unit 28 is registered is registered in the development theme management table 304, and the reading unit 30 reads the specified program and Although the case where a program having a dependency relationship with the program is transmitted to the development environment server 110 has been described, the present invention is not limited to this. For example, the processing based on the dependency relationship may be performed at another stage such as a check-in stage.

  In the embodiment, the catch-up necessity determination unit 76, when the overwriting unit 60 overwrites the parallel development program stored in the production storage area 92 by the second changed program prior to the first changed program, Although the case where it was determined that one development theme needs to catch up with the second development theme has been described, the present invention is not limited to this.

  For example, the catch-up necessity determination unit, when the overwriting unit 60 is scheduled to overwrite the parallel development program stored in the production storage area 92 by the second changed program before the first changed program, It may be determined that the first development theme needs to catch up with the second development theme.

  In particular, the catch-up necessity determination unit refers to the development theme management table 304, and the planned release date corresponding to the first development theme ID for the parallel development program is later than the planned release date corresponding to the second development theme ID. If it is, it may be determined that the first development theme needs to catch up with the second development theme. In this case, more detailed notification is possible.

  In the embodiment, the case where a date is used as a unit of time such as a start date, an end date, and a release application date has been described. However, the present invention is not limited to this, and other units of time may be used.

  In the embodiment, the case has been described in which the development environment server 110, the test environment server 112, and the production gateway 114 are separate bodies. However, the present invention is not limited to this, and may be realized by, for example, one server.

The notification unit 70 may accumulate information to be notified to the user that is generated while the user is logged off, and notify the user of the information accumulated when the user logs in.
In this case, the notification unit 70 monitors the parallel development management table 302, and if there is a change in the status ID, the date and time of the change and the content of the change are associated with each other and registered in a not-shown notification content holding unit (not shown). To do. When the user logs in to the parallel development management apparatus 100, the notification unit 70 extracts information about the logged-in user from information held in the login notification content holding unit. The notification unit 70 generates screen information for displaying the fourth notification screen 532 including the extracted information on the display of the user terminal. The notification unit 70 transmits the screen information to the user terminal of the user who has logged in via the input / output interface unit 10.

FIG. 15 is a representative screen diagram of the fourth notification screen 532. The fourth notification screen 532 displays a notification date and time 534, a message ID 536, and a message 538 indicating the status change content in a table format.
In this case, the user can grasp the status and history of parallel development at the time of login.

  2 program development system, 10 input / output interface unit, 20 reception unit, 30 reading unit, 40 test / release management unit, 50 production environment distribution unit, 60 overwriting unit, 70 notification unit, 90 storage device, 92 production system storage area, 94 development storage area, 96 management storage area, 100 parallel development management device, 108 network, 110 development environment server, 112 test environment server, 114 production gateway, 116 production environment server.

Claims (4)

A first storage area for storing a computer program;
A second storage area for storing information about the dependency relationship between the computer programs, indicating that when one computer program is changed, the other computer program is necessarily changed;
A change target designation receiving unit that accepts designation of a computer program to be changed for each development theme;
A dependency reference unit that refers to the second storage area and extracts a computer program that is dependent on the specified computer program;
A reading unit that reads the designated computer program and the computer program having a dependency relationship from the first storage area;
An overwriting unit for overwriting the computer program stored in the first storage area by the changed computer program, when a change according to the theme is made to the computer program read by the reading unit;
A notification unit that notifies predetermined information to a notification destination associated with a theme,
The reading unit reads one computer program as a first computer program from the first storage area for the first theme, and also reads the one computer program for the second theme as a second computer program. As read from the first storage area,
When the overwriting unit overwrites the one computer program stored in the first storage area by a second computer program prior to the first computer program, the notifying unit overwrites the information of the one computer program and Notify the second theme information to the notification destination associated with the first theme,
If the overwriting unit is to overwrite the one computer program stored in the first storage area by a second computer program prior to the first computer program, the notifying unit A parallel development management apparatus characterized by notifying information on the computer program and information on the second theme to a notification destination associated with the first theme. A first storage area for storing a computer program;
A second storage area for storing information about the dependency relationship between the computer programs, indicating that when one computer program is changed, the other computer program is necessarily changed;
A change target designation receiving unit that accepts designation of a computer program to be changed for each development theme;
A dependency reference unit that refers to the second storage area and extracts a computer program that is dependent on the specified computer program;
A reading unit that reads the designated computer program and the computer program having a dependency relationship from the first storage area;
An overwriting unit for overwriting the computer program stored in the first storage area by the changed computer program, when a change according to the theme is made to the computer program read by the reading unit;
A notification unit that notifies predetermined information to a notification destination associated with a theme,
The reading unit reads one computer program as a first computer program from the first storage area for the first theme, and also reads the one computer program for the second theme as a second computer program. As read from the first storage area,
When the overwriting unit overwrites the one computer program stored in the first storage area by a second computer program prior to the first computer program, the notifying unit overwrites the information of the one computer program and Notify the second theme information to the notification destination associated with the first theme,
When the receiving unit receives the specification of the one computer program for the second theme after the receiving unit receives the specification of the one computer program for the first theme, the notification unit receives information on the one computer program and Notify the second theme information to the notification destination associated with the first theme,
If the overwriting unit is to overwrite the one computer program stored in the first storage area by a second computer program prior to the first computer program, the notifying unit A parallel development management apparatus characterized by notifying information on the computer program and information on the second theme to a notification destination associated with the first theme. When the overwriting unit overwrites the one computer program stored in the first storage area by a second computer program prior to the first computer program, the second computer program A determination unit for determining whether a change according to the theme of 2 is reflected in the first computer program;
The overwriting unit overwrites the one computer program stored in the first storage area by the first computer program when it is determined to be reflected in the determination unit,
Until it is overwritten by the first computer program that the overwriting unit overwrites the one computer program stored in the first storage area after it is determined that it is reflected in the determination unit. 3. The parallel development management apparatus according to claim 1, wherein other overwriting is restricted. The parallel development management apparatus according to claim 3 , wherein, when it is determined that the notification unit is reflected in the determination unit, the notification unit outputs that effect.

Images