Software development support device and control method for software development support device

The software development support device evaluates reviewer suitability and adjusts authority levels to improve efficiency by reducing inappropriate reviews in agile development.

JP2024179831APending Publication Date: 2024-12-26HITACHI LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
JP2023099041
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-06-16
Publication Date
2024-12-26

AI Technical Summary

Technical Problem

In agile software development, reviewers with varying levels of experience and understanding of the method may lead to inappropriate reviews, increasing unnecessary re-reviews and reducing efficiency.

Method used

A software development support device that evaluates reviewer suitability, grants authority levels based on comments, and determines software change permissions using a system that includes a processor, memory, and storage units to manage authority levels and judgment criteria.

Benefits of technology

This system allows for appropriate evaluation of reviewer suitability, reduces unnecessary re-reviews, and enhances software development efficiency by dynamically adjusting authority levels based on reviewer comments.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024179831000001_ABST
    Figure 2024179831000001_ABST
Patent Text Reader

Abstract

To appropriately evaluate the suitability of reviewers and determine change permission / rejection of software by granting the authority according to the suitability to the reviewers.SOLUTION: A software development support device includes: an authority level storage unit that stores an authority level representing the strength of determination authority for each reviewer who has the determination authority regarding change approval of software; a determination reference storage unit that stores a determination reference for approving the change of the software; a change request acquisition unit that acquires a change request of the software that specifies a change content of the software; a determination result acquisition unit that acquires comments by one or more reviewers for the change request and a determination result about the change approval; a software change decision unit that decides change permission / rejection of the software on the basis of the determination result of each reviewer, the authority level and the determination reference; and an authority level update unit that updates the authority level of the reviewer based on a content of the comment by the reviewer.SELECTED DRAWING: Figure 1
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a software development support device and a control method for the software development support device. [Background technology]

[0002] Modern software development is often carried out according to agile methodologies.

[0003] When developing software using the agile approach, unlike the waterfall approach that was once mainstream, in which detailed definitions of requirements and the overall design structure were determined at the early stages of a project and detailed plans were made before development could proceed, agile development is carried out on a small scale, incorporating changes in specifications and requirements as they occur, allowing development to proceed flexibly.

[0004] Therefore, in the case of agile development, it is important to have a system that provides an efficient collaboration environment within the team and software version control functions. Various platforms such as GitHub, GitLab, and Gerrit have been developed as such systems and are used by many companies, organizations, and individuals.

[0005] In these platforms, software under development, such as source code and libraries, is stored in a repository set up on the cloud and shared among project team members.

[0006] When a software developer wishes to make changes to the software, they submit a pull request, which specifies the changes to be made to the software. The changes are then reviewed by people assigned as reviewers, and once certain conditions are met, such as approval from a certain number of reviewers, the changes are officially reflected (merged) in the software.

[0007] Various techniques have been developed for reviewing such software (see, for example, Patent Document 1 and Patent Document 2). [Prior art documents] [Patent documents]

[0008] [Patent Document 1] JP 2016-133946 A [Patent Document 2] JP 2012-138032 A Summary of the Invention [Problem to be solved by the invention]

[0009] However, the people assigned as reviewers vary widely, and each person has different years of experience in software development, as well as the content and roles of development projects they have worked on.

[0010] For this reason, for example, if a reviewer who is unfamiliar with agile software development methods is assigned to a project using agile software development methods, the review may not be conducted appropriately. In this case, reviews conducted from an inappropriate perspective may increase unnecessary re-review requests, reducing the efficiency of software development.

[0011] The present invention has been made in consideration of these problems, and one of its objectives is to provide a software development support device and a control method for a software development support device that are capable of appropriately evaluating the suitability of a reviewer, granting the reviewer authority according to his or her suitability, and then deciding whether or not to allow changes to the software. [Means for solving the problem]

[0012] A software development support device according to one embodiment of the present invention is a software development support device that supports the development of software, and is equipped with a processor and a memory, and is equipped with: an authority level memory unit that stores, for each reviewer who has the authority to make decisions regarding the approval of changes to the software, an authority level that indicates the strength of the judgment authority of the reviewer; a judgment criterion memory unit that stores judgment criteria for approval of changes to the software; a change request acquisition unit that acquires a change request for the software that specifies the changes to the software; a judgment result acquisition unit that acquires comments by one or more reviewers regarding the software change request and judgment results regarding approval of the changes to the software; a software change decision unit that decides whether to approve the changes to the software based on the judgment results and authority levels of each reviewer and the judgment criteria; and an authority level update unit that updates the authority level of the reviewer to a new authority level based on the content of the comments made by the reviewer.

[0013] In addition, the problems and solutions disclosed in this application will be made clear by the description in the section of the preferred embodiment of the invention and the descriptions in the drawings. Effect of the Invention

[0014] It will be possible to properly evaluate the suitability of reviewers and grant them authority according to their suitability, and then decide whether or not to allow changes to the software. [Brief description of the drawings]

