Method and system for reducing instability when upgrading software

• US 10,198,255 B2
• Filed: 08/29/2016
• Issued: 02/05/2019
• Est. Priority Date: 07/09/2013
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Higginson, Antony, Greenough, Michael, Trifu, Catalin, Masterson, John, Fagan, Jean
• Primary Examiner(s): Sough, S.
• Assistant Examiner(s): Sough, H.
• Application Number:
  US15/250,522
• Publication Number:
  US 20160364229A1
• Time in Patent Office: 890 Days
• Field of Search: 717100-178
• CPC Class Codes: G06F 11/3414 Workload generation, e.g. scripts, playback
• CPC Class Codes: G06F 11/3466 Performance evaluation by tracing or monitoring
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software
• CPC Class Codes: G06F 16/24578 using ranking
• CPC Class Codes: G06F 16/248 Presentation of query results
• CPC Class Codes: G06F 2201/875 Monitoring of systems including the internet
• CPC Class Codes: G06F 8/65 Updates security arrangements therefor G06F21/57
• CPC Class Codes: H04L 43/04 Processing captured monitoring data, e.g. for logfile generation
• CPC Class Codes: H04L 43/067 using time frame reporting

Abstract

A system and a method of rating software bugs using a bug scoring and tracking system is presented. The system and method may use automated scoring of the bugs to determine the impact of the bug. The system and method may connect to one or more databases to determine the extent of the deployment of the software, the impact of the bug, and/or the history of the bug. Scoring is used to prioritize the bugs and the scoring is extensible and adjustable allowing easy addition of new parameters and allowing the system to be modified for different bug types, software, or customers.

Claims

1. A system comprising:

one or more processors; and

a memory communicatively coupled with and readable by the one or more processors and having stored therein a series of instructions which, when executed by the one or more processors, cause the one or more processors to;

receive a software bug report, the software bug report having a data portion describing a plurality of software bugs, wherein the data portion includes information describing at least one effect of at least one software bug of the plurality of software bugs;

determine at least one code base associated the plurality of software bugs based at least in part on the at least one effect, wherein the at least one code base is a software code containing a coding error causing the at least one effect;

process a customer preference, the customer preference defining a set of parameters that indicate preferences for rating the plurality of software bugs;

generate a first set of bug scores at least in part by, for each software bug of the plurality of software bugs;

calculating a respective set of parameter scores in relation to the respective software bug, wherein the respective set of parameter scores correspond to a respective quantification of the set of parameters defined in the customer preference; and

computing a respective bug score based at least in part on the respective set of parameter scores;

process first data associated with a patch, including information regarding a set of software bugs addressed by the patch, wherein the set of software bugs corresponds at least in part to the plurality of software bugs;

process second data for the set of software bugs addressed by the patch, and determine a second set of bug scores for the set of software bugs, wherein the second set of bug scores is different from the first set of bug scores;

determine a first priority for the patch based at least in part on the second set of bug scores; and

generate a first patch report with a first prioritization of the patch, the first prioritization based at least in part on the first priority determined.

2. The system of claim 1, wherein the series of instructions further cause the one or more processors to:

generate a prioritized list of patches based at least in part on the first set of bug scores;

wherein the generating the first patch report is based at least in part on the prioritized list of patches, and the first patch report indicates a respective prioritization of each patch of the prioritized list of patches.

3. The system of claim 2, wherein the series of instructions further cause the one or more processors to:

process a second customer preference, the second customer preference defining a second set of parameters that indicate different preferences for rating the plurality of software bugs;

generate a third set of bug scores based at least in part on the second customer preference; and

determine a second priority for the patch based at least in part on the third set of bug scores, wherein the second priority is different from the first priority.

4. The system of claim 2, wherein the series of instructions further cause the one or more processors to:

assign the first priority to the patch as the patch is remotely deployed via a network to a remote target system.

5. The system from claim 4, wherein the series of instructions further cause the one or more processors to:

deploy the patch from a server system to the remote target system via a portal of the server system and a gateway installed at a datacenter comprising the remote target system.

6. The system of claim 5, wherein the series of instructions further cause the one or more processors to:

determine a highest bug score of the second set of bug scores;

assign the highest bug score to the patch;

identify the patch for installation based at least in part on the highest bug score; and

facilitate exposing the highest bug score via the portal.

7. The system of claim 1, wherein the respective set of parameter scores include one or more of:

a deployment parameter score, wherein the deployment parameter score summarizes a number of times the code base has been deployed;

an impact parameter score, wherein the impact parameter score summarizes a severity of the at least one effect of the at least one software bug;

a related bug parameter score, wherein the related bug parameter score summarizes a number of bugs related to the at least one software bug;

or

a technology parameter score, wherein the technology parameter score summarizes an importance of the code base.

8. The system of claim 1, wherein the series of instructions further cause the one or more processors to:

determine a second priority for the patch based at least in part on a third set of bug scores, wherein the second priority is different from the first priority; and

generate a second patch report with a second prioritization of the patch, the second prioritization based at least in part on the second priority determined, wherein the first patch report is different from the second patch report.

9. A method comprising:

