Information processing device, information processing method, information processing program, and terminal device

Abstract

The present invention provides an information processing device, an information processing method, an information processing program, and a terminal device that allow for clearer prioritization of bug countermeasures compared to conventional methods. [Solution] The information processing device of the embodiment is an information processing device for managing bugs in software development, and comprises at least one processor configured to calculate priority points for determining the priority of bug repair according to bug attribute information relating to the attributes of a bug, including bug repair method information relating to a bug repair method, and to output bug information relating to the bug corresponding to the priority points.

Description

Technical Field

[0001] The present disclosure relates to an information processing apparatus, an information processing method, an information processing program, and a terminal apparatus.

Background Art

[0002] Conventionally, in software development, in a point assignment scheme for determining the prioritization of bug countermeasures, points are determined by adding an adjustment value as necessary to a value obtained by multiplying the bug priority and the severity. The priority indicates, for example, the urgency of fixing a bug, and the severity indicates, for example, the degree of impact on functions and operations, and is generally classified into 3 to 5 levels. The adjustment value is added, for example, at the discretion of the project leader layer in software development.

Prior Art Documents

Patent Documents

[0003]

Patent Document 1

Summary of Invention

Problems to be Solved by the Invention

[0004] However, in the case of large-scale software development, the number of bug occurrences may increase. When the number of bug occurrences increases, a plurality of bugs having the same priority point as described above exist, and it becomes difficult to determine which bug to take countermeasures against first. For this reason, the priority judgment for bug countermeasures may differ between the software development staff and the leader, and there is room for improvement because it is necessary to clarify the priority of bug countermeasures.

[0005] One of the problems to be solved by the present disclosure is to provide an information processing apparatus, an information processing method, an information processing program, and a terminal apparatus that can clarify the priority of bug countermeasures compared to the conventional art.

Means for Solving the Problems

[0006] The information processing device relating to this disclosure is an information processing device for managing bugs in software development, and comprises at least one processor configured to calculate priority points for determining the priority of bug repair based on bug attribute information relating to the attributes of the bug, including bug repair method information relating to a bug repair method, and to output bug information relating to the bug corresponding to the priority points. [Effects of the Invention]

[0007] According to this disclosure, it is possible to clarify the priority of bug fixes compared to the past. [Brief explanation of the drawing]

[0008] [Figure 1] Figure 1 shows an example of a schematic configuration of an information processing system according to the embodiment. [Figure 2] Figure 2 is a functional block diagram showing an example of the functional configuration of a terminal device according to this embodiment. [Figure 3] Figure 3 is a functional block showing an example of the functional configuration of the server according to this embodiment. [Figure 4] Figure 4 is a schematic diagram illustrating the first point stored in register C according to the embodiment. [Figure 5] Figure 5 is a schematic diagram illustrating the points to be stored in register D according to the embodiment. [Figure 6] Figure 6 is a schematic diagram illustrating the points to be stored in register E according to the embodiment. [Figure 7] Figure 7 is a schematic diagram illustrating the second point stored in register F according to the embodiment. [Figure 8] Figure 8 is a schematic diagram illustrating the third point stored in register G according to the embodiment. [Figure 9] Figure 9 is a schematic diagram illustrating the release schedule information according to this embodiment. [Figure 10] Figure 10 is a schematic diagram showing an example of a display screen displayed by a terminal device according to this embodiment. [Figure 11] FIG. 11 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 12] FIG. 12 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 13] FIG. 13 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 14] FIG. 14 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 15] FIG. 15 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 16] FIG. 16 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 17] FIG. 17 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 18] FIG. 18 is a schematic diagram illustrating an example of a display screen presented by the terminal device according to the embodiment. [Figure 19] FIG. 19 is a flowchart illustrating an example of the flow of processing executed by the server according to the embodiment. [Figure 20] FIG. 20 is a flowchart illustrating an example of the flow of processing executed by the server according to the embodiment. [Figure 21] FIG. 21 is a flowchart illustrating an example of the flow of processing executed by the server according to the embodiment. [Figure 22] FIG. 22 is a functional block diagram illustrating an example of the functional configuration of the server according to the first modification. [Figure 23] FIG. 23 is a schematic diagram for explaining the fifth point stored in register J and the sixth point stored in register K according to the first modification. [Figure 24] FIG. 24 is a flowchart illustrating an example of the flow of processing executed by the server according to the first modification. [Figure 25] FIG. 25 is a functional block diagram illustrating an example of the functional configuration of the server according to the second modification. [Figure 26] Figure 26 is a schematic diagram for explaining the seventh point stored in register I according to the second modification. [Figure 27] Figure 27 is a schematic diagram for explaining the first point stored in register C according to the second modification. [Figure 28] Figure 28 is a flowchart illustrating an example of the flow of processing executed by the server according to the second modification. [Figure 29] Figure 29 is a flowchart illustrating an example of the flow of processing executed by the server according to the second modification. [Figure 30] Figure 30 is a functional block diagram illustrating an example of the functional configuration of the server according to the third modification. [Figure 31] Figure 31 is a flowchart illustrating an example of the flow of processing executed by the server according to the third modification. [Figure 32] Figure 32 is a diagram illustrating an example of the hardware configuration of the information processing system according to the embodiment and the modifications. [Mode for Carrying Out the Invention]

[0009] Hereinafter, embodiments of the information processing apparatus and the terminal apparatus according to the present disclosure will be described with reference to the drawings.

[0010] (Embodiment) Figure 1 is a diagram illustrating an example of the schematic configuration of the information processing system 100 according to the embodiment. As shown in Figure 1, the information processing system 100 includes a terminal apparatus 1 and a server 2. The terminal apparatus 1 and the server 2 are communicably connected via, for example, a network or the like.

[0011] Terminal device 1 is a terminal used by users involved in software development. Terminal device 1 inputs and outputs bug information related to bugs in software development. Terminal device 1 can be various mobile devices such as notebook PCs, tablet devices, and smartphones as appropriate. Alternatively, a stationary terminal such as a regular personal computer may be used as terminal device 1. Terminal device 1 transmits bug information related to bugs in software development, input by the user, to server 2. A detailed explanation of bug information will be given later.

[0012] Server 2 is a device for managing bugs in software development. For example, based on bug information transmitted by terminal device 1, Server 2 determines priority points for determining the priority of bug fixes according to bug attribute information, including bug recovery method information regarding the bug recovery method, and outputs bug information corresponding to the priority points. Server 2 is an example of an information processing device. Server 2 is a dedicated or general-purpose computer. Details of these processes will be described later. Note that although terminal device 1 and Server 2 are shown in a single configuration in Figure 1, the information processing system 100 may include multiple terminal devices 1 and multiple servers 2.

[0013] Figure 2 is a functional block diagram showing an example of the functional configuration of terminal device 1 according to this embodiment. Terminal device 1 includes an input unit 11 and a display unit 12. However, the functions of terminal device 1 are not limited to these.

[0014] The input unit 11 accepts various operations from the user. Specifically, the input unit 11 inputs bug attribute information, including bug recovery method information regarding the bug recovery method. The input unit 11 also transmits the bug attribute information entered by the user to the server 2. The input unit 11 is, for example, a keyboard and a pointing device such as a mouse, a microphone, etc.

[0015] The display unit 12 displays various types of information. Specifically, the display unit 12 receives bug information related to bugs corresponding to priority points used to determine the priority of bug fixes, which is transmitted by the server 2. The display unit 12 also outputs bug information. The display unit 12 is, for example, a display, a speaker that outputs various types of sound, etc.

[0016] The input unit 11 and the display unit 12 may be integrated into a single touch panel. Alternatively, the input unit 11 and the display unit 12 may be configured separately from the terminal device 1. In this case, the input unit 11 and the display unit 12 and the terminal device 1 may be connected in a way that allows for communication.

[0017] Figure 3 shows a functional block illustrating an example of the functional configuration of Server 2 according to the embodiment. Server 2 comprises a first determination unit 211, an acquisition unit 212, a second determination unit 213, a third determination unit 214, a first storage unit 215, a second storage unit 216, a third storage unit 217, a fourth storage unit 218, a fifth storage unit 219, a sixth storage unit 220, a seventh storage unit 221, an eighth storage unit 222, a calculation unit 223, a fourth determination unit 224, an addition unit 225, an issuance unit 226, a ninth storage unit 227, an output unit 228, a fifth determination unit 229, and a notification unit 230. However, the functions of Server 2 are not limited to these.

[0018] The first determination unit 211 determines whether a bug has occurred. Specifically, the first determination unit 211 determines whether bug information regarding a bug in software development has been transmitted from the terminal device 1.

[0019] The acquisition unit 212 acquires bug information, including bug attribute information regarding the attributes of the bug. Specifically, the acquisition unit 212 acquires bug information, including bug attribute information regarding the attributes of the bug transmitted by the terminal device 1, and bug countermeasure deadline information regarding the deadline for bug countermeasures. The bug attribute information includes at least bug recovery method information regarding the method of recovering the bug.

[0020] Furthermore, bug attribute information includes, in addition to bug recovery method information, reporting information regarding the recipient of the bug report, customer report information regarding the customer report of the bug, severity information regarding the bug's severity, frequency information regarding the bug's occurrence, priority information regarding the bug's priority, severity rank information regarding the bug's severity rank associated with the severity, reporting information, and customer report information, priority rank information regarding the bug's priority and frequency associated with the bug's priority and occurrence, management information regarding software development management, and adjustment point information regarding adjustment points for adjusting priority points. A detailed explanation of the bug attribute information described above will be given later.

[0021] The second determination unit 213 determines whether the recipient of the report information included in the bug attribute information is a customer. Specifically, the second determination unit 213 determines whether the recipient of the report information included in the bug attribute information acquired by the acquisition unit 212 is a customer. The recipients of the report are, for example, the customer, who is the first user who commissioned the software development, and the development company, who is the second user who was commissioned to develop the software.

[0022] The third determination unit 214 determines whether the customer report information included in the bug attribute information is a customer report. Specifically, if the second determination unit 213 determines that the recipient of the report information included in the bug attribute information is not a customer, the third determination unit 214 determines whether a customer report is required based on the customer report information included in the bug attribute information acquired by the acquisition unit 212. The customer report information includes whether a second user has requested a customer report from the first user. Customer reports are sometimes also referred to as customer sharing.

[0023] The first storage unit 215 stores the severity rank in register A. The register is a memory circuit built into the processor of server 2. Specifically, when the second determination unit 213 determines that the recipient of the report information included in the bug attribute information is a customer, the first storage unit 215 stores the severity rank included in the severity rank information regarding the severity of the bug corresponding to the customer in register A.

[0024] Furthermore, if the third determination unit 214 determines that a customer report is required based on the customer report information included in the bug attribute information, the first storage unit 215 stores the severity rank included in the severity rank information regarding the severity of the bug corresponding to the customer report in register A. In addition, if the third determination unit 214 determines that a customer report is not required based on the customer report information included in the bug attribute information, the first storage unit 215 stores the severity rank included in the severity rank information regarding the severity of the bug corresponding to the development company in register A.

[0025] The second storage unit 216 stores the priority rank in register B. Specifically, when the second determination unit 213 determines that the recipient of the report information included in the bug attribute information is a customer, the second storage unit 216 stores the priority rank related to the priority of the bug corresponding to the customer and the priority of the bug associated with the frequency of occurrence in register B. Also, when the third determination unit 214 determines that a customer report is required based on the customer report information included in the bug attribute information, the second storage unit 216 stores the priority rank related to the priority of the bug corresponding to the customer report and the priority of the bug associated with the frequency of occurrence in register B.

[0026] Furthermore, if the third determination unit 214 determines that customer reporting is not required based on the customer reporting information included in the bug attribute information, the second storage unit 216 stores the priority rank of the bug, which is associated with the bug priority and frequency of occurrence, in register B.

[0027] The third storage unit 217 stores the first point determined from registers A and B in register C. Specifically, the third storage unit 217 stores the first point determined from register A, where the severity rank is stored in the first storage unit 215, and from register B, where the priority rank is stored in the second storage unit 216, in register C. The first point to be stored in register C will be explained using Figure 4.

[0028] Figure 4 is a schematic diagram illustrating the first point stored in register C according to the embodiment. Table T1 shown in Figure 4 is a table showing the first point determined from the severity rank associated with the severity of the bug corresponding to the customer, customer report, or development company, and the priority rank of the bug associated with the priority and frequency of occurrence of the bug corresponding to the customer, customer report, or development company. For example, if the severity rank is "1" and the priority rank is "1", the first point will be "178,000". Note that the points shown in Table T1 may be set according to the software development.

[0029] Returning to Figure 3, the explanation continues. The fourth storage unit 218 stores the points determined from the recovery method information in register D. Specifically, the fourth storage unit 218 stores the points corresponding to the bug recovery method information included in the bug attribute information acquired by the acquisition unit 212 in register D. Here, the points to be stored in register D will be explained using Figure 5.

[0030] Figure 5 is a schematic diagram illustrating the points stored in register D according to the embodiment. Table T2 shown in Figure 5 is a table that associates bug recovery methods with points. For example, if the recovery method is "never recover," the points will be "30." Furthermore, the points corresponding to the bug recovery method information are set lower the easier it is to recover from the bug state. Note that the points shown in Table T2 may be set according to software development.

[0031] Returning to Figure 3, the explanation continues. The fifth storage unit 219 stores the points determined from the occurrence frequency information in register E. Specifically, the fifth storage unit 219 stores the points corresponding to the occurrence frequency information included in the bug attribute information acquired by the acquisition unit 212 in register E. Here, the points to be stored in register E will be explained using Figure 6.

[0032] Figure 6 is a schematic diagram illustrating the points stored in register E according to the embodiment. Table T3 shown in Figure 6 is a table that associates the frequency of bug occurrence with points. For example, if the frequency of occurrence is "Always (100%)", the points will be "9". Note that the points shown in Table T3 may be set according to software development.

[0033] Returning to Figure 3, the explanation continues. The sixth storage unit 220 stores a second point in register F, which is the product of the points stored in registers D and E. Specifically, the sixth storage unit 220 stores a second point in register F, which is the product of the point stored in register D by the fourth storage unit 218 and the point stored in register E by the fifth storage unit 219. Here, the second point stored in register F will be explained using Figure 7.

[0034] Figure 7 is a schematic diagram illustrating the second point stored in register F according to the embodiment. Table T4 shown in Figure 7 is a table showing the second point, which is obtained by multiplying the point corresponding to the bug recovery method by the point corresponding to the bug occurrence frequency. For example, if the recovery method is "never recover" and the occurrence frequency is "Always (100%)", the second point obtained by multiplying the respective points is "270". Note that the second point shown in Table T4 may be set according to software development.

[0035] Returning to Figure 3, the explanation continues. The seventh storage unit 221 stores the third point determined from the management information in register G. Specifically, the seventh storage unit 221 stores the third point corresponding to the software development management of the management information included in the bug attribute information acquired by the acquisition unit 212 in register F. Here, the third point stored in register F will be explained using Figure 8.

[0036] Figure 8 is a schematic diagram illustrating the third point stored in register G according to the embodiment. Table T5 shown in Figure 7 is a table that associates software development management with the third point. For example, if the management is "PDT", the third point will be "10,000,000". Note that the third point shown in table T5 may be set according to the software development.

[0037] Returning to Figure 3, the explanation continues. The eighth storage unit 222 stores the fourth point determined from the adjustment point information in register H. Specifically, the eighth storage unit 222 stores the fourth point corresponding to the adjustment point included in the bug attribute information acquired by the acquisition unit 212 in register H. The priority points corresponding to the adjustment points are set as appropriate depending on the software development and bugs.

[0038] The calculation unit 223 calculates priority points to determine the priority for fixing bugs, based on bug attribute information relating to bug attributes, including bug recovery method information relating to bug recovery methods. Specifically, the calculation unit 223 sums up the first point associated with severity rank information and priority rank information, the second point associated with bug recovery method information and occurrence frequency information, the third point corresponding to management information, and the fourth point corresponding to adjustment point information as priority points.

[0039] For example, the calculation unit 223 sums up the points stored in registers C, F, G, and H to calculate priority points for determining the priority of bug fixes. Specifically, the calculation unit 223 sums up the first point stored in register C by the third storage unit 217, the second point stored in register F by the sixth storage unit 220, the third point stored in register G by the seventh storage unit 221, and the fourth point stored in register H by the eighth storage unit 222 to calculate priority points for determining the priority of bug fixes.

[0040] The fourth determination unit 224 determines whether the deadline for bug countermeasures included in the bug information is not entered. Specifically, the fourth determination unit 224 determines whether the deadline for bug countermeasures included in the bug information, which was acquired by the acquisition unit 212, is not entered. Here, "not entered" means that the user has not set a deadline for countermeasures.

[0041] The addition unit 225 adds a deadline for countermeasures based on priority points. Specifically, if the fourth determination unit 224 determines that the deadline for countermeasures in the bug information is not entered, the addition unit 225 refers to the release schedule information related to the release schedule based on the priority points calculated by the calculation unit 223 and adds a deadline for countermeasures. The release schedule information will be explained using Figure 9.

[0042] Figure 9 is a schematic diagram illustrating the release schedule information according to the embodiment. Table T6 shown in Figure 9 is a table that associates software development milestones with the scheduled dates for those milestones. For example, if the milestone is "Alpha Version (Function Implementation)", the scheduled date will be "YYYY / 04 / 01". Note that the scheduled dates shown in Table T6 are set according to the software development.

[0043] Returning to Figure 3, let's continue the explanation. The issuing unit 226 issues bug management tickets to manage bugs. Specifically, the issuing unit 226 issues bug management tickets that associate the bug information acquired by the acquisition unit 212, the priority points calculated by the calculation unit 223, and the deadline for corrective action.

[0044] The ninth storage unit 227 stores bug information corresponding to bug management tickets in a database. Specifically, the ninth storage unit 227 stores bug information corresponding to bug management tickets issued by the issuing unit 226 in a database. The database is an auxiliary storage device built into server 2. Note that the database may be on a different server connected to server 2, or it may be an external auxiliary storage device connected to server 2.

[0045] The output unit 228 outputs bug information related to bugs corresponding to priority points. Specifically, the output unit 228 outputs bug information related to bugs corresponding to priority points calculated by the calculation unit 223 to the terminal device 1. For example, the output unit 228 outputs the bug information sorted in descending order of priority points calculated by the calculation unit 223.

[0046] The fifth determination unit 229 determines whether a priority point is subject to automatic notification. Specifically, the fifth determination unit 229 determines whether the priority point of the bug information output by the output unit 228 is subject to automatic notification. Here, the fifth determination unit 229 determines that a priority point is subject to automatic notification when the priority point is above a predetermined threshold. The predetermined threshold can be arbitrarily set by the user. The server 2 may also set a predetermined threshold according to the priority point.

[0047] The notification unit 230 automatically notifies bug information. Specifically, when the fifth determination unit 229 determines that a priority point is subject to automatic notification to the user, the notification unit 230 notifies the terminal device 1 of the bug information subject to automatic notification.

[0048] Next, we will describe the user interface output by terminal device 1.

[0049] Figure 10 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. Display screen D1 shown in Figure 10 is a screen where the user inputs bug attribute information regarding the attributes of a bug. Display screen D1 shows an overview of the bug. The overview shows priority points, response priority, severity of the phenomenon, customer report, customer report rank, customer report priority, customer report date, customer report recipient, defect notification number (within customer management), and details about the handed-over bug.

[0050] The priority level is displayed as selectable from options such as "Immediaite," "Highest," "Medium," and "Low." The severity level is displayed as selectable from options such as "A(MM6)," "A(Bloker)," "A," "B," "B-," "C," and "Unassigned."

[0051] The customer report shown on display screen D1 can be selected from options such as "Unassigned", "Pending", "Reported", "Not Report", and "Transferred". The customer report rank can be selected from options such as "A(MM6)", "A(Bloker-over100)", "A(Bloker-over10)", "A(Bloker)", "A", "A-", "B", "B-", "C", and "Unassigned". The customer report priority can be selected from options such as "P0-Bloker", "P1-Critical", "P2-High", "P3-Medium", "P4-Low", and "Unassigned".

[0052] Figure 11 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. Display screen D2 shown in Figure 11 is a screen where the user inputs bug attribute information regarding the attributes of a bug. Display screen D2 shows the bug details regarding the details of the bug. The bug details include the frequency of occurrence, the number of occurrences / number of attempts, the recovery method, the test specification, the test item number, the serial number, remarks, and the recipient of the report.

[0053] The frequency of occurrence can be selected from options such as "Always (100%)", "High (99%-50%)", "Medium (49%-10%)", "Low (less than 10%)", "Only Once", and "Unknown". The recovery method can be selected from options such as "Never recover", "Only recovers with +B OFF / ON", "Only recovers with ACC OFF / ON", "Manual recovery (not the same operation)", "Manual recovery (user operation retry)", "Automatic recovery (after a certain time of 5 seconds or more)", "Automatic recovery (after a certain time of less than 5 seconds)", and "Unknown". The recipient of the report can be selected from options such as "01_Soft", "02_Electrical", "03_Mechanical", "04_Quality", "51_c_Customer", and "91_o_OtherUnit".

[0054] Figure 12 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. Display screen D3 shown in Figure 12 is a screen where the user inputs bug attribute information regarding the attributes of a bug. Display screen D3 shows content related to management. The content related to management includes adjustment points for adjusting priority points and management information related to software development management. For example, "1,000,000" is entered for the adjustment points on display screen D3. For example, the "Top 10 Priority" checkbox is selected for the management information on display screen D3.

[0055] Terminal device 1 transmits bug attribute information to server 2, for example, regarding the attributes of bugs entered according to display screens D1, D2, and D3 shown in Figures 10 to 12. Server 2 then calculates priority points to determine the priority for fixing bugs according to the bug attribute information and outputs bug information for bugs corresponding to the priority points. Next, the bug information that server 2 transmits to terminal device 1 will be described.

[0056] Figure 13 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. Display screen D4 shown in Figure 13 is a screen that sorts and outputs bug information in order of highest priority points. Display screen D5 shown in Figure 13 is a screen that outputs priority points.

[0057] Display screen D4 shows bug information, such as information associated with "Defect ID", "Summary", "Status", "Category", "Priority Points", "Priority", "Severity", "Detected Process", "Frequency", "Recovery Method", "Recipient", "Customer Priority", "Adjustment Points", and "Management Points". Display screen D5 shows the priority point value of "2,073,270" for "Defect ID" 433947.

[0058] Next, we will explain the settings for automatically notifying users of bug information according to their priority points. For example, a user can use terminal device 1 to create a dashboard to be displayed on terminal device 1, then set up alerts on the dashboard, and configure automatic notifications corresponding to those alerts. As a result, terminal device 1 can automatically notify users of bug information.

[0059] Figure 14 is a schematic diagram showing an example of a display screen displayed by terminal device 1 according to the embodiment. The transition of the display screen shown in Figure 14 is the process of creating a dashboard on terminal device 1. First, the user moves the cursor to display screen D6 and selects pin 151. Next, the user selects "Existing Dashboard" 152 on display screen D7 and presses the pin button 153. As a result, the selected content is displayed on the dashboard as shown in display screen D8.

[0060] Figure 15 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. The transition of the display screens shown in Figure 15 is for setting alerts. First, the user selects area 161 of display screen D9 to display display screen D10. Next, the user clicks area 162 of display screen D10 to display display screen D11. Display screen D11 is the screen for managing alerts.

[0061] The user then enters the value of the priority points to be targeted for automatic notifications into the threshold 163 on display screen D11 and presses the "Save and Close" button 164 on display screen D11. As a result, the threshold for priority points to be targeted for automatic notifications can be set. The user can also set the frequency of automatic notifications using display screen D11.

[0062] Figure 16 is a schematic diagram showing an example of a display screen displayed by terminal device 1 according to the embodiment. The transition of the display screens shown in Figure 16 is for setting up automatic notification of bug information. First, when the user presses the "Automatic Notification Settings" button 171 on display screen D12, terminal device 1 displays at least one of display screens D13 or D14. Display screen D13 is for setting up automatic notification of bug information in the workflow, which is a shared tool for software development. Display screen D14 is for setting up automatic notification of bug information in the workflow, which is a shared tool for software development.

[0063] Users can complete the setting to automatically notify users of bug information by pressing the save button 172 displayed on screens D13 and D14. Note that the screen transitions shown in Figures 14 to 17 are just one example of the setting to automatically notify users of bug information, and other screens can be used to set up automatic bug notification.

[0064] Figure 17 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. Display screen D15 shown in Figure 17 is an automated notification corresponding to the content saved in display screen D13 shown in Figure 16. Display screen D15 shows the content of an automated notification with the following text: "Via Workflow Mr. A 6:12 A high-priority bug has been issued ·Defect ID:12345 ·Summary:Screen lock occurred while driving ·Priority points:0,000,000 Occurred in customer evaluation ·Date and time of occurrence:202y / mm / dd ·Version:xxxxxx …The log is below. Please follow up with analysis. URL:"

[0065] Figure 18 is a schematic diagram showing an example of a display screen displayed by the terminal device 1 according to the embodiment. Display screen D16 shown in Figure 18 is an automated notification corresponding to the content saved in display screen D14 shown in Figure 16. Display screen D16 shows the content of an automated notification with the text: "Notification of request for follow-up to confirm reproduction of a high-priority bug To: Mr. A 6:12 A high-priority bug has been issued ·Defect ID:12345 ·Summary:Screen lock occurred while driving ·Priority points:0,000,000 Occurred in customer evaluation ·Date and time of occurrence:202y / mm / dd ·Version:xxxxxx ·Frequency of occurrence:Low (less than 10%) The log is below. Please follow up to confirm reproduction. URL:"

[0066] Users can understand bug information for priority points targeted by automatic notifications by checking the automatic notifications displayed on screens D15 and D16.

[0067] Figure 19 is a flowchart showing an example of the processing flow executed by Server 2 according to this embodiment.

[0068] The first determination unit 211 determines whether bug information regarding a bug in software development has been transmitted from the terminal device 1 (step S101). If the first determination unit 211 determines that no bug information has been transmitted (step S101: No), the process returns to step S101. If the first determination unit 211 determines that bug information has been transmitted (step S101: Yes), the process proceeds to step S102. The acquisition unit 212 acquires bug information, including bug attribute information regarding the attributes of the bug transmitted by the terminal device 1 and bug countermeasure deadline information regarding the deadline for bug countermeasures (step S102). Subsequently, the calculation unit 223 calculates priority points to determine the priority for fixing the bugs (step S103).

[0069] Next, the fourth determination unit 224 determines whether the bug fix deadline information included in the bug information acquired by the acquisition unit 212 is not entered (step S104). If the fourth determination unit 224 determines that the bug fix deadline information included in the bug information acquired by the acquisition unit 212 is already entered (step S104: No), the process proceeds to step S106. On the other hand, if the fourth determination unit 224 determines that the bug fix deadline information included in the bug information acquired by the acquisition unit 212 is not entered (step S104: Yes), the process proceeds to step S105.

[0070] In step S105, the addition unit 225 refers to the release schedule information related to the release schedule based on the priority points calculated by the calculation unit 223 and adds the countermeasure deadline (step S105). Subsequently, the issuing unit 226 issues a bug management ticket that manages the bug associated with the bug information acquired by the acquisition unit 212, the priority points calculated by the calculation unit 223, and the countermeasure deadline (step S106). Subsequently, the ninth storage unit 227 stores the bug information corresponding to the bug management ticket issued by the issuing unit 226 in the database (step S107). Subsequently, the output unit 228 outputs the bug information related to the bug corresponding to the priority points calculated by the calculation unit 223 to the terminal device 1 (step S108).

[0071] The fifth determination unit 229 determines whether the priority point of the bug information output by the output unit 228 is subject to automatic notification (step S109). If the fifth determination unit 229 determines that the priority point of the bug information output by the output unit 228 is not subject to automatic notification (step S109: No), the server 2 terminates this process. On the other hand, if the fifth determination unit 229 determines that the priority point of the bug information output by the output unit 228 is subject to automatic notification (step S109: Yes), the process proceeds to step S110. In step S110, the notification unit 230 notifies the terminal device 1 of the bug information subject to automatic notification. When the process in step S110 is completed, the server 2 terminates this process.

[0072] Figure 20 is a flowchart showing an example of the processing flow executed by Server 2 according to this embodiment. The flowchart in Figure 20 is a detailed explanation of the process described in step S103 shown in Figure 19.

[0073] The second determination unit 213 determines whether the target of the reported information included in the bug attribute information acquired by the acquisition unit 212 is a customer (step S111). If the second determination unit 213 determines that the target of the reported information included in the bug attribute information acquired by the acquisition unit 212 is not a customer (step S111: No), the process proceeds to step S114. On the other hand, if the second determination unit 213 determines that the target of the reported information included in the bug attribute information acquired by the acquisition unit 212 is a customer (step S111: Yes), the process proceeds to step S112.

[0074] In step S112, the first storage unit 215 stores the severity rank of the bug corresponding to the customer in register A (step S112). Subsequently, the second storage unit 216 stores the priority rank of the bug, which is associated with the frequency and priority of the bug corresponding to the customer, in register B (step S113).

[0075] In step S114, the third determination unit 214 determines whether a customer report is required based on the customer report information included in the bug attribute information acquired by the acquisition unit 212 (step S114). If the third determination unit 214 determines that a customer report is not required based on the customer report information included in the bug attribute information acquired by the acquisition unit 212 (step S114: No), the process proceeds to step S117. On the other hand, if the third determination unit 214 determines that a customer report is required based on the customer report information included in the bug attribute information acquired by the acquisition unit 212 (step S114: Yes), the process proceeds to step S115.

[0076] In step S115, the first storage unit 215 stores the severity rank of the bug corresponding to the customer report in register A (step S115). Subsequently, the second storage unit 216 stores the priority rank of the bug, which is associated with the frequency and priority of the bug corresponding to the customer report, in register B (step S116).

[0077] In step S117, the first storage unit 215 stores the bug severity rank corresponding to the development company in register A (step S117). Subsequently, the second storage unit 216 stores the bug priority rank associated with the bug frequency and priority corresponding to the development company in register B (step S118). When at least one of steps S113, S116, and S118 is completed, the server 2 proceeds to process A.

[0078] Figure 21 is a flowchart showing an example of the processing flow executed by Server 2 according to this embodiment. The flowchart shown in Figure 21 shows the content of the processing that follows from Process A shown in Figure 20.

[0079] The third storage unit 217 stores the first point determined from register A, in which the first storage unit 215 stores the severity rank, and register B, in which the second storage unit 216 stores the priority rank, in register C (step S119). Next, the fourth storage unit 218 stores the point corresponding to the bug recovery method information included in the bug recovery method information, which has been acquired by the acquisition unit 212, in register D (step S120). Next, the fifth storage unit 219 stores the point corresponding to the occurrence frequency information included in the bug attribute information, which has been acquired by the acquisition unit 212, in register E (step S121).

[0080] Next, the sixth storage unit 220 stores a second point in register F, which is the product of the point stored in register D by the fourth storage unit 218 and the point stored in register E by the fifth storage unit 219 (step S122). Next, the seventh storage unit 221 stores a third point in register G, which corresponds to the management of software development in the management information included in the bug attribute information acquired by the acquisition unit 212 (step S123). Next, the eighth storage unit 222 stores a fourth point in register H, which corresponds to the adjustment point included in the bug attribute information acquired by the acquisition unit 212 (step S124).

[0081] Next, the calculation unit 223 sums up the points stored in registers C, F, G, and H to calculate priority points for determining the priority of bug fixes (step S125). Once step S125 is completed, server 2 finishes step S103 and proceeds to step S104 shown in Figure 19.

[0082] As described above, Server 2 according to one aspect of the present disclosure includes at least one processor configured to calculate priority points for determining the priority of bug fixes according to bug attribute information relating to the attributes of a bug, including bug fix method information relating to a bug fix method, and to output bug information relating to the bug corresponding to the priority points.

[0083] Furthermore, the processor adds up the first point associated with the severity rank information and priority rank information, the second point associated with the bug recovery method information and occurrence frequency information, the third point corresponding to the management information, and the fourth point corresponding to the adjustment point information as priority points, and outputs the bug information sorted in descending order of priority points. In addition, if the bug information does not have a deadline set for correcting the bug, the processor adds the deadline. Finally, if the priority points are eligible for automatic notification to the user, the processor automatically notifies the user of the bug information.

[0084] Furthermore, a terminal device 1 according to one aspect of this disclosure is a terminal device 1 that inputs and outputs bug information relating to bugs in software development, and comprises at least one processor configured to input bug attribute information relating to bug attributes, including bug recovery method information relating to a bug recovery method, and to output bug information relating to bugs corresponding to priority points for determining the priority of bug repair.

[0085] For example, in conventional software development, the point system used to prioritize bug fixes involves multiplying the bug's priority and severity, and then adding adjustment values ​​as needed to determine the points. However, the priority points in this disclosure, in addition to the conventional method, also include points corresponding to the bug recovery method, the frequency of bug occurrence, and management. Therefore, by making the priority points more detailed, the cases in which the same priority points are obtained are reduced, and the priority of bug fixes can be clearly defined. As a result, the priority of bug fixes can be clearly defined compared to conventional methods.

[0086] The embodiments described above can also be modified and implemented as appropriate by changing some of the configurations or functions of each of the devices described above. Therefore, several modifications of the embodiments described above will be described below as other embodiments. In the following, we will mainly describe the differences from the embodiments described above, and will omit detailed explanations of points that are common with what has already been described.

[0087] (First variation) For example, bug attribute information may include bug ratio information, which relates to the proportion of bugs in software development, and bug occurrence combination information, which relates to combinations of conditions under which bugs occur.

[0088] Figure 22 is a functional block showing an example of the functional configuration of Server 2 according to the first modified example. Server 2 includes a first determination unit 211, an acquisition unit 212, a second determination unit 213, a third determination unit 214, a first storage unit 215, a second storage unit 216, a third storage unit 217, a fourth storage unit 218, a fifth storage unit 219, a sixth storage unit 220, a seventh storage unit 221, an eighth storage unit 222, a calculation unit 223, a fourth determination unit 224, an addition unit 225, an issuing unit 226, a ninth storage unit 227, an output unit 228, a fifth determination unit 229, and a notification unit 230, in addition to a tenth storage unit 231 and an eleventh storage unit 232.

[0089] The tenth storage unit 231 stores a fifth point determined from bug ratio information relating to the proportion of bugs in software development in register J. Specifically, the tenth storage unit 231 stores a fifth point corresponding to the proportion of bugs in software development in the bug ratio information included in the bug attribute information acquired by the acquisition unit 212 in register J.

[0090] The 11th storage unit 232 stores the 6th point, determined from the bug occurrence combination information relating to the combination of bug occurrence conditions, in register K. Specifically, the 11th storage unit 232 stores the 6th point in register K that corresponds to the combination of bug occurrence conditions in the bug occurrence combination information included in the bug attribute information acquired by the acquisition unit 212. The 5th point stored in register J and the 6th point stored in register K will be explained using Figure 23.

[0091] Figure 23 is a schematic diagram illustrating the fifth point stored in register J and the sixth point stored in register K in the first modified example. Table T7 shown in Figure 23 is a table that associates the percentage of the total number of bugs with the fifth point. For example, if the percentage of the total number of bugs is "30%", the fifth point will be "300". Table T8 shown in Figure 23 is a table that associates the number of combinations of bug occurrence conditions with the fifth point. For example, if the number of combinations is "less than 3", the sixth point will be "0". Note that the fifth point shown in Table T7 and the sixth point shown in Table T8 may be set according to the software development.

[0092] Returning to Figure 22, the explanation continues. The calculation unit 223 sums up the points stored in registers C, F, G, H, J, and K to calculate priority points for determining the priority of bug fixes. Specifically, the calculation unit 223 sums up the first point stored in register C by the third storage unit 217, the second point stored in register F by the sixth storage unit 220, the third point stored in register G by the seventh storage unit 221, the fourth point stored in register H by the eighth storage unit 222, the fifth point stored in register J by the tenth storage unit 231, and the sixth point stored in register K by the eleventh storage unit 232 to calculate priority points for determining the priority of bug fixes.

[0093] Figure 24 is a flowchart showing an example of the processing flow executed by Server 2 in the first modified example. Steps S119 to S124 shown in Figure 24 are the same as steps S119 to S124 shown in Figure 21, so their explanation is omitted.

[0094] In step S131, the tenth storage unit 231 stores the fifth point, determined from bug ratio information relating to the proportion of bugs in software development, in register J (step S131). In step S132, the eleventh storage unit 232 stores the sixth point, determined from bug occurrence combination information relating to combinations of bug occurrence conditions, in register K (step S132). In step S133, the calculation unit 223 sums up the points stored in registers C, F, G, H, J, and K, and calculates priority points to determine the priority order for fixing bugs.

[0095] As explained above, the bug attribute information relating to the first modified example includes bug count ratio information relating to the proportion of bugs in software development, and bug occurrence combination information relating to the combination of conditions under which bugs occur, and the priority points include a fifth point corresponding to the bug count ratio information and a sixth point corresponding to the bug occurrence combination information.

[0096] (Second variation) For example, the priority points may include a seventh point corresponding to the contact information regarding the recipient of the bug report and the customer report information regarding the customer report of the bug.

[0097] Figure 25 is a functional block showing an example of the functional configuration of Server 2 according to the second modified example. Server 2 includes a first determination unit 211, an acquisition unit 212, a second determination unit 213, a third determination unit 214, a first storage unit 215, a second storage unit 216, a third storage unit 217, a fourth storage unit 218, a fifth storage unit 219, a sixth storage unit 220, a seventh storage unit 221, an eighth storage unit 222, a calculation unit 223, a fourth determination unit 224, an addition unit 225, an issuance unit 226, a ninth storage unit 227, an output unit 228, a fifth determination unit 229, and a notification unit 230, in addition to a twelfth storage unit 233.

[0098] The 12th storage unit 233 stores the 7th point, determined from the report information regarding the recipient of the bug report, in register I. Specifically, the 12th storage unit 233 stores the 7th point corresponding to the recipient of the bug report included in the report information of the bug attribute information in register I. For example, if the 2nd determination unit 213 determines that the recipient of the report included in the report information of the bug attribute information is a customer, the 12th storage unit 233 stores the 7th point corresponding to the customer of the report information included in the report information of the bug attribute information in register I.

[0099] Furthermore, for example, if the second determination unit 213 determines that the target of the bug report information included in the bug attribute information is not a customer, and the third determination unit 214 determines that a customer report is required based on the customer report information included in the bug attribute information, the 12th storage unit 233 stores the 7th point corresponding to the customer report in the customer report information included in the bug attribute information in register I.

[0100] Figure 26 is a schematic diagram illustrating the seventh point stored in register I in the second modified example. Table T9 shown in Figure 26 is a table that associates the importance of the identified item with the seventh point. For example, if the importance is "Customer," the seventh point will be "10,000." Furthermore, the seventh point is set in the following order of increasing importance: Customer (First User), Development company requiring customer reporting (Shared) (Second User), and Development company not requiring customer reporting (Internal) (Second User, No Customer Report).

[0101] Returning to Figure 25, the explanation continues. The third storage unit 217 stores the first point, determined from register A where the severity rank is stored in the first storage unit 215, and register B where the priority rank is stored in the second storage unit 216, in register C. Here, the first point to be stored in register C will be explained using Figure 27.

[0102] Figure 27 is a schematic diagram illustrating the first point stored in register C in the second modified example. Table T10 shown in Figure 27 is a table that shows points corresponding to severity rank information related to the severity rank associated with the severity of the bug, and priority rank information related to the priority of the bug associated with the reporting information and customer report information, and the priority rank of the bug associated with the frequency of occurrence. For example, if the severity is "A", the severity rank is "3", and if the frequency of occurrence is "Always", the priority rank is "1", and the points are "108,000". Also, if the severity is "B", the severity rank is "4", and if the frequency of occurrence is "Immediate", the priority rank is "2", and the points are "62,000". Note that the points shown in Table T10 may be set according to the software development.

[0103] Returning to Figure 25, the explanation continues. The calculation unit 223 sums up the points stored in registers C, F, G, H, and I to calculate priority points for determining the priority of bug fixes. Specifically, the calculation unit 223 sums up the first point stored in register C by the third storage unit 217, the second point stored in register F by the sixth storage unit 220, the third point stored in register G by the seventh storage unit 221, the fourth point stored in register H by the eighth storage unit 222, and the seventh point stored in register I by the twelfth storage unit 233 to calculate priority points for determining the priority of bug fixes.

[0104] Figure 28 is a flowchart showing an example of the processing flow executed by Server 2 in the second modified example. Steps S111 to S118 shown in Figure 28 are the same as steps S111 to S118 shown in Figure 20, so their explanation is omitted.

[0105] In step S141, the 12th storage unit 233 stores the 7th point corresponding to the customer in the bug attribute information included in the bug attribute information into register I. In step S142, the 12th storage unit 233 stores the 7th point corresponding to the customer report in the customer report information included in the bug attribute information into register I. In step S143, the 12th storage unit 233 stores the 7th point corresponding to the development company in the bug attribute information included in the bug attribute information into register I.

[0106] Figure 29 is a flowchart showing an example of the processing flow executed by Server 2 in the second modified example. Steps S119 to S124 shown in Figure 29 are the same as steps S119 to S124 shown in Figure 21, so their explanation is omitted.

[0107] In step S144, the calculation unit 223 sums up the points stored in registers C, F, G, H, and I, and calculates priority points to determine the priority order for fixing bugs.

[0108] As explained above, the priority points for the second modification include the seventh point corresponding to the information pointed out, and the seventh point is set in the following order: first user, second user requiring customer reporting, and second user not requiring customer reporting.

[0109] (Third variation) For example, if Server 2 has bug information with a high calculated priority point value and a short remaining period until the deadline for bug fixes, it may add a predetermined number of points to that priority point value.

[0110] Figure 30 is a functional block showing an example of the functional configuration of Server 2 according to the third modified example. Server 2 includes a first determination unit 211, an acquisition unit 212, a second determination unit 213, a third determination unit 214, a first storage unit 215, a second storage unit 216, a third storage unit 217, a fourth storage unit 218, a fifth storage unit 219, a sixth storage unit 220, a seventh storage unit 221, an eighth storage unit 222, a calculation unit 223, a fourth determination unit 224, an addition unit 225, an issuance unit 226, a ninth storage unit 227, an output unit 228, a fifth determination unit 229, and a notification unit 230, in addition to a sixth determination unit 234, a seventh determination unit 235, and an addition unit 236.

[0111] The sixth determination unit 234 determines whether there is bug information with a high priority point and a short remaining period until the bug fix deadline. Specifically, the sixth determination unit 234 determines whether there is bug information with a high priority point calculated by the calculation unit 223 and a short remaining period until the bug fix deadline. The predetermined deadline is set according to the priority point and the fix deadline.

[0112] The seventh determination unit 235 determines whether there has been no progress in the status of the bug information for a certain period of time. Specifically, if the sixth determination unit 234 determines that there is bug information with a high priority point and a short remaining period of days until the deadline for bug countermeasures, the seventh determination unit 235 determines whether there has been no progress in the status of the bug information for a certain period of time.

[0113] The addition unit 236 adds a predetermined number of points to the priority points corresponding to the bug information. Specifically, when the seventh determination unit 235 determines that there has been no progress in the status of the bug information for a certain period of time, the addition unit 236 adds a predetermined number of points to the priority points corresponding to the bug information. The predetermined number of points is set according to the priority points.

[0114] Figure 31 is a flowchart showing an example of the processing flow performed by Server 2 in the third modified example. The processing in Figure 31 concerns the processing performed by Server 2 after calculating the priority points.

[0115] The sixth determination unit 234 determines whether there is any bug information with a high priority point value calculated by the calculation unit 223 and with a short remaining period of days until the bug fix deadline (step S151). If the sixth determination unit 234 determines that there is no bug information with a high priority point value and a short remaining period of days until the bug fix deadline (step S151: No), the server 2 terminates this process. On the other hand, if the sixth determination unit 234 determines that there is bug information with a high priority point value and a bug fix deadline earlier than the predetermined deadline (step S151: Yes), the process proceeds to step S152.

[0116] In step S152, the seventh determination unit 235 determines whether there has been no progress in the bug information status for a certain period of time (step S152). If the seventh determination unit 235 determines that there has been progress in the bug information status for a certain period of time (step S152: No), the server 2 terminates this process. On the other hand, if the seventh determination unit 235 determines that there has been no progress in the bug information status for a certain period of time (step S152: Yes), the process proceeds to step S153.

[0117] In step S153, the addition unit 236 adds a predetermined number of points to the priority points corresponding to the bug information (step S153). When step S153 is completed, the server 2 terminates this process.

[0118] As explained above, in the third modified example, the processor of Server 2 adds a predetermined number of points to the priority points if there is bug information with a high priority point value and a short remaining period until the deadline for bug fix. This allows Server 2 to set a higher priority for bugs that are behind schedule. As a result, the priority of bug fixes can be made clearer compared to the conventional method.

[0119] (Hardware configuration) Figure 32 shows an example of the hardware configuration of the information processing system 100 according to the embodiment and modified example. The terminal device 1 and server 2 of the information processing system 100 according to the embodiment and modified example are interconnected by a bus 45, etc., and the processor 41, main memory 42, auxiliary memory 43, and device I / F 44 are connected to each other, and the hardware configuration is that of a normal computer.

[0120] The processor 41 is, for example, a CPU, and is an arithmetic unit that controls the terminal device 1 and server 2 of the above embodiment and its modified form. The main memory 42 is, for example, RAM, and stores data necessary for various processes performed by the processor 41. The auxiliary memory 43 is, for example, ROM, and stores programs and the like that realize information processing performed by the processor 41.

[0121] The device interface 44 is an interface for various inputs / outputs and / or communications between terminal device 1 and server 2. For example, the device interface 44 may include a communication interface configured to allow connection of an external communication device that communicates with terminal device 1 and server 2, or configured to function as such a communication device.

[0122] As for communication interfaces, wired communication circuits such as USB (Universal Serial Bus®) and Ethernet®, or wireless communication circuits compatible with various standards such as 3G, LTE, 4G, 5G, 6G, Wi-Fi®, and Bluetooth® can be used as appropriate.

[0123] In the above embodiment and modified versions of the terminal device 1 and server 2, the processor 41 reads a program from the auxiliary storage device 43 onto the main storage device 42 and executes it, thereby realizing each of the above-mentioned functional units on the computer.

[0124] Furthermore, the programs for executing the above-mentioned processes performed by the terminal device 1 and server 2 in the above-described embodiment and modified version may be stored in an HDD (hard disk drive). Alternatively, the programs for executing the above-mentioned processes performed by the terminal device 1 and server 2 in the above-described embodiment and modified version may be pre-installed and provided in an auxiliary storage device 43.

[0125] Furthermore, the program for executing the above-mentioned processing performed by the terminal device 1 and server 2 of the above-described embodiment and its modifications may be provided as a computer program product by being stored in an installable or executable file format on a computer-readable storage medium such as a CD-ROM, CD-R, memory card, DVD (Digital Versatile Disk), or flexible disk (FD). Alternatively, the program for executing the above-mentioned information processing performed by the terminal device 1 and server 2 of the above-described embodiment and its modifications may be stored on a computer connected to a network such as the Internet and provided by being downloaded via the network. Alternatively, the program for executing the above-mentioned information processing performed by the terminal device 1 and server 2 of the above-described embodiment and its modifications may be provided or distributed via a network such as the Internet.

[0126] According to at least one embodiment described above, the priority of bug fixes can be clarified compared to conventional methods.

[0127] While several embodiments of the present invention have been described, these embodiments are presented as examples only and are not intended to limit the scope of the invention. These embodiments can be carried out in a variety of other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the claims and their equivalents. [Explanation of Symbols]

[0128] 1. Terminal device 2 servers 11 Input section 12 Display section 41 processors 42 Main storage 43 Auxiliary storage device 44 Equipment I / F 45 bus 100 Information Processing Systems 211 1st Judgment Department 212 Acquisition Department 213 Second Judgment Department 214 Third Judgment Section 215 First storage unit 216 Second storage unit 217 Third Hangar 218 Fourth Hangar 219 Fifth Hangar 220 Sixth Hangar 221 Hangar 7 222 Hangar No. 8 223 Calculation Section 224 4th Judgment Section 225 Addition part 226 Publishing Department 227 Hangar No. 9 228 Output section 229 5th Judgment Section 230 Notification Department 231 Tenth Hangar 232 Hangar No. 11 233 Hangar No. 12 234 6th Judgment Department 235 7th Judgment Department 236 Addition section

Claims

1. An information processing device for managing bugs in software development, Based on the bug attribute information relating to the attributes of the bug, which includes bug recovery method information relating to the bug recovery method, priority points are calculated to determine the priority for fixing the bug. The system comprises at least one processor configured to output bug information relating to the bug corresponding to the priority point, Information processing device.

2. The points corresponding to the bug recovery method information are set lower the easier it is to recover from the bug state. The information processing apparatus according to claim 1.

3. The aforementioned bug attribute information includes information about the recipient of the report that pointed out the bug, and customer report information about the customer report of the bug information. The parties mentioned above are the first user who commissioned the software development and the second user who undertook the software development. The customer reporting information includes whether the second user requires the first user to submit the customer report. The information processing apparatus according to claim 2.

4. The bug attribute information includes severity information relating to the severity of the bug, frequency information relating to the frequency of occurrence of the bug, priority information relating to the priority of the bug, severity rank information relating to the severity of the bug associated with the severity, the reporting information, and the customer report information, priority rank information relating to the priority of the bug associated with the reporting information and the customer report information, and the priority rank of previous bugs associated with the frequency of occurrence, management information relating to the management of the software development, and adjustment point information relating to adjustment points for adjusting the priority points. The information processing apparatus according to claim 3.

5. The processor sums the first point associated with the severity rank information and the priority rank information, the second point associated with the bug recovery method information and the occurrence frequency information, the third point corresponding to the management information, and the fourth point corresponding to the adjustment point information as the priority points, and outputs the bug information sorted in descending order of priority points. The information processing apparatus according to claim 4.

6. The bug attribute information includes bug ratio information relating to the proportion of the number of bugs in the software development, and bug occurrence combination information relating to the combination of conditions under which the bug occurs. The aforementioned priority points include a fifth point corresponding to the bug count ratio information and a sixth point corresponding to the bug occurrence combination information. The information processing apparatus according to claim 5.

7. The aforementioned priority points include a seventh point corresponding to the aforementioned information on the identified location and the aforementioned customer report information, The seventh point is set in the following order: first user, second user who is required to submit a customer report, and second user who is not required to submit a customer report. The information processing apparatus according to claim 5.

8. The processor adds a deadline for implementing a fix for the bug if the bug information does not already contain such a deadline. The information processing apparatus according to claim 1.

9. The processor, if it has bug information with a high priority point and a short remaining period until the deadline for corrective action, adds a predetermined point to the priority point. The information processing apparatus according to claim 8.

10. The processor, if the priority point is subject to automatic notification to the user, will automatically notify the user of the bug information. The information processing apparatus according to claim 1.

11. An information processing method executed in an information processing device for managing bugs in software development, Based on the bug attribute information relating to the attributes of the bug, which includes bug recovery method information relating to the bug recovery method, priority points are calculated to determine the priority for fixing the bug. This includes outputting bug information relating to the bug corresponding to the aforementioned priority point, Information processing methods.

12. A computer that realizes an information processing device for managing bugs in software development, Based on the bug attribute information relating to the attributes of the bug, which includes bug recovery method information relating to the bug recovery method, priority points are calculated to determine the priority for fixing the bug. To perform the output of bug information relating to the bug corresponding to the aforementioned priority point, Information processing program.

13. A terminal device that inputs and outputs bug information related to bugs in software development, The bug attribute information relating to the attributes of the bug, including bug recovery method information relating to the bug recovery method, is input. The system comprises at least one processor configured to output bug information relating to the bug corresponding to a priority point for determining the priority of fixing the bug, Terminal device.

Images