[0015] [Figure 1] FIG. 1 is a diagram illustrating an overall configuration of a software development system. [Diagram 2] FIG. 2 is a diagram illustrating the hardware configuration of a software development support device, a reviewee terminal, and a reviewer terminal. [Diagram 3] FIG. [Figure 4] FIG. 13 illustrates a reviewer management table. [Diagram 5] FIG. 13 illustrates a merge determination criteria management table. [Figure 6]FIG. 13 illustrates a keyword management table. [Figure 7] FIG. 13 is a diagram showing an example of an input screen for a software change request; [Figure 8] FIG. 13 is a diagram showing an example of an input screen for review results. [Figure 9] FIG. 2 is a diagram illustrating a functional configuration of the software development support device. [Figure 10] FIG. 2 is a diagram illustrating a functional configuration of a reviewee terminal. [Figure 11] FIG. 2 is a diagram illustrating a functional configuration of a reviewer terminal. [Figure 12] 10 is a flowchart showing a process flow when software is changed. [Figure 13] 13 is a flowchart showing a process flow when updating the authority level of a reviewer. [Figure 14] FIG. [Figure 15] FIG. 13 illustrates a reviewer management table. [Figure 16] FIG. 13 illustrates an authority level management table. [Figure 17] FIG. 13 illustrates a merge determination criteria management table. [Figure 18] FIG. 1 is a diagram illustrating an overall configuration of a software development system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0016] From the description of this specification and the accompanying drawings, at least the following matters will become apparent. Hereinafter, the present invention will be described in accordance with one embodiment with reference to the accompanying drawings. ==Overall Configuration== 1 shows the overall configuration of a software development system 1000 including a software development support device 100 according to one embodiment of the present invention, a reviewee terminal 200, and a reviewer terminal 300. The software development system 1000 is configured by connecting the software development support device 100, the reviewee terminal 200, and the reviewer terminal 300 communicably via a network 500 such as the Internet, a LAN (Local Area Network), or a telephone network.

[0017] The reviewer terminal 300 is a computer operated by a member of the software development project team who is assigned as a reviewer. The reviewers are composed of QA (quality control) personnel who have the authority to make decisions regarding the approval of software changes, and one or more reviewers are assigned as reviewers within the team. When a reviewee, described below, makes a software change request specifying the changes to be made to the software, the reviewer reviews the change request and responds with a comment and a decision (review result) regarding the approval of the software changes.

[0018] An example of a screen showing the review result replied by the reviewer is shown in Fig. 8. The review result includes at least the decision on whether to accept the software change or not. It also includes any comments made by the reviewer. The review result may also include a decision to withhold, as shown in Fig. 8.

[0019] In this embodiment, each reviewer is given an authority level that indicates the strength of the decision-making authority regarding permission to change the software. This authority level is set and updated according to the suitability of the reviewer evaluated by the software development support device 100 based on the content of the comment made by the reviewer. For example, a stronger authority level is given to a reviewer who has made a comment that improves software development efficiency, and a weaker authority level is given to a reviewer who has made a comment that reduces development efficiency.

[0020] The reviewee terminal 200 is a computer operated by a member of a software development project team, such as a programmer, who is in charge of software development. When this member (reviewee) wishes to make changes to the software (changes to the source code), he or she makes a software change request (review request) specifying the changes to be made to the software. An example of the input screen when the reviewee makes a review request is shown in FIG. 7. If the reviewer's judgment satisfies the specified criteria, the software change is approved and the changes are officially incorporated into the software.

[0021] This criterion can be appropriately determined within the development project team. For example, it can be determined that "a change is permitted if the total value of the authority levels of the reviewers who have approved the change to the software is equal to or greater than a predetermined value," or "a change to the software is permitted if the change is approved by a predetermined number of reviewers who have an authority level equal to or greater than a predetermined level." Also, as described below, different criterion can be set depending on the type of change to the software (for example, a minor change such as fixing a minor bug, or a major change such as adding a new function).

[0022] The software development support device 100 is a computer that supports software development, and as shown in FIG. 18, it acquires a software review request (change request) from the reviewee terminal 200, and acquires the review results (judgment results regarding approval of changes) and comments from the reviewer in response to the review request from the reviewer terminal 300, and performs a process of determining whether or not to approve the changes to the software based on the judgment results of each reviewer regarding approval of changes to the software and the authority level of each reviewer. Furthermore, the software development support device 100 evaluates the suitability of the reviewer based on the contents of the comments obtained from the reviewer, and updates the authority level of the reviewer to a new authority level.

[0023] With this aspect, it is possible to appropriately evaluate the suitability of a reviewer, grant authority to the reviewer according to the suitability, and then decide whether to allow or deny software changes. As a result, even if a project is being developed using an agile methodology, the authority level of a reviewer who has made comments from the perspective of a traditional waterfall-type software development methodology can be lowered, thereby reducing the influence of the reviewer's decision on the permission to change the software, and preventing a decrease in software development efficiency. It is also possible to feed back the evaluation results on the suitability of reviewers to each reviewer, and to encourage reviewers with low suitability to change their behavior, such as by making them recognize the need to catch up on technology. ==Device configuration== Next, a description will be given of the hardware configuration when the software development support device 100, the reviewee terminal 200, and the reviewer terminal 300 are realized by physical computers. Note that the configurations of the software development support device 100, the reviewee terminal 200, and the reviewer terminal 300 are not necessarily the same, but since they share a basic configuration, they are shown together in FIG. 2 to avoid duplication. <Software development support device> The software development support device 100 includes a CPU (Central Processing Unit) 110 , a memory 120 , a communication device 130 , a storage device 140 , an input device 150 , an output device 160 , and a recording medium reading device 170 .

[0024] The CPU 110 is responsible for the overall control of the software development support device 100, and is a processor that realizes the various functions of the software development support device 100 by reading out a software development support device control program 700, which is composed of codes for performing various operations related to this embodiment stored in the storage device 140, and various data into the memory 120 and executing or processing them.

[0025] For example, the CPU 110 executes or processes the software development support device control program 700 and various data, and by working in cooperation with hardware devices such as the memory 120, communication device 130, and storage device 140, functions such as the authority level memory unit 101, judgment criterion memory unit 102, change request acquisition unit 103, judgment result acquisition unit 104, software change decision unit 105, authority level update unit 106, keyword memory unit 107, and authority level management table 108, which will be described later, are realized.

[0026] The CPU 110 may be configured using, for example, a Micro Processing Unit (MPU), a Graphics Processing Unit (GPU), a Field Programmable Gate Array (FPGA), an Application Specific Integrated Circuit (ASIC), an Artificial Intelligence (AI) chip, or the like.

[0027] The software development support device control program 700 is a general term for programs for realizing the functions of the software development support device 100, and includes, for example, application programs, an OS (Operating System), middleware, various libraries, etc. that run on the software development support device 100.

[0028] The memory 120 can be configured by, for example, a semiconductor storage device. The memory 120 is a device that stores programs and data, and is, for example, a Read Only Memory (ROM), a Random Access Memory (RAM), a Non-Volatile RAM (NVRAM), or the like.

[0029] The storage device 140 is a device that provides a physical storage area for storing various programs, data, tables, etc. The storage device 140 is, for example, a solid state drive (SSD), a hard disk drive, an optical storage device (CD (Compact Disc), DVD (Digital Versatile Disc), etc.), a storage system, an IC card, a read / write device for a non-transient storage medium such as an SD card or an optical storage medium, a non-transient storage area of ​​a cloud server, etc. Programs and data can be read into the storage device 140 from other information processing devices equipped with non-transient storage media or non-transient storage devices via a storage medium reader or a communication device 130. The programs and data stored (stored) in the storage device 140 are read into the memory 120 at any time.

[0030] In this embodiment, as shown in FIG. 3, the storage device 140 stores various data such as a software development support device control program 700, a reviewer management table 600, a merge criterion management table 620, a keyword management table 630, and a management repository 640.

[0031] The storage device 140 may be built into the software development support device 100 or may be externally attached.

[0032] The recording medium reader 170 reads the programs and data recorded on a recording medium 800 such as a CD-ROM or a DVD, and stores them in the storage device 140 .

[0033] The communication device 130 is a device that realizes communication with other devices. The communication device 130 is a wired or wireless communication interface that realizes communication with other devices that comply with a predetermined communication protocol via the network 500, and is, for example, a NIC (Network Interface Card), a wireless communication module, etc.

[0034] For example, the communication device 130 transmits and receives data and programs to and from other computers such as the reviewee terminal 200 and the reviewer terminal 300 via a network 500 such as the Internet or a LAN (Local Area Network). For example, the above-mentioned software development support device control program 700 can be stored in another computer (not shown), and the software development support device 100 can download and execute the software development support device control program 700 from this computer.

[0035] Furthermore, the software development support device 100 may not have a storage device 140, and may instead realize its functions by using various data such as the above programs and tables stored in another computer (not shown) communicatively connected via the network 500.

[0036] The input device 150 is a device used by an operator or the like to input data to the software development support device 100, and functions as a user interface. As the input device 150, for example, a keyboard, a mouse, a touch panel, a card reader, a pen-input tablet, a microphone, etc. can be used.

[0037] The output device 160 is a device for outputting information to the outside and functions as a user interface. The output device 160 is, for example, a display device (liquid crystal monitor, LCD (Liquid Crystal Display), graphic card, etc.) that visualizes the above-mentioned various information, a device (audio output device (speaker, etc.)) that converts the above-mentioned various information into voice, and a device (printer, etc.) that converts the above-mentioned various information into text. For example, the software development support device 100 may be configured to input and output information to and from other devices via the communication device 130.

[0038] The input device 150 and the output device 160 constitute a user interface that realizes interactive processing with the user (receiving information, providing information, etc.).

[0039] The software development support device 100 may be implemented with, for example, an operating system, a file system, a DBMS (DataBase Management System) (relational database, NoSQL, etc.), a KVS (Key-Value Store), and the like. <Reviewee terminal> The review terminal 200 is configured to include a CPU 210 , a memory 220 , a communication device 230 , a storage device 240 , an input device 250 , an output device 260 , and a recording medium reading device 270 .

[0040] The CPU 210 is responsible for the overall control of the reviewee terminal 200, and is a processor that realizes the various functions of the reviewee terminal 200 described in this embodiment by reading out a reviewee terminal control program (not shown), which is composed of codes for performing various operations related to this embodiment stored in the storage device 240, and various data into the memory 220 and executing or processing them.

[0041] For example, the review terminal control program and various data are executed or processed by the CPU 210, and by cooperating with hardware devices such as the memory 220, the communication device 230, and the storage device 240, each function such as the change request transmission unit 201 is realized.

[0042] The reviewee terminal control program is a general term for programs for realizing the functions of the reviewee terminal 200, and includes, for example, application programs, an OS (Operating System), middleware, various libraries, etc. that run on the reviewee terminal 200.

[0043] As described above, the review terminal 200 has a common configuration with the software development support device 100, so a duplicated explanation will be omitted. <Reviewer device> The reviewer terminal 300 is configured to include a CPU 310 , a memory 320 , a communication device 330 , a storage device 340 , an input device 350 , an output device 360 ​​, and a recording medium reading device 370 .

[0044] The CPU 310 is responsible for the overall control of the reviewer terminal 300, and is a processor that realizes the various functions of the reviewer terminal 300 described in this embodiment by reading out a reviewer terminal control program (not shown), which is composed of code for performing various operations related to this embodiment stored in the storage device 340, and various data into the memory 320 and executing or processing it.

[0045] For example, the reviewer terminal control program and various data are executed or processed by the CPU 310, and by cooperating with hardware devices such as the memory 320, the communication device 330, and the storage device 340, each function such as the judgment result transmission unit 301 is realized.

[0046] The reviewer terminal control program is a general term for programs for realizing the functions of the reviewer terminal 300, and includes, for example, application programs, an OS (Operating System), middleware, various libraries, and the like that run on the reviewer terminal 300.

[0047] As described above, reviewer terminal 300 has a common configuration with software development support device 100, so a duplicated explanation will be omitted.

[0048] Examples of computers that realize the software development support device 100, the reviewee terminal 200, and the reviewer terminal 300 include personal computers, office computers, server devices, smartphones, tablets, general-purpose computers (mainframes), and the like.

[0049] Furthermore, all or a part of this computer may be realized using virtual information processing resources provided using virtualization technology, process space separation technology, etc., such as a virtual server provided by a cloud system. All or a part of the functions provided by this computer may be realized by a service provided by a cloud system via an API or the like, or may be realized using SaaS (Software as a Service), PaaS (Platform as a Service), IaaS (Infrastructure as a Service), etc.

[0050] When the software development support device 100, the reviewee terminal 200, and the reviewer terminal 300 are realized by a hypervisor type virtual computer, a physical computer (not shown) executes virtualization software (not shown) for realizing the configuration shown in Fig. 2 by software. In this case, the configuration of this physical computer is the same as the configuration shown in Fig. 2.

[0051] Next, the reviewer management table 600, the merge criterion management table 620, the keyword management table 630, and the management repository 640 stored in the storage device 140 shown in FIG. 3 will be described.

[0052] First, an example of the reviewer management table 600 is shown in Fig. 4. The reviewer management table 600 is a table that stores, for each reviewer, an authority level that indicates the strength of the decision-making authority regarding permission to modify software that is given to each reviewer.

[0053] In this embodiment, the authority level is numerical data with a larger value corresponding to stronger decision-making authority, but it may also be character data representing the alphabet such as "A", "B", or "C", or colors such as "gold", "silver", or "bronze".

[0054] Next, an example of the merge determination criteria management table 620 is shown in Fig. 5. The merge determination criteria management table 620 is a table that stores determination criteria for whether or not a software change is permitted.

[0055] In this embodiment, a criterion is set for each type of software change. As shown in Fig. 5, each criterion is defined as the total value of the authority level of the reviewer who responded to accept the change, and is defined as 40 or more for a "minor bug", 120 or more for a "major bug", and 200 or more for a "function addition".

[0056] The judgment criteria may also be defined as, for example, that the calculated value obtained by subtracting the sum of the authority levels of reviewers who responded to approve the change from the sum of the authority levels of reviewers who responded to reject the change is equal to or greater than a predetermined judgment value, that a predetermined number or more reviewers with a predetermined level or higher of judgment authority have approved the change, or that the number of reviewers who rejected the change is equal to or less than a predetermined number.

[0057] Next, an example of the keyword management table 630 is shown in Fig. 6. The keyword management table 630 is a table that stores keywords for evaluating the appropriateness of comments obtained from reviewers and points determined according to the keywords, in association with each keyword.

[0058] In the example shown in Figure 6, "100% coverage" and "bug curve" are concepts that should be considered when developing software using the waterfall model, and if these keywords are used in a comment, -5 points will be given (5 points will be deducted). On the other hand, if the keyword "user story" is used, +3 points will be given.

[0059] The keywords and points set in the keyword management table 630 can be determined for each project. For example, in a waterfall software development project, the points for the above "100% coverage" and "bug curve" can be set to positive values. The keywords and points can also be appropriately reviewed after the start of the project.

[0060] Furthermore, wildcards (? or *) that represent any character or character string may be used in the keywords set in the keyword management table 630. In this manner, it becomes possible to correctly pick up keywords even if there are typos or variations in notation in the comments obtained from reviewers.

[0061] Although not shown in the figure, the management repository 640 stores software under development for each version together with the change history. Therefore, in response to a request, the software development support device 100 can read and output not only the latest version of the software but also a specified previous version of the software from the management repository 640. ==Functional Configuration== 9 shows an example of the functional configuration of software development support device 100. Software development support device 100 has the functions of authority level storage unit 101, judgment criterion storage unit 102, change request acquisition unit 103, judgment result acquisition unit 104, software change decision unit 105, authority level update unit 106, keyword storage unit 107, and authority level management table 108.

[0062] These functions are realized by the hardware of the software development support device 100 executing a software development support device control program 700 according to this embodiment.

[0063] The authority level storage unit 101 stores, for each reviewer, an authority level indicating the strength of the decision-making authority regarding permission to change the software. In this embodiment, the authority level is numerical data that has a higher value as the decision-making authority is stronger, but as described above, it may also be alphabetical data such as "A", "B", and "C", or character data indicating colors such as "gold", "silver", and "bronze". In this embodiment, the authority level storage unit 101 is embodied as the reviewer management table 600 described above.

[0064] The judgment criteria storage unit 102 stores judgment criteria for allowing a change to the software. The judgment criteria can be appropriately determined within the project team, and may be determined, for example, that the total value of the authority levels of the reviewers who responded to allow the change is equal to or greater than a predetermined judgment value, or that a calculated value obtained by subtracting the total sum of the authority levels of the reviewers who responded to reject the change from the total sum of the authority levels of the reviewers who responded to allow the change is equal to or greater than a predetermined judgment value. Furthermore, the judgment criteria may be determined such that a predetermined number or more of reviewers who have judgment authority of a predetermined level or higher have allowed the change, or that the number of reviewers who rejected the change is equal to or less than a predetermined number.

[0065] In this embodiment, the judgment criteria storage unit 102 is embodied as a merge judgment criteria management table 620 .

[0066] The change request acquisition unit 103 acquires a software change request that specifies the change content of the software. An example of a software change request is shown in Fig. 7. In the example shown in Fig. 7, the software change request includes a "change request number," a "change request type," a "corresponding issue number," a "description," and a "change content."

[0067] The "Change Request Number" column contains a number for uniquely identifying each change request.

[0068] The "Change Request Type" field contains information for identifying the type of change request entered by the reviewer. The change request type is identified by selecting from pre-registered options, such as "minor bug," "major bug," and "addition of function." As described above, in this embodiment, the criteria required for approval of a change differ depending on the change request type.

[0069] The "Corresponding Issue Number" column contains a number that identifies the information (such as a bug report) that prompted the software change.

[0070] The "Description" column contains information that specifically explains the changes to the software.

[0071] The "Changes" column lists the specific changes to the source code.

[0072] The change request acquisition unit 103 acquires a software change request including the above-mentioned information from the reviewee terminal 200. Then, the software development support device 100 notifies each reviewer's reviewer terminal 300 that the software change request has arrived. Each reviewer then refers to this software change request and reviews it.

[0073] An example of a screen on which a reviewer enters information when performing a review is shown in Fig. 8. The review screen shown in Fig. 8 has fields for "Target change request number", "Reviewer", "Review result", and "Comment".

[0074] The "Target Change Request Number" field contains the identification number of the change request that is the subject of the review.

[0075] The "Reviewer" field contains information for identifying the reviewer, such as the reviewer's name and ID.

[0076] The "review result" column describes the reviewer's decision regarding the permission to modify the software. In this embodiment, the reviewer can select one of the following results: "approved," "rejected," or "suspended."

[0077] The "Comments" column contains information such as the reasons for the decision.

[0078] When the reviewer completes the review by filling in each of the above fields, this information is transmitted from reviewer terminal 300 to software development support device 100 .

[0079] The judgment result acquisition unit 104 then acquires comments by one or more reviewers on the software change request and the judgment result regarding permission for the software change.

[0080] The software modification decision unit 105 also decides whether to permit the software modification based on the judgment results and authority levels of each reviewer and the judgment criteria. For example, the software change decision unit 105 permits the software change when the sum of the authority levels of the reviewers who have made decisions to permit the software change is equal to or greater than a predetermined judgment value defined as a judgment criterion. According to this embodiment, the judgment results of the reviewers who have made decisions to permit the change can be aggregated after being weighted according to the authority level of each reviewer, so that it is possible to determine whether or not to permit the software change while taking into account the suitability of each reviewer.

[0081] Alternatively, the software change decision unit 105 may approve the software change when a calculated value obtained by subtracting the sum of the authority levels of the reviewers who made the decision to reject the software change from the sum of the authority levels of the reviewers who made the decision to approve the software change is equal to or greater than a predetermined judgment value defined as a judgment criterion. According to this aspect, it is possible to determine whether or not to approve the software change by taking into consideration the judgment result of approving the software change and the judgment result of rejecting the change, and it is also possible to aggregate the judgment results of each reviewer by weighting them according to their authority levels.

[0082] The authority level update unit 106 updates the authority level of the reviewer to a new authority level based on the content of the comment by the reviewer. For example, a reviewer who has made a comment that improves software development efficiency is updated to a stronger authority level, and a reviewer who has made a comment that reduces development efficiency is updated to a weaker authority level. The content of the comment may be analyzed using AI (artificial intelligence), or, as in this embodiment, may be analyzed by performing keyword matching on the comment and accumulating points determined according to the matched keyword.

[0083] The keyword storage unit 107 stores keywords for evaluating the suitability of a comment and points determined according to the keywords, in association with each keyword. Since the suitability of a comment varies depending on the development project, the keywords and points stored in the keyword storage unit 107 are determined for each development project. In this embodiment, the keyword storage unit 107 is embodied as a keyword management table 630.

[0084] The authority level update unit 106 can update the authority level of the reviewer to a new authority level based on the total sum of points corresponding to keywords included in the comments obtained from the reviewer and the current authority level of the reviewer by referring to the keyword storage unit 107. In this manner, it becomes possible to determine the suitability of the reviewer from the comments of the reviewer and reflect it in the authority level.

[0085] For example, the authority level update unit 106 calculates a new authority level by adding the sum of points to the reviewer's current authority level. For example, if the comment made by reviewer CCC shown in Fig. 4 contains the words "user story" and "bug curve," these will be "+3 points" and "-5 points," respectively, according to the keyword management table 630 in Fig. 6. The sum of these, "-2 points," is added to CCC's current authority level of "14," making the new authority level "12." This aspect makes it possible to immediately reflect the points calculated from the comment made by the reviewer in the authority level.

[0086] The authority level update unit 106 may calculate a new authority level by dividing the current authority level of the reviewer and a provisional authority level obtained by adding the total points to the current authority level at a predetermined ratio. For example, in the above example of reviewer CCC, when the predetermined ratio is set to 1:1, the new authority level is "13" by dividing CCC's current authority level "14" and provisional authority level "12" at a 1:1 ratio. In this manner, it is possible to update the authority level according to the appropriateness of the comment made by the reviewer while suppressing a sudden change from the current authority level of the reviewer.

[0087] The authority level management table 108 stores, for each authority level stage, a point value required to acquire the authority level in association with the authority level. As described above, when authority levels are set in stages such as "A", "B", and "C" or "gold", "silver", and "bronze", it is necessary to separately determine the criteria for acquiring each authority level, and the authority level management table 108 is a table for determining the criteria in such cases.

[0088] A case where authority levels are set in stages will be described later, and is embodied as an authority level management table 610 shown in Fig. 16. In the example shown in Fig. 16, authority levels are set as "1", "2", and "3", and to obtain each of these authority levels, it is necessary to obtain "5 points", "30 points", and "100 points", respectively. In this way, by providing the authority level management table 108 (610), it becomes possible to flexibly adjust the difficulty of the authority levels.

[0089] In this case, the authority level update unit 106 updates the cumulative point value to the latest cumulative value ("12 points" in the above CCC example) by adding the total points calculated from the reviewer's latest comments ("-2 points" in the above CCC example) to the cumulative point value calculated from the reviewer's previous comments ("14 points" in the above CCC example), and then updates the reviewer's authority level to a new authority level based on the latest cumulative point value and the authority level management table 108.

[0090] To explain using the example shown in Figure 16, if a reviewer's current accumulated points are "95 points" and his / her authority level is "2", and the points calculated from a new comment created by this reviewer are "20 points", the new accumulated points will be "115 points", so the reviewer's authority level will be updated to "3".

[0091] Next, an example of the functional configuration of the reviewee terminal 200 is shown in Fig. 10. The reviewee terminal 200 has the function of a change request transmission unit 201. This function is realized by the hardware of the reviewee terminal 200 executing a reviewee terminal control program (not shown) according to this embodiment.

[0092] 7 created by the reviewee, to software development support device 100. This allows the reviewee, who wishes to make a change to the software, to request a reviewer to review the software to see whether the change should be permitted.

[0093] Next, an example of the functional configuration of the reviewer terminal 300 is shown in Fig. 11. The reviewer terminal 300 has the function of a judgment result transmission unit 301. This function is realized by the hardware of the reviewer terminal 300 executing a reviewer terminal control program (not shown) according to this embodiment.

[0094] The judgment result transmission unit 301 transmits the review results and comments created by the reviewer, as shown in FIG. ==Process flow== Next, the flow of processing in the software development system 1000 according to this embodiment will be described with reference to FIGS.

[0095] First, when software (source code) is improved in the reviewee terminal 200 (S1000), a software change request is transmitted from the reviewee terminal 200 (S1010).

[0096] When the software development support device 100 acquires a software change request from the reviewee terminal 200, it transmits a review request to the reviewer terminal 300 (S1020).

[0097] When the reviewer checks the source code and makes a comment (S1030), the reviewer terminal 300 transmits the comment and the result of the decision regarding permission to modify the software to the software development support device 100 (S1040).

[0098] In response, software development support device 100 updates the authority level of the reviewer based on the content of the comment (S1050).

[0099] If the reviewer's judgment is "approved", the software development support device 100 adds the reviewer's authority level to a specified variable (herein called the calculated value) (S1080), if the reviewer's judgment is "rejected", the software development support device 100 subtracts the reviewer's authority level from the calculated value (S1070), and if the reviewer's judgment is "pending", the software development support device 100 does not change the calculated value.

[0100] The software development support device 100 updates the above-mentioned calculated value each time it obtains a judgment result from each reviewer's reviewer terminal 300, and when the calculated value (the sum of the authority levels) becomes equal to or exceeds a predetermined judgment value, it approves the software change (S1090).

[0101] For example, in the example of FIG. 5, if the change is a "minor bug," the change is approved if the calculated value is 40 points or more.

[0102] Next, the process of updating the authority level of each reviewer in S1050 described above will be described with reference to FIG.

[0103] First, the software development support device 100 performs a lexical analysis on the comments made by the reviewer (S2000).

[0104] Thereafter, software development support device 100 extracts keywords listed in keyword management table 630 from the comments, and calculates the sum of points corresponding to each keyword (S2010).

[0105] Then, software development support apparatus 100 adds the sum of the points to the current authority level of the reviewer, and updates the authority level to a new one (S2020).

[0106] By performing such processing, it becomes possible to properly evaluate the suitability of the reviewer, grant the reviewer authority according to the suitability, and then decide whether or not to allow the software changes.

[0107] In the example shown in FIG. 12, the reviewer's authority level is updated to a new authority level (S1050) and then the process of updating the calculated value is performed (S1070, S1080). However, it is also possible to perform the process of updating the calculated value first and then update the reviewer's authority level.

[0108] In the example shown in Fig. 12, if the reviewer's decision is to reject, the authority level of the reviewer is subtracted from the calculated value, but if the decision is to reject, the calculated value may not be changed, as in the case of withholding. According to this embodiment, the decision as to whether to permit a software change is based only on the decision on permission, so that software changes are more likely to be approved, and development speed can be improved. The development style to be adopted can be decided based on the operational policy of each development team.

[0109] 12, when a second reviewer with a higher authority level than the first reviewer who has made a decision to reject the software change has made a decision to approve the software change, software development support device 100 may add a value according to the authority level of the first reviewer to the calculated value to cancel the amount subtracted from the calculated value due to the first reviewer's decision result (rejection). In this manner, when the two reviewers make different decisions, it is possible to give priority to the decision result of the reviewer with the higher authority level.

[0110] 12, when a second reviewer with a higher authority level than the first reviewer who has made a decision to approve the software change makes a decision to reject the software change, the software development support device 100 may cancel the amount added to the calculated value due to the first reviewer's decision result (approval) by subtracting a value according to the authority level of the first reviewer from the calculated value. This embodiment also makes it possible to give priority to the decision result of the reviewer with the higher authority level when the decisions of the two reviewers differ. ==Progressive Permission Levels== The software development support device 100 may have an authority level management table 610 in the storage device 140, as shown in Fig. 14. An example of the authority level management table 610 is shown in Fig. 16.

[0111] The authority level management table 610 is a table that stores, for each authority level stage, a point value required to acquire the authority level in association with the authority level. In the example shown in FIG. 16, the authority levels are expressed numerically, such as "1", "2", and "3", but the authority levels may be expressed as "A", "B", "C", "gold", "silver", and "bronze". In any case, when the authority levels are set in stages, it is necessary to separately determine a criterion for acquiring each authority level, and the authority level management table 610 is a table for determining this criterion. By providing such an authority level management table 610, it becomes possible to flexibly adjust the difficulty of the authority level.

[0112] When authority levels are set in stages, the reviewer management table 600 is set as shown in FIG. 15, for example.

[0113] In the example shown in FIG. 15, the reviewer management table 600 stores, for each reviewer, the total points that the reviewer has acquired so far and the authority level.

[0114] The cumulative points are updated according to the keywords in the comment each time the reviewer creates a comment. When the cumulative points reach or exceed the required points defined in the authority level management table 610, the reviewer's authority level is shifted to a higher authority level than the current level, and when the cumulative points fall below the required points defined in the authority level management table 610, the reviewer's authority level is shifted to a lower authority level than the current level.

[0115] FIG. 17 shows an example of the merge criteria management table 620 in the case where the authority levels of the reviewers are expressed as "1," "2," and "3" as in FIG.

[0116] In the example shown in Figure 17, if the change is a "minor bug," the change to the minor bug is permitted if the total authority level of the reviewer who gave the approval is 2 or higher. If the change is a "major bug," the change to the major bug is permitted if the total authority level of the reviewer who gave the approval is 3 or higher. If the change is an "addition of a feature," the change to add a feature is permitted if the total authority level of the reviewer who gave the approval is 4 or higher.

[0117] According to this embodiment, the authority level of each reviewer can be adjusted by changing the contents of the authority level management table 610, so that it is possible to essentially adjust the criteria for determining whether or not to allow software changes without changing the contents of the merge judgment criteria management table 620.

[0118] The software development support device 100 and the control method of the software development support device 100 according to the present embodiment have been described above. According to the present embodiment, it is possible to prevent unnecessary re-reviews and improve the efficiency of software development. In addition, in code reviews, it is possible to provide feedback to reviewers and encourage behavioral change. Furthermore, by scoring the comments and remarks of the reviewers, adjusting the authority of the reviewers based on the results, and determining whether or not to merge based on the results, it is possible to dynamically adjust the reviewer authority and obtain the effect of encouraging behavioral change in the reviewers.

[0119] The above-described embodiment is for the purpose of facilitating understanding of the present invention, and is not intended to limit the present invention. The present invention may be modified or improved without departing from the spirit of the present invention, and equivalents thereof are also included in the present invention.

[0120] For example, in the above embodiment, the authority level of the reviewer is updated to a new authority level based on the text data that the reviewer inputs as a comment to the reviewer terminal 300 when reviewing a software change request, but this comment may be voice data. Or, it may include both text data and voice data. For example, as shown in Fig. 18, when multiple reviewers jointly review using a web meeting system, the software development support device 100 can use voice data that records the remarks of each reviewer as a comment.

[0121] According to such an embodiment, the proficiency of each reviewer in software development methodologies is expressed in words in real time, which is expected to enable a more accurate judgment of the suitability of each reviewer. [Explanation of symbols]

[0122] 100 Software development support device 101 Authority level storage unit 102 Judgment criteria storage section 103 Change Request Acquisition Unit 104 Judgment result acquisition part 105 Software Change Decision Department 106 Authority Level Update Section 107 Keyword storage section 108 Authority Level Management Table 110 CPU 120 Memory 130 Communication Equipment 140 Storage device 150 Input Device 160 Output Device 170 Recording medium reader 200 Reviewee terminals 201 Change Request Submission Department 210 CPU 220 Memory 230 Communication Equipment 240 Storage device 250 Input Device 260 Output Device 270 Recording medium reader 300 reviewer devices 301 Judgment result transmission unit 310 CPU 320 Memory 330 Communication Equipment 340 Storage device 350 Input Device 360 Output Device 370 Recording medium reader 500 Network 600 Reviewer Management Table 610 Privilege Level Management Table 620 Merge Criteria Management Table 630 Keyword Management Table 640 Management Repository 700 Software development support device control program 800 Recording media 1000 Software Development Systems

Claims

1. A software development support device for supporting software development, comprising: A processor and a memory, an authority level storage unit that stores, for each reviewer having authority to make a decision regarding permission to change the software, an authority level that indicates the strength of the decision authority; a criterion storage unit that stores criteria for whether or not a change to the software is permitted; a change request acquisition unit that acquires a change request for the software that specifies the change content of the software; a judgment result acquisition unit that acquires comments by one or more reviewers on the change request for the software and a judgment result regarding permission for the change to the software; a software change decision unit that decides whether or not to permit a change to the software based on the judgment results and authority levels of the reviewers and the judgment criteria; an authority level updating unit that updates an authority level of the reviewer to a new authority level based on the content of the comment by the reviewer; A software development support device comprising:

2. 2. The software development support device according to claim 1, The authority level is numerical data that has a larger value as the judgment authority is stronger, the software change decision unit permits the software change when a sum of authority levels of the reviewers who have determined to permit the software change is equal to or greater than a predetermined judgment value defined as the judgment criterion. Software development support device.

3. 2. The software development support device according to claim 1, The authority level is numerical data that has a larger value as the judgment authority is stronger, The software change decision unit approves the software change when a calculated value obtained by subtracting the sum of the authority levels of each reviewer who has made a decision to reject the software change from the sum of the authority levels of each reviewer who has made a decision to approve the software change is equal to or greater than a predetermined judgment value defined as the judgment criterion. Software development support device.

4. 4. The software development support device according to claim 3, When a second reviewer having a higher authority level than a first reviewer who has made a decision to reject the software change has made a decision to approve the software change, the software change decision unit corrects the calculated value by adding a value corresponding to the authority level of the first reviewer to the calculated value. Software development support device.

5. 2. The software development support device according to claim 1, The authority level is numerical data that has a larger value as the judgment authority is stronger, a keyword storage unit that stores keywords for evaluating the appropriateness of the comment and points determined according to the keywords in association with each keyword; Further equipped with the authority level update unit updates the authority level of the reviewer to the new authority level based on a total sum of points corresponding to the keywords included in the comments obtained from the reviewer and a current authority level of the reviewer; Software development support device.

6. 6. The software development support device according to claim 5, the authority level update unit calculates the new authority level by adding the sum of the points to the reviewer's current authority level; Software development support device.

7. 6. The software development support device according to claim 5, the authority level update unit calculates the new authority level by dividing the current authority level of the reviewer and a provisional authority level obtained by adding the total sum of the points to the current authority level in a predetermined ratio; Software development support device.

8. 6. The software development support device according to claim 5, an authority level management table that stores, for each of the authority levels, a value of the points required to acquire the authority level of the corresponding level in association with each other; Further equipped with the authority level update unit updates the accumulated value of points to a latest accumulated value by adding the sum of points calculated from the latest comments of the reviewer to an accumulated value of points calculated from previous comments of the reviewer, and then updates the authority level of the reviewer to the new authority level based on the latest accumulated value of points and the authority level management table. Software development support device.

9. 2. The software development support device according to claim 1, The comment includes at least one of text data created by the reviewer and audio data recording the content of the reviewer's remarks. Software development support device.

10. A method for controlling a software development support device having a processor and a memory for supporting software development, comprising: The software development support device, storing an authority level representing the strength of the decision-making authority for each reviewer who has decision-making authority regarding the approval of changes to the software; storing criteria for whether a change to the software is permitted; obtaining a change request for the software that specifies the changes to be made to the software; Obtaining comments by one or more reviewers on the change request for the software and a judgment result regarding approval of the change to the software; determining whether to permit or deny the modification of the software based on the judgment results and authority levels of the reviewers and the judgment criteria; updating the authority level of the reviewer to a new authority level based on the content of the comment by the reviewer; A method for controlling a software development support device.

Citation Information

Patent Citations

  • Information processing device, information processing method and computer program

    JP2012138032A

  • Source code reviewing method and system therefor

    JP2016133946A