receiving a software bug report, the software bug report having a data portion describing a plurality of software bugs, wherein the data portion includes information describing at least one effect of at least one software bug of the plurality of software bugs;

determining at least one code base associated the plurality of software bugs based at least in part on the at least one effect, wherein the at least one code base is a software code containing a coding error causing the at least one effect;

processing a customer preference, the customer preference defining a set of parameters that indicate preferences for rating the plurality of software bugs;

generating a first set of bug scores at least in part by, for each software bug of the plurality of software bugs;

calculating a respective set of parameter scores in relation to the respective software bug, wherein the respective set of parameter scores correspond to a respective quantification of the set of parameters defined in the customer preference; and

computing a respective bug score based at least in part on the respective set of parameter scores;

processing first data associated with a patch, including information regarding a set of software bugs addressed by the patch, wherein the set of software bugs corresponds at least in part to the plurality of software bugs;

processing second data for the set of software bugs addressed by the patch, and determine a second set of bug scores for the set of software bugs, wherein the second set of bug scores is different from the first set of bug scores;

determining a first priority for the patch based at least in part on the second set of bug scores; and

generating a patch report with a first prioritization of the patch, the first prioritization based at least in part on the first priority determined.

10. The method of claim 9, further comprising:

generating a prioritized list of patches based at least in part on the first set of bug scores;

wherein the generating the patch report is based at least in part on the prioritized list of patches, and the patch report indicates a respective prioritization of each patch of the prioritized list of patches.

11. The method of claim 10, further comprising:

processing a second customer preference, the second customer preference defining a second set of parameters that indicate different preferences for rating the plurality of software bugs;

generating a third set of bug scores based at least in part on the second customer preference; and

determining a second priority for the patch based at least in part on the third set of bug scores, wherein the second priority is different from the first priority.

12. The method of claim 10, further comprising:

assigning the first priority to the patch as the patch is remotely deployed via a network to a remote target system.

13. The method of claim 12, further comprising:

deploying the patch from a server system to the remote target system via a portal of the server system and a gateway installed at a datacenter comprising the remote target system.

14. The method of claim 13, further comprising:

determining a highest bug score of the second set of bug scores;

assigning the highest bug score to the patch;

identifying the patch for installation based at least in part on the highest bug score; and

facilitate exposing the highest bug score via the portal.

15. The method of claim 9, wherein the respective set of parameter scores include one or more of:

a deployment parameter score, wherein the deployment parameter score summarizes a number of times the code base has been deployed;

an impact parameter score, wherein the impact parameter score summarizes a severity of the at least one effect of the at least one software bug;

a related bug parameter score, wherein the related bug parameter score summarizes a number of bugs related to the at least one software bug;

or

a technology parameter score, wherein the technology parameter score summarizes an importance of the code base.

16. One or more non-transitory, processor-readable media storing thereon instructions, which, when executed by one or more processors, cause the one or more processors to:

receive a software bug report, the software bug report having a data portion describing a plurality of software bugs, wherein the data portion includes information describing at least one effect of at least one software bug of the plurality of software bugs;

determine at least one code base associated the plurality of software bugs based at least in part on the at least one effect, wherein the at least one code base is a software code containing a coding error causing the at least one effect;

process a customer preference, the customer preference defining a set of parameters that indicate preferences for rating the plurality of software bugs;

generate a first set of bug scores at least in part by, for each software bug of the plurality of software bugs;

calculating a respective set of parameter scores in relation to the respective software bug, wherein the respective set of parameter scores correspond to a respective quantification of the set of parameters defined in the customer preference; and

computing a respective bug score based at least in part on the respective set of parameter scores;

process first data associated with a patch, including information regarding a set of software bugs addressed by the patch, wherein the set of software bugs corresponds at least in part to the plurality of software bugs;

process second data for the set of software bugs addressed by the patch, and determine a second set of bug scores for the set of software bugs, wherein the second set of bug scores is different from the first set of bug scores;

determine a first priority for the patch based at least in part on the second set of bug scores; and

generate a patch report with a first prioritization of the patch, the first prioritization based at least in part on the first priority determined.

17. The one or more non-transitory, processor-readable media of claim 16, wherein the instructions further cause the one or more processors to:

generate a prioritized list of patches based at least in part on the first set of bug scores;

wherein the generating the patch report is based at least in part on the prioritized list of patches, and the patch report indicates a respective prioritization of each patch of the prioritized list of patches.

18. The one or more non-transitory, processor-readable media of claim 16, wherein the instructions further cause the one or more processors to:

process a second customer preference, the second customer preference defining a second set of parameters that indicate different preferences for rating the plurality of software bugs;

generate a third set of bug scores based at least in part on the second customer preference; and

determine a second priority for the patch based at least in part on the third set of bug scores, wherein the second priority is different from the first priority.

19. The one or more non-transitory, processor-readable media of claim 18, wherein the instructions further cause the one or more processors to:

assign the first priority to the patch as the patch is remotely deployed via a network to a remote target system.

20. The one or more non-transitory, processor-readable media of claim 19, wherein the instructions further cause the one or more processors to:

deploy the patch from a server system to the remote target system via a portal of the server system and a gateway installed at a datacenter comprising the remote target system.