Program development support system and program development support method

Abstract

In a program development support system having an automatic execution processing server, when the automatic execution processing server receives a submission completion notification indicating that source code has been registered, it obtains submission information including source code information and document information, extracts the document identifier from the submission information, obtains attribute information of the document based on the extracted document identifier, saves execution object information corresponding to the source code to be automatically executed in an automatic execution queue in a predetermined order, changes the order of the execution object information in the automatic execution queue based on the obtained attribute information of the document, obtains source code and test instances that are objects of automatic execution, and performs automatic execution using the source code and test instances based on the order of the execution object information changed by the automatic execution processing change unit.

Description

[0001] This application claims the priority of Japanese application No. 2019-237180 filed on December 26, 2019, the contents of which are incorporated herein by reference. Technical Field

[0002] The present invention relates to a program development support system and a program development support method. Background Art

[0003] As a method for developing programs, there is a method called continuous integration, which is known as one of the best practices of agile development. In program development using continuous integration, when the produced source code is registered (submitted) to the version management system that manages the source code, operations such as source code construction and testing are automatically performed. As a result, defect detection can be performed at an earlier stage, thereby achieving efficient and high-quality development. As a tool for realizing such continuous integration, for example, Jenkins (Non-Patent Document 1) is known.

[0004] In addition, in program development, a development method is known as ticket-driven development, which divides work into tasks and assigns them to tickets of BTS (Bug Tracking System) for management. As a tool for managing such tickets, for example, Redmine (Non-Patent Document 2) is known. Since the method of Non-Patent Document 2 has a high affinity with agile development, it is often combined with the above-mentioned continuous integration for practice.

[0005] As background technology in the technical field related to the above-mentioned technology, there is known patent document 1. Patent document 1 describes a test instance selection method and a selection system for selecting test instances in a manner that can efficiently implement tests in continuous integration, and describes a scheme for selecting test instances to be executed based on the implementation importance and implementation time threshold transmitted from a continuous integration tool, and the importance and actual execution time of the test instances stored in a repository.

[0006] Prior art literature

[0007] Patent Document 1: Japanese Patent Application Publication No. 2010-134643

[0008] Non-patent literature 1: Smart, John Ferguson (author) and Ryuji Tamagawa (translator), "Jenkins", published by O'Reilly Japan (Japanese: Olay Japan), February 22, 2012

[0009] Non-patent document 2: Andriy Lesyuk, “Mastering Redmine”, Packtpublishing, January 25, 2013 Summary of the invention

[0010] The continuous integration tool described in the above-mentioned Non-Patent Document 1 and the like and the receipt management tool described in the above-mentioned Non-Patent Document 2 and the like are sometimes combined for practice to provide a structure for collaboration.

[0011] However, since it is only a simple collaboration of switching from the document display screen of the document management tool to the screen of the result of automatic execution by the continuous integration tool, if automatic execution is desired based on the content written in the document, manual settings must be made in advance.

[0012] For example, when more submissions are made, a waiting queue for automatic execution is generated, so it is necessary to manually set the settings in advance to avoid delaying the processing of documents with higher priority. In addition, efficiency can be improved by changing the scope and frequency of automatic execution according to the content of the job, but it is necessary to prepare multiple settings of the scope and frequency that take into account all situations.

[0013] Patent Document 1 describes a scheme for selecting a test case to be executed based on the thresholds of the importance and execution time of the execution transmitted from the continuous integration tool and the importance and actual execution time of the test cases stored in the repository.

[0014] This allows the selection of test cases to be performed efficiently in continuous integration. However, since the judgment is based on the importance of the test case, construction, static analysis (coding check), and review other than testing are not considered.

[0015] In addition, in Patent Document 1, since the attribute to be determined is only the importance of the test instance, it is not possible to give priority to cases with the same importance. Furthermore, attributes such as date, person in charge, and status, which are attributes of the document, are not considered. Therefore, with regard to giving priority to processes other than testing and giving priority to cases with the same importance, it is necessary to prepare multiple settings that take into account all situations based on the attribute information of the document.

[0016] Therefore, the present invention provides a program development support system and a program development support method capable of efficiently executing the automatic execution process by automatically changing the content of the automatic execution process according to the attributes of the document.

[0017] The present invention is a program development support system, which has an automatic execution processing server, which has a processor, a memory and a communication interface, wherein the automatic execution processing server has: a submission information acquisition unit, when receiving a submission completion notification indicating that source code has been registered, to acquire submission information containing information of the source code and information of a receipt corresponding to the source code; a collaboration unit, which extracts a receipt identifier corresponding to the submission completion notification from the submission information; an attribute information acquisition unit, which acquires attribute information of the receipt based on the extracted receipt identifier; an automatic execution queue, which stores the source code pairs to be automatically executed in a predetermined order. corresponding execution object information; an automatic execution processing change unit, which generates information specifying source code from the obtained submission information as execution object information and puts it into the automatic execution queue, and changes the order of execution object information in the automatic execution queue based on the obtained attribute information of the document; an object deliverable acquisition unit, which acquires source code and test instances that become objects of the automatic execution processing; an automatic execution processing unit, which performs automatic execution processing using the source code and test instances acquired by the object deliverable acquisition unit based on the order of execution object information changed by the automatic execution processing change unit; and a notification unit, which notifies the result of execution by the automatic execution processing unit.

[0018] According to the present invention, the automatically executed process can be automatically changed according to the attribute information of the document, and the automatically executed process in the continuous integration can be efficiently implemented.

[0019] Other problems, structures, and effects than those described above will become apparent from the following description of the embodiments. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1A The first embodiment of the present invention is shown, and is a block diagram showing an example of the configuration of a program development support system.

[0021] Figure 1B The first embodiment of the present invention is shown, and is a block diagram showing an example of the structure of an automatic execution processing server.

[0022] Figure 2 The first embodiment of the present invention is shown in the figure, which shows an example of a document.

[0023] Figure 3 The first embodiment of the present invention is shown, and is a flowchart showing an example of processing performed by the program development support system.

[0024] Figure 4 The first embodiment of the present invention is shown, and is a flowchart showing an example of processing performed by the program development support system.

[0025] Figure 5The first embodiment of the present invention is shown, and is a flowchart showing an example of processing performed by the program development support system.

[0026] Figure 6 The first embodiment of the present invention is shown and is a diagram for explaining an example of a use case.

[0027] Figure 7 The second embodiment of the present invention is shown and is a diagram for explaining an example of a use case. DETAILED DESCRIPTION

[0028] Hereinafter, embodiments of the present invention will be described based on the drawings.

[0029] Example 1

[0030] This embodiment is an embodiment of the program development support system and program development support method of the present invention. Figures 1A to 6 This embodiment is described.

[0031] Figure 1A : is a block diagram showing the structure of the program development support system in this embodiment. Figure 1B This is a block diagram showing an example of the structure of the automatic execution processing server. Figure 2 It is a diagram showing the recorded contents of the document in this embodiment. Figure 3 1 is a flowchart showing an overview of the processing procedure of the automatic execution processing system in this embodiment. Figure 4 Detailed description of the process of changing the queue order in this embodiment. Figure 5 Detailed procedure of automatic execution setting in this embodiment is shown in FIG. Figure 6 This is an example of a diagram for explaining a use case in which a plurality of persons in charge modify source code for one document in this embodiment.

[0032] exist Figure 1A In the figure, 100 is a version management server that manages source code and test instances (execution environment, etc.) corresponding to the source code in units of versions, 110 is a ticket management server that manages operations related to program production and contents related to defects as tickets, 120 is an automatic execution processing server that automatically executes operations related to program production such as source code construction and testing when source code is registered (submitted) to the version management server 100, and 300 is a development client that generates source code.

[0033] The program development support system in this embodiment includes the version management server 100 , the receipt management server 110 , the automatic execution processing server 120 , and the development client 300 .

[0034] Reference numeral 101 is a deliverable database storing source code and test cases managed by the version management server 100. Reference numeral 102 is a management unit for registering, searching, and managing the source code and test cases in the deliverable database 101. The version management server 100 in this embodiment is composed of the deliverable database 101 and the management unit 102.

[0035] In addition, 111 is a document database for storing the documents managed by the document management server 110. 112 is a management unit for registering, searching, and managing the documents in the document database 111. The document management server 110 in this embodiment is composed of the document database 111 and the management unit 112. In addition, the version management server 100 and the document management server 110 can also use existing tools that are commercially available or OSS (Open Source Software).

[0036] In addition, 121 is a submission information acquisition unit that acquires the submitted information from the version management server 100. 122 is a coordination unit that extracts the ID (or number) of the receipt corresponding to the submission from the submission information acquired by the submission information acquisition unit 121 and coordinates the version management server 100 with the receipt management server 110. 123 is an attribute information acquisition unit that acquires the attribute information of the receipt from the receipt management server 110 for the receipt of the extracted receipt ID.

[0037] Reference numeral 124 is an automatic execution process changing unit that changes the order of the execution target information stored in the automatic execution queue 127 based on the acquired document attribute information. Reference numeral 125 is a target deliverable acquisition unit that acquires source code and test cases to be automatically executed from the version control server 100.

[0038] In this embodiment, a process to be automatically executed is set as execution target information, and one or more execution target information is stored in the automatic execution queue 127. The execution target information includes information for specifying source code and test instance for automatic execution process. The automatic execution process changing unit 124 controls the execution order of the execution target information stored in the automatic execution queue 127. In addition, the execution target information is not limited to the information for specifying source code and test instance, and may also be the entity of source code and test instance.

[0039] Reference numeral 126 is an automatic execution processing unit that performs automatic execution processing using the source code and test case of the object acquired by the object deliverable acquisition unit 125 based on the processing order of the execution object information determined by the automatic execution processing change unit 124. In addition, the automatic execution processing unit 126 implements source code construction, testing based on test cases, and static analysis and review in the same manner as the conventional example. Reference numeral 127 is an automatic execution queue that manages one or more execution object information in a queue in a predetermined order. Reference numeral 128 is a notification unit that notifies relevant parties of the results of the execution by the automatic execution processing unit by email or the like.

[0040] The automatic execution processing server 120 in this embodiment includes a submission information acquisition unit 121 , a coordination unit 122 , an attribute information acquisition unit 123 , an automatic execution processing change unit 124 , a target delivery acquisition unit 125 , an automatic execution processing unit 126 , an automatic execution queue 127 , and a notification unit 128 .

[0041] Reference numeral 310 denotes a development tool that generates source code based on information received from an input device (not shown) operated by a developer, etc. Reference numeral 320 denotes a source storage unit that stores the generated source code and information (test cases, etc.) accompanying the source code.

[0042] The development client 300 in this embodiment includes these development tools 310 and a source storage unit 320 .

[0043] Figure 1B 1 is a block diagram showing an example of the structure of the automatic execution processing server 120. The automatic execution processing server 120 is a computer including a processor 11, a memory 12, a communication interface 13, an input / output device 14, and a storage device 15.

[0044] The input / output device 14 includes input devices such as a mouse, keyboard, or touch panel, and output devices such as a display. The communication interface 13 communicates with the version management server 100 , the receipt management server 110 , and the development client 300 via the network 80 .

[0045] The submission information acquisition unit 121, the coordination unit 122, the attribute information acquisition unit 123, the automatic execution process change unit 124, the target delivery acquisition unit 125, the automatic execution processing unit 126, and the notification unit 128 are loaded into the memory 12 and executed by the processor 11. In addition, the automatic execution queue 127 managed by the automatic execution processing unit 126 is set in the memory 12.

[0046] The processor 11 performs processing according to the programs of each functional unit, thereby operating as a functional unit that provides a predetermined function. For example, the processor 11 performs processing according to the automatic execution processing program, thereby functioning as the automatic execution processing unit 126. The same applies to other programs. In addition, the processor 11 also operates as a functional unit that provides the functions of each of the multiple processes executed by each program. Computers and computer systems are devices and systems that include these functional units.

[0047] Figure 2 This is an example of a screen display of a receipt managed by the receipt management server 110, showing the attributes of the receipt.

[0048] exist Figure 2 201 is a type attribute indicating the type of the document such as "work" or "defect". 202 is a title attribute indicating the title of the document. 203 is a content description attribute indicating "work details" or "defect details" of the document.

[0049] 204 is a person-in-charge attribute indicating the person-in-charge of the document. 205 is a status attribute indicating the status and state of the document such as "new", "working", and "work completed". 206 is a priority attribute indicating the priority of the processing corresponding to the document such as work and defect.

[0050] 207 is a date attribute indicating the date corresponding to the operation or defect. 208 is a parent ticket attribute indicating information of the parent ticket, which is the hierarchical ticket of the upper level of the ticket. 209 is a ticket attribute indicating a ticket that has a relationship in terms of operation sequence, such as that the operation cannot be started unless the status attribute of another ticket becomes "finished", or a relationship such as that the contents are repeated.

[0051] 210 is a critical path attribute, which indicates whether the document is a sequence of operations (critical path) in the process management until all processes are completed, and the operation time cannot be shortened even if the operations are performed in parallel. 211 is a change history attribute indicating a report on the status of the operation content shown in the document and a change history of the document's attributes.

[0052] In addition, Figure 2 In the embodiment, these attributes are clearly recorded on the document screen, but they may not be clearly recorded on the document screen. For example, the critical path attribute 210 may also be displayed as attribute data of the document.

[0053] Here, using Figure 1 and Figure 3First, for a receipt issued by the receipt management server 110, a person in charge of using the development client 300 creates a program (creates or modifies source code) according to the contents of the issued receipt.

[0054] After that, the person in charge registers (submits) the source code using the version management server 100. At this time, the document number (ID) of the document corresponding to the submission log is recorded, and it is clearly recorded which document the source code is for. When the submission of the source code is completed, the version management server 100 sends a notification indicating the completion of the submission (submission completion notification) to the automatic execution processing server 120.

[0055] The automatic execution processing server 120 receives the submission completion notification and obtains the submission information (submission information) from the version management server 100 through the submission information acquisition unit 121 (step S301). Here, the submission information in this embodiment refers to the file name (or identifier) ​​of the submitted source code, the submission log (identifier of the diagram), and the information when the test case is submitted.

[0056] The linking unit 122 acquires the slip information such as the corresponding slip number (or slip ID) included in the submission information acquired by the submission information acquisition unit 121, and causes the slip management server 110 to select the slip corresponding to the submission (step S302).

[0057] After that, the attribute information acquisition unit 123 acquires the document attribute information of the corresponding document from the document management server 110 (step S303). Figure 2 The document attributes (201-210) are shown.

[0058] The queue order of the automatic execution queue 127 is changed by the automatic execution process changing unit 124 based on the acquired document attribute information (step S304).

[0059] The automatic execution process changing unit 124 first generates information specifying source code and test cases from the acquired submission information as execution target information, and puts it into the automatic execution queue 127. Then, the automatic execution process changing unit 124 changes or sets the order of the execution target information based on the acquired document attribute information (step S305).

[0060] The automatic execution processing unit 126 uses the date attribute 207 in the document attribute information obtained in the above step S303 to determine whether the automatic execution of the execution object information is completed within the date based on the actual time of the past automatic execution processing (step S306). When the automatic execution is completed within the date, the automatic processing of the execution object information in the automatic execution queue 127 is executed in the order set in the step S305 (step S307).

[0061] Furthermore, the automatic execution processing unit 126 saves the actual data of the execution time for each combination of the source code and the test case (execution object information) to the storage device 15, and determines whether the automatic execution of the execution object information can be completed before the date attribute 207 based on the actual data of the past execution time. In addition, regarding the actual data of the past execution time, pre-set statistical information such as the maximum value and average value of the execution time can be used.

[0062] On the other hand, for the execution target information determined by the automatic execution processing unit 126 to be not completed within the date, warning information including a message indicating that the execution target information is not completed before the date is set (step S308), and the automatic processing is not executed. After that, the notification unit 128 notifies the result of the execution in step S307 or the warning set in step S308 to a preset destination (for example, the development client 300) by means of notification such as an email or a message (step S309), and a series of processing is terminated.

[0063] Next, use Figure 4 The flowchart is used to illustrate Figure 3 The detailed procedure of the queue order change process (step S304) in the flowchart shown in FIG. The queue order change process is executed by the automatic execution process change unit 124. This process is performed on the information of the document corresponding to the source code corresponding to the submission completion notice.

[0064] The automatic execution process change unit 124 determines whether the priority attribute 206 in the document attribute information obtained by the document attribute information acquisition (step S303) is a high priority such as "large (or high)" (step S401). If the value of the priority attribute 206 is greater than a predetermined threshold value Thp, the automatic execution process change unit 124 determines that the priority is high and proceeds to step S404.

[0065] On the other hand, if the priority attribute 206 is not high, the automatic execution process change unit 124 determines whether the number of days until the date is within a predetermined threshold value Thd for the date attribute 207 of the document attribute information (step S402). Here, the threshold value Thd is set to a predetermined setting value.

[0066] In step S402 , if the number of days until the date attribute 207 exceeds the threshold Thd, the automatic execution process changing unit 124 determines that there is a margin until the date and moves to step S403 . In step S403 , the automatic execution process changing unit 124 determines whether a flag is set for the critical path attribute 210 .

[0067] If the flag is not set, the automatic execution process change unit 124 determines that the document is not a critical path document, and is a document that does not need to change the order of the queue in the end, and ends a series of processes.

[0068] In step S401, when the priority attribute 206 is a high priority above the threshold Thp, or in step S402, when the number of days remaining until the date is within the threshold Thd, that is, when it is judged that there is no time before the date, or in step S403, when it is judged to be a document on the critical path, the automatic execution processing change unit 124 determines that it is necessary to change the order of the execution object information in the automatic execution queue 127, and enters step S404.

[0069] The automatic execution process changing unit 124 sets the first sort key in the order of "priority" from high to low (step S404), sets the second sort key in the order of the remaining schedule until the "date" from short to long (step S405), and sets the third sort key to whether it is a "critical path" (step S406). Then, the automatic execution process changing unit 124 sorts the execution object information in the automatic execution queue 127 using the first to third sort keys, changes the order of the execution object information in the automatic execution queue 127 (step S407), and ends a series of processing.

[0070] That is, the automatic execution process change unit 124 determines whether to change the execution order of the execution object information based on the attribute information of the document corresponding to the source code of the submission completion notice. In the case of change, the execution object information is sorted in a predetermined order based on the document attribute information. In addition, in the above embodiment, an example of changing the execution order of the execution object information using priority, date and critical path is shown, but it is not limited to this. As for the elements for sorting the execution object information, at least one element can be selected from the document attribute information.

[0071] Next, use Figure 5 The flowchart is used to illustrate Figure 3 The detailed process of the automatic execution setting (step S305) in the flowchart shown.

[0072] The automatic execution setting is executed by the automatic execution process changing unit 124. The automatic execution process changing unit 124 uses the parent document attribute 208 in the document attribute information acquired by acquiring the document attribute information (step S303) to determine whether the submission is to the parent document (step S501).

[0073] If the submission is not to the parent document, the automatic execution process change unit 124 extracts the responsible person of the document from the responsible person attribute 204. Next, the automatic execution process change unit 124 extracts the document corresponding to the responsible person attribute 204 from the document management server 110 and obtains information on the number of unfinished responsible documents and the number of responsible defective documents in the past. In addition, the automatic execution process change unit 124 obtains information on the number of submissions of the responsible person from the version management server 100, and determines which value is greater than a predetermined threshold value Thc, or obtains the change information of the responsible person from the history attribute 211, and determines whether the difference between the change date and time of the responsible person and the current date and time is less than a predetermined threshold value Thc (step S502).

[0074] When the number of documents or submissions is less than the threshold value Thc and the person in charge has not just changed, the automatic execution process change unit 124 determines whether the status is "working" or "working completed" based on the information of the status attribute 205 (step S503).

[0075] When the status is "in progress", the automatic execution process change unit 124 sets the setting that the content of the automatic execution process is efficiently performed (step S504), and ends a series of processes. Here, the setting that the automatic execution process is efficiently performed means, for example, setting that only the files of the target source code submitted for build and test execution are set, no review is required, and no check is performed on whether the horizontally expanded correction content of the same defect is included, and no email notification of the automatic execution result is sent to the development person in charge.

[0076] When it is determined in the above step S501 that it is a submission to the parent document, the automatic execution processing change unit 124 can determine that it is an important submission in the operation process to merge the contents of the child document into the parent document, and therefore sets the setting in which the contents of the automatic execution processing are performed with emphasis (step S505), and ends a series of processing.

[0077] Similarly, in step S502, when the number of documents or the number of submissions is greater than the threshold value Thc or when the person in charge has just changed, the automatic execution processing change unit 124 determines that it is necessary to focus on testing, etc., sets the setting for automatic execution processing to be focused (step S505), and ends a series of processing.

[0078] Then, when the status is "job completed" in step S503, the automatic execution process changing unit 124 sets the setting so that the automatic execution process is performed intensively (step S505), and ends a series of processes.

[0079] Here, the settings where automatic execution processing is focused on are, for example, settings such as the following: the build and test execution objects are set to the entire source code of the target product, and a review is required, and a check is also made to see whether the horizontal expansion correction content of the same defect is included, and the automatic execution results are notified to the development responsible person by email.

[0080] pass Figure 4 as well as Figure 5 In the process shown, the automatic execution process changing unit 124 automatically changes the automatic execution process according to the attribute of the document corresponding to the submission completion notice, thereby enabling the automatic execution process to be efficiently implemented according to necessity.

[0081] In addition, the above example shows that the automatic execution process change unit 124 determines the content of the automatic execution process based on the parent document attribute 208, the person in charge attribute 204, and the history attribute 211, but the present invention is not limited to this. The automatic execution process change unit 124 may also determine the content of the automatic execution process based on at least one attribute in the document attribute information.

[0082] Next, use Figure 6 In this embodiment, a case where multiple persons in charge modify the source code for one document is described. Figure 6 The following is a diagram showing an example of its use.

[0083] exist Figure 6 In the use example shown, two persons, A and B, use the development client 300 to correct defects in a document 601 whose type attribute 201 is "defect". In addition, A is a person who has a small number of uncompleted documents in his / her charge, a small number of defective documents in his / her charge in the past, and a small number of submissions. Similarly to A, B is a person who has a small number of uncompleted documents in his / her charge, a small number of defective documents in his / her charge in the past, and a small number of submissions.

[0084] A defective ticket 601 is input to the ticket management server 110 by a person who finds a defect. As a person responsible for the defect, a responsible person A is initially assigned. The responsible person A investigates the cause based on the contents of the ticket 601 and uses the development client 300 to correct the defect.

[0085] At this time, the status attribute of the receipt 601 is changed to "in process" (or "under revision") by the receipt management server 110. Figure 6In the example, only the type attribute 201, the person in charge attribute 204, and the status attribute 205 are recorded as the attributes of the document 601, but Figure 2 Other properties shown.

[0086] exist Figure 6 In the example of use shown, the defect to be corrected covers a wide range, and the correction is also carried out in multiple times within the scope of the person in charge A. Therefore, the submission of the corrected source code is also divided into multiple times (602 to 604).

[0087] Person in charge A uses the development client 300 to make the initial revision and submits the revised source code to the version management server 100 (submission 602). The automatic execution processing server 120 executes the submission 602 (the receipt of the submission completion notification, the same applies below) as an opportunity. Figures 3 to 5 The following is only an explanation of the Figure 6 The processing part involved in the use case described in .

[0088] In the process triggered by the submission of submission 602, in the automatic execution setting (step S305), Figure 5 Since it is not a commit to the parent commit in the process, the judgment in step S501 becomes "No".

[0089] In the step of determining the responsible person and historical information in step S502, in this use case, the number of unfinished responsible documents, the number of defective responsible documents in the past, and the number of submissions of responsible person A are small and within the threshold value Thc, so it is determined to be "No".

[0090] Next, since the state attribute 205 is "in progress" in step S503, the automatic execution processing server 120 moves to step S504 and sets the efficient execution. Through the subsequent processing, the automatic execution processing is executed in the submission 602 with the efficient setting.

[0091] exist Figure 3 In step S309, no email notification is sent to the developer. Figure 6 In the process, the person in charge A uses the development client 300 to make the next revision and submits the revised source code to the version management server 100 (submit 603). With the submission of the submission 603 as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5 The processing shown is the same as the submission 602 described above.

[0092] Next, the person in charge A uses the development client 300 to make final revisions as part of his / her responsibility, and submits the revised source code to the version management server 100 (submit 604 ).

[0093] The automatic execution processing server 120 executes the submission 604 as a trigger. Figures 3 to 5 The processing shown is the same flow as the submit 602. As the person in charge A has completed the last revision, the person in charge of the slip 601 is set to the person in charge B (slip 601a) from the development client 300.

[0094] Person in charge B investigates the cause based on the contents of the receipt 601a and corrects the defect using the development client 300. Figure 6 In the usage example shown, the defect correction site covers a wide range, and the correction is carried out in multiple times within the range of the person in charge B.

[0095] Therefore, submission of the revised source code is also divided into multiple times like the person in charge A. Person in charge B first makes the first revision and submits the revised source code to the version control server 100 using the development client 300 (submit 605 ).

[0096] The automatic execution processing server 120 executes the submission 605 as a trigger. Figures 3 to 5 The following is only an explanation of the Figure 6 The processing part involved in the use case described in .

[0097] In the process triggered by the submission of submission 605, in the automatic execution setting (step S305), Figure 5 The processing is not a submission to the parent, so the judgment in step S501 is "No".

[0098] In the step of determining the responsible person and historical information in step S502, in this use case, the number of unfinished responsible documents, the number of defective responsible documents in the past, and the number of submissions of responsible person B are small and within the threshold value Thc, so the automatic execution processing server 120 determines as "no".

[0099] In step S503, the status attribute is "in progress", so the automatic execution processing server 120 transfers to step S504 and sets the efficient execution. Through the subsequent processing, the automatic execution processing is executed with the efficient setting in submit 602. Figure 3 In step S309, no email notification is sent to the development person in charge.

[0100] Next, the person in charge B makes the next revision and submits the revised source code to the version management server 100 using the development client 300 (submit 606). With the submission of the submission 606 as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5 The processing shown is the same flow as the submission 605 described above.

[0101] Next, the person in charge B performs final corrections using the development client 300. At this time, before submission, the person in charge B changes the status of the receipt to "work completed" using the development client 300 (receipt 601b).

[0102] Person in charge B uses the development client 300 to submit the revised source code to the version management server 100 (submit 607) for the document 601b. The automatic execution processing server 120 executes Figures 3 to 5 The following is only an explanation of the Figure 6 The processing part involved in the use case described in .

[0103] In the process triggered by the submission of submission 605, in the automatic execution setting (step S305), Figure 5 In the process of , it is not a submission to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "No". In the judgment step of the person in charge and the historical information in step S502, in this use case, the number of unfinished documents in charge, the number of defective documents in charge in the past, and the number of submissions of person in charge B are small and within the threshold value Thc, so the judgment of the automatic execution processing server 120 becomes "No".

[0104] In step S503, the status attribute is "job completed", so the automatic execution processing server 120 transfers to step S505 and sets the priority execution. Through the subsequent processing, the automatic execution processing is executed with the priority setting in submit 607. Figure 3 In step S309, a notification is made to the person in charge of development via e-mail or the like.

[0105] Thus, efficient automatic execution is performed based on the attribute information of the document in the submission as a job, and focused automatic execution is performed as the final job in the submission as the completion of the job, so that efficient automatic execution processing can be performed as a whole.

[0106] As described above, the automatic execution process server 120 can automatically change the content of the automatic execution process according to the attribute of the document, and can efficiently implement the automatic execution process in continuous integration.

[0107] In the first embodiment, the version control server 100 and the receipt management server 110 are independent from each other, but the present invention is not limited thereto, and the version control server 100 and the receipt management server 110 may be formed by a single computer.

[0108] Example 2

[0109] Embodiment 2 is an embodiment in which, in the program development support system and the program development support method shown in Embodiment 1, one function is divided into a plurality of sub-functions and source codes are created by a plurality of persons in charge.

[0110] In addition, the block diagram, document description, and flow chart shown in Example 1 are similar to those in FIG. Figures 2 to 5 The same as shown, so the respective descriptions are omitted. Figure 7 The following is a description of a usage example in this embodiment. Figure 7 This is a diagram for explaining an example of use of the second embodiment.

[0111] exist Figure 7 In the illustrated use case, a parent document 700 represents a function, and a plurality of child documents 710, 720, and 730 of the parent document 700 are documents for making sub-functions A, B, and C, respectively. In addition, a person in charge A, B, and C are assigned to the child documents 710, 720, and 730, respectively.

[0112] In addition, whether it is a parent document 700 or a child document 710, 720, 730 is determined based on the parent document attribute 208. In addition, in this embodiment, all child documents are assumed to be in the "working" state until the parent document state becomes "working completed".

[0113] Here, similarly to the first embodiment, the following is the case: the person in charge A, person in charge B, and person in charge C are persons in charge of which the number of uncompleted documents is small, the number of defective documents they have been in charge of in the past is small, and the number of submissions is small.

[0114] Parent document 700 and child documents 710, 720, and 730 are input to the document management server 110. At this time, the person in charge attribute 204 of child document 710 is set to person in charge A, the person in charge attribute 204 of child document 720 is set to person in charge B, and the person in charge attribute 204 of child document 730 is set to person in charge C.

[0115] Person in charge A creates a program for sub-function A based on the contents of receipt 710. Figure 7 The use example shown is a case where the creation of sub-functions covers a wide range, and the program creation is carried out in multiple times even within the scope of the person in charge A.

[0116] Therefore, submission of the created source code is also divided into multiple times. Person in charge A first creates the initial source code using the development client 300 and submits the created source code to the version management server 100 (submit 711).

[0117] The automatic execution processing server 120 executes the submission 711 as a trigger. Figures 3 to 5 The following is only an explanation of the Figure 7 The processing part involved in the use case described in .

[0118] In the process triggered by the submission of submission 711, in the automatic execution setting (step S305), Figure 5 The processing is not a submission to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "No".

[0119] In the step of determining the responsible person and historical information in step S502, in this use case, the number of unfinished responsible documents, the number of defective responsible documents in the past, and the number of submissions of responsible person B are small and within the threshold value Thc, so the automatic execution processing server 120 determines to be "No".

[0120] Since the status attribute is "in progress" in step S503, the automatic execution processing server 120 moves to step S504 and sets the efficient execution. Through the subsequent processing, the automatic execution processing is executed with the efficient setting in submit 711. Figure 3 In step S309, no email notification is sent to the development person in charge.

[0121] Next, person in charge A creates the next function and submits the created source code to the version management server 100 using the development client 300 (submit 712). With the submission 712 being submitted as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5 The processing shown is the same as the above-mentioned submission 711. In this embodiment, it is assumed that the creation of the sub-function A is completed by submission 712.

[0122] Next, since the person in charge A has completed the creation of the sub-function A, he submits all the created source codes for the parent document 700 to the version control server 100 using the development client 300 (submit 713 ).

[0123] The automatic execution processing server 120 executes the submission 713 as a trigger. Figures 3 to 5 The following is only an explanation of the Figure 7 The processing part involved in the use case described in .

[0124] In the process triggered by the submission of submission 713, in the automatic execution setting (step S305), Figure 5 In the process of , the submission is submitted to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "yes" and transfers to step S505, which becomes the setting of key execution. Through the subsequent processing, the automatic execution processing is executed with the key setting in submission 713. Figure 3 In step S309, an email notification is sent to the development person in charge.

[0125] Person in charge B creates a program for sub-function B based on the contents of receipt 720. Figure 7 In the use example shown, the creation of sub-functions covers a wide range, and the program creation is also carried out in multiple times within the scope of the person in charge B. Therefore, the submission of the created source code is also divided into multiple times.

[0126] Person in charge B first creates the initial source code and submits the created source code to the version management server 100 using the development client 300 (submit 721). With the submission of the submission 721 as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5 The following is only an explanation of the Figure 7 The processing part involved in the use case described in .

[0127] In the process triggered by the submission of submission 721, in the automatic execution setting (step S305), Figure 5 In the process of , it is not a submission to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "No". In the step of judging the responsible person and historical information in step S502, in this use case, the number of unfinished responsible documents, the number of responsible defective documents in the past, and the number of submissions of responsible person B are small and within the threshold value Thc, so the automatic execution processing server 120 judges to be "No".

[0128] Since the status attribute is "in progress" in step S503, the automatic execution processing server 120 moves to step S504 and sets the efficient execution. Through the subsequent processing, the automatic execution processing is executed with the efficient setting in the submission 721. Figure 3 In step S309, no email notification is sent to the development person in charge.

[0129] Next, the person in charge B creates the next function and submits the created source code to the version management server 100 using the development client 300 (submit 722). With the submission of the submission 722 as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5The processing shown is the same as the above-mentioned submission 711. In this embodiment, it is assumed that the creation of the sub-function B is completed by submission 722.

[0130] Next, since the person in charge B has completed the creation of the sub-function B, he submits all the created source codes for the parent document 700 to the version control server 100 using the development client 300 (submit 723 ).

[0131] The automatic execution processing server 120 executes the submission 723 as a trigger. Figures 3 to 5 The following is only an explanation of the Figure 7 The processing part involved in the use case described in .

[0132] In the process triggered by the submission of submission 723, in the automatic execution setting (step S305), Figure 5 In the process of , the submission is submitted to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "yes" and transfers to step S505, which becomes the setting of key execution. Through the subsequent processing, the automatic execution processing is executed with the key setting in submission 723. Figure 3 In step S309, an email notification is sent to the development person in charge.

[0133] Person C creates a program for sub-function C based on the contents of receipt 730. Figure 7 In the use example shown, the creation of sub-functions covers a wide range, and the program creation is also carried out in multiple times within the scope of the person in charge C. Therefore, the submission of the created source code is also divided into multiple times.

[0134] Person in charge C first creates the initial source code and submits the created source code to the version management server 100 using the development client 300 (submit 731). With the submission of the submission 731 as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5 The following is only an explanation of the Figure 7 The processing part involved in the use case described in .

[0135] In the process triggered by the submission of submission 731, in the automatic execution setting (step S305), Figure 5 The processing is not a submission to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "No".

[0136] In the step of determining the responsible person and historical information in step S502, in this use case, the number of unfinished responsible documents, the number of defective responsible documents in the past, and the number of submissions of responsible person B are small and within the threshold value Thc, so the automatic execution processing server 120 determines to be "No".

[0137] Since the status attribute is "in progress" in step S503, the automatic execution processing server 120 moves to step S504 and sets the efficient execution. Through the subsequent processing, the automatic execution processing is executed with the efficient setting in the submission 731. Figure 3 In step S309, no email notification is sent to the development person in charge.

[0138] Next, the person in charge C creates the next function and submits the created source code to the version management server 100 using the development client 300 (submit 732). With the submission of the submission 732 as an opportunity, the automatic execution processing server 120 executes Figures 3 to 5 The processing shown is the same as the above-mentioned submission 731. In this embodiment, it is assumed that the creation of the sub-function C is completed by submission 732.

[0139] Next, since the person in charge C has created the sub-function C, he uses the development client 300 to submit all the created source codes for the parent document 700 to the version management server 100 (submit 733). Figures 3 to 5 The following is only an explanation of the Figure 7 The processing part involved in the use case described in .

[0140] In the process triggered by the submission of submission 733, in the automatic execution setting (step S305), Figure 5 In the process of , the submission is submitted to the parent, so the automatic execution processing server 120 sets the judgment of step S501 to "yes" and transfers to step S505, which becomes the setting of key execution. Through the subsequent processing, the automatic execution processing is executed with the key setting in submission 723. Figure 3 In step S309, an email notification is sent to the development person in charge.

[0141] As a result, in the submission of sub-function creation, efficient automatic execution is performed based on the attribute information of the document, and in the submission of the merged sub-function to the parent document, focused automatic execution is performed as the final operation, thereby enabling efficient automatic execution processing as a whole.

[0142] In addition, for Figure 7In the example of use described in the , it is also possible to use the branch function in the version management server 100 to set the in-job branch and the job completion branch instead of the document attribute as in the present embodiment, and change the automatic execution process for each branch. However, the number of branches corresponding to the number of responsible persons is required, and the number of responsible persons in large-scale program development also becomes large, so a large number of branches are required, and the management of branches becomes difficult. On the other hand, if the document attribute is used as in the present embodiment, it can be implemented even with one branch, so the management of branches becomes easy.

[0143] As described above, the automatic execution process server 120 can automatically change the content of the automatic execution process according to the attribute of the document, and can efficiently implement the automatic execution process in continuous integration.

[0144] <Conclusion>

[0145] As described above, the program development support system of the above-mentioned embodiment can be configured as follows.

[0146] A program development support system has an automatic execution processing server (120), the automatic execution processing server (120) has a processor (11), a memory (12) and a communication interface (13) as shown in FIG1, wherein the program development support system is characterized in that the automatic execution processing server (120) has: a submission information acquisition unit (121) that, when receiving a submission completion notification indicating that source code has been registered, acquires submission information including information about the source code and information about a receipt corresponding to the source code; a collaboration unit (122) that extracts a receipt identifier corresponding to the submission completion notification from the submission information; an attribute information acquisition unit (123) that acquires attribute information of the receipt based on the extracted receipt identifier; and an automatic execution queue (127) that stores and performs automatic execution processing in a predetermined order. an automatic execution processing change unit (124) that generates information specifying the source code from the obtained submission information as the execution object information and puts it into the automatic execution queue (127), and changes the order of the execution object information in the automatic execution queue (127) based on the obtained attribute information of the document; an object deliverable acquisition unit (125) that acquires the source code and test instance that become the object of the automatic execution processing; an automatic execution processing unit (126) that performs automatic execution processing based on the order of the execution object information changed by the automatic execution processing change unit (124) using the source code and test instance acquired by the object deliverable acquisition unit (125); and a notification unit (128) that notifies the result of the execution by the automatic execution processing unit (126).

[0147] With the above configuration, the automatic execution process server 120 can automatically change the content of the automatic execution process based on the attribute information of the document, and can efficiently implement the automatic execution process in continuous integration.

[0148] The program development support system described in (1) above is characterized in that it also comprises: a version management server (100) for managing the source code or the test instance corresponding to the source code in units of versions; a document management server (110) for managing the work related to program development or the content related to defects as documents; and a network (80) for connecting the automatic execution processing server (120), the version management server (100) and the document management server (110), the submission information acquisition unit (121) receiving the submission completion notification from the version management server (100), acquiring the submission information corresponding to the submission completion notification from the version management server (100), and the attribute information acquisition unit (123) acquiring the attribute information of the document based on the extracted document identifier from the document management server (110).

[0149] Through the above structure, the version management server 100 is used to manage the versions of source code and test instances, and the tasks related to program development or the contents related to defects are managed as documents using the document management server 110, thereby enabling the processing to be decentralized and to be processed in collaboration with the automatic execution processing server 120.

[0150] The program development support system described in (1) above is characterized in that the attribute information acquisition unit (123) acquires at least one of the priority attribute (206), date attribute (207) and critical path attribute (210) contained in the attribute information of the document, and changes the order of the execution object information of the automatic execution queue (127) based on the acquired attribute information.

[0151] With the above configuration, the automatic execution processing server 120 can change the order of the execution target information in the automatic execution queue 127 based on at least one of the priority attribute 206 , the date attribute 207 , and the critical path attribute 210 .

[0152] The program development support system described in (1) above is characterized in that the automatic execution processing unit (126) obtains at least one of the attribute information of the parent document attribute (206), the responsible person attribute (204), the history attribute (211) and the status attribute (206) contained in the attribute information of the document, and sets the content of the automatic execution processing based on the obtained attribute information.

[0153] With the above configuration, the automatic execution process server 120 can determine the content of the automatic execution process based on the parent document attribute 208 , the person in charge attribute 204 , and the history attribute 211 .

[0154] The program development support system described in (3) above is characterized in that the automatic execution processing unit (126) uses the information of the attributes (204) of the person in charge obtained by the attribute information acquisition unit (123) to obtain at least one of the number of unfinished documents in charge, the number of defective documents in charge in the past, and the number of submissions of the person in charge, and sets the content of the automatic execution processing based on the obtained values.

[0155] With the above configuration, the automatic execution process server 120 can automatically change the content of the automatic execution process according to the attribute of the document, and can efficiently implement the automatic execution process in continuous integration.

[0156] In addition, the present invention is not limited to the above-described embodiments, but includes various modified examples. For example, the above-described embodiments are only embodiments described in detail to explain the present invention in an easy-to-understand manner, and are not necessarily limited to embodiments having all the described structures.

[0157] In addition, a part of the structure of a certain embodiment can be replaced with the structure of another embodiment, and the structure of another embodiment can be added to the structure of a certain embodiment. In addition, with respect to a part of the structure of each embodiment, other structures can be added, deleted, or replaced.

[0158] In addition, the above-mentioned structures, functions, processing units, processing components, etc. may be partially or entirely implemented by hardware, for example, by designing with integrated circuits. In addition, the above-mentioned structures, functions, etc. may be implemented by software by interpreting and executing programs for implementing the functions by a processor. Information such as programs, tables, and files for implementing the functions may be set to a recording device such as a memory, a hard disk, or an SSD (Solid State Drive), or a recording medium such as an IC card, an SD card, or a DVD.

[0159] In addition, regarding the control lines and information lines, lines considered necessary for explanation are shown, and not all control lines and information lines are necessarily shown in terms of products. In fact, it can be considered that almost all the components are connected to each other.

[0160] <Supplement>

[0161] The following aspects are listed as representative aspects of the present invention other than those described in the claims.

[0162] The above-mentioned program development support system is characterized in that:

[0163] Using the information of the historical attributes acquired by the attribute information acquisition unit, time information from when the person in charge was changed is acquired, and automatic execution processing is set based on the acquired time information.

[0164] The above-mentioned program development support system is characterized in that:

[0165] As the content of the automatic execution process set by the automatic execution process change unit, at least one of the following settings is made: the source code to be built and tested, whether a review is required, whether correction confirmation of defects in the same part is required, and whether notification to the development person in charge is required.

[0166] The above-mentioned program development support method is characterized in that:

[0167] Using the historical attribute information acquired in the attribute information acquisition step, time information from when the person in charge was changed is acquired, and automatic execution processing is set based on the acquired time information.

[0168] The above-mentioned program development support method is characterized in that:

[0169] As the content of the automatic execution process set in the automatic execution process change step, at least one of the following settings is made: the source code that becomes the object of construction and test execution, whether a review is required, whether correction confirmation of defects in the same part is required, and whether notification to the development responsible person is required.

Claims

1. A program development support system having an automatic execution processing server, the automatic execution processing server having a processor, a memory, and a communication interface, wherein the program development support system is characterized in that: The automatic execution processing server has: a submission information acquisition unit that, upon receiving a submission completion notification indicating that a source code has been registered, acquires submission information including information about the source code and information about a slip corresponding to the source code; A cooperation unit extracts a document identifier corresponding to the submission completion notice from the submission information; an attribute information acquisition unit that acquires attribute information of the document based on the extracted document identifier; An automatic execution queue stores execution object information corresponding to the source code to be automatically executed in a predetermined order; an automatic execution process changing unit that generates information specifying a source code from the acquired submission information as execution target information and puts the information into the automatic execution queue, and changes the order of the execution target information in the automatic execution queue based on the acquired attribute information of the document; A target deliverable acquisition unit that acquires source code and test cases that are targets of the automatic execution process; an automatic execution processing unit that performs automatic execution processing using the source code and test case acquired by the target deliverable acquisition unit based on the order of the execution target information changed by the automatic execution processing change unit; as well as a notification unit for notifying a result of execution by the automatic execution processing unit, The attribute information acquisition unit acquires at least one of a priority attribute, a date attribute, and a critical path attribute included in the attribute information of the document, The automatic execution processing change unit determines whether the value of the priority attribute is above a predetermined threshold, whether the number of days until the date attribute is within a predetermined threshold, and whether it is a document of a critical path in the critical path attribute, and sets a first sort key based on the value of the priority attribute, sets a second sort key based on the number of days until the date attribute, and sets a third sort key based on whether it is a critical path in the critical path attribute, to change the order of the execution object information of the automatic execution queue.

2. The program development support system according to claim 1, wherein: Also features: A version management server, which manages the source code or a test instance corresponding to the source code in units of versions; The document management server manages the work related to program development or the contents related to defects as documents; as well as A network is used to connect the automatic execution processing server, the version management server and the document management server. The commit information acquisition unit receives a commit completion notification from the version management server, and acquires the commit information corresponding to the commit completion notification from the version management server. The attribute information acquisition unit acquires attribute information of the receipt based on the extracted receipt identifier from the receipt management server.

3. The program development support system according to claim 1, wherein: The automatic execution processing unit obtains at least one attribute information of a parent document attribute, a person in charge attribute, a history attribute, and a status attribute included in the attribute information of the document, and sets the content of the automatic execution processing based on the obtained attribute information.

4. The program development support system according to claim 1, wherein: The automatic execution processing unit uses the information of the responsible person's attributes obtained by the attribute information acquisition unit to obtain at least one numerical value of the number of unfinished responsible documents, the number of defective responsible documents in the past, and the number of submissions of the responsible person's attributes, and sets the content of the automatic execution processing based on the obtained numerical value.

5. A program development support method for supporting program development by an automatic execution processing server having a processor, a memory, and a communication interface, the program development support method comprising: a submission information acquisition process in which, upon receiving a submission completion notification indicating that the source code has been registered, the automatic execution processing server acquires submission information including information about the source code and information about a receipt corresponding to the source code; In the collaborative process, the automatic execution processing server extracts a document identifier corresponding to the submission completion notification from the submission information; an attribute information acquisition process, wherein the automatic execution processing server acquires attribute information of the document based on the extracted document identifier; In the queuing process, the automatic execution processing server saves the execution object information corresponding to the source code to be automatically executed into the automatic execution queue in a predetermined order; an automatic execution processing change process, wherein the automatic execution processing server generates information specifying source code from the acquired submission information as execution object information and puts the information into the automatic execution queue, and changes the order of the execution object information in the automatic execution queue based on the acquired attribute information of the document; The automatic execution processing server obtains source code and test examples that are the objects of the automatic execution processing; an automatic execution processing process, wherein the automatic execution processing server performs automatic execution processing using the source code and test case acquired in the target deliverable acquisition process based on the order of the execution target information changed in the automatic execution processing change process; as well as a notification process, wherein the automatic execution processing server notifies the result of execution in the automatic execution processing process, In the process of acquiring the attribute information, at least one of a priority attribute, a date attribute, and a critical path attribute included in the attribute information of the document is acquired. During the automatic execution processing change process, it is determined whether the value of the priority attribute is above a predetermined threshold, whether the number of days until the date attribute is within a predetermined threshold, and whether it is a document on a critical path in the critical path attribute. A first sort key is set based on the value of the priority attribute, a second sort key is set based on the number of days until the date attribute, and a third sort key is set based on whether it is a critical path in the critical path attribute, so as to change the order of the execution object information of the automatic execution queue.

6. The program development support method according to claim 5, characterized in that: In the process of obtaining the submission information, a submission completion notification is received from a version management server that manages the source code or the test case corresponding to the source code in units of versions via a network, and the submission information corresponding to the submission completion notification is obtained from the version management server. In the attribute information acquisition process, attribute information of the receipt based on the extracted receipt identifier is acquired via the network from a receipt management server that manages work related to program development or contents related to defects as receipts.

7. The program development support method according to claim 5, characterized in that: In the automatic execution process, at least one of the parent document attributes, the responsible person attributes, the history attributes and the status attributes included in the attribute information of the document is obtained, and the content of the automatic execution process is set based on the obtained attribute information.

8. The program development support method according to claim 5, characterized in that: During the automatic execution process, the information on the attributes of the person in charge obtained during the attribute information acquisition process is used to obtain at least one of the values ​​of the number of unfinished documents in charge, the number of defective documents in charge in the past, and the number of submissions for the person in charge, and the content of the automatic execution process is set based on the obtained values.

Images