CN105580032A

CN105580032A - Method and system for reducing instability when upgrading software

Info

Publication number: CN105580032A
Application number: CN201480035255.XA
Authority: CN
Inventors: A·希金森; M·格里诺; C·特里夫; J·马斯特森; J·费根
Original assignee: Oracle International Corp
Current assignee: Oracle International Corp
Priority date: 2013-07-09
Filing date: 2014-07-02
Publication date: 2016-05-11
Anticipated expiration: 2034-07-02
Also published as: EP3020010A1; US20150019564A1; CN107729252A; CN105580032B; CN107729252B; US9442983B2; US10198255B2; US20150019706A1; US20160364229A1; WO2015006132A1; US9491072B2

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.

Description

For reducing instable method and system during upgrade software

To the cross reference of related application

The application is relevant to following jointly co-pending, commonly assigned U.S. Patent application: synchronously submitted to by Davis, name is called the U.S. Patent application No.13/938 of " CONSOLIDATIONPLANNINGSERVICEFORSYSTEMSMIGRATION ", 061 (agency case 88325-870368 (137700US)); Synchronously submitted to by Davis, the U.S. Patent application No.13/938 that name is called " MIGRATIONSERVICESFORSYSTEMS ", 066 (agency case 88325-870369 (137800US)); Synchronously submitted to by Higginson, the U.S. Patent application No.13/937 that name is called " DATABASEMODELINGANDANALYSIS ", 885 (agency case 88325-870374 (137900US)); Synchronously submitted to by Higginson, the U.S. Patent application No.13/937 that name is called " AUTOMATEDDATABASEMIGRATIONARCHITECTURE ", 868 (agency case 88325-870373 (138000US)); Synchronously submitted to by Raghunathan etc., the U.S. Patent application No.13/937 that name is called " CLOUDSERVICESLOADTESTINGANDANALYSIS ", 344 (agency case 88325-870381 (138100US)); Synchronously submitted to by Raghunathan etc., name is called the U.S. Patent application No.13/937 of " CLOUDSERVICESPERFORMANCETUNINGANDBENCHMARKING ", 483 (agency case 88325-870383 (138200US)); Synchronously submitted to by Buehne etc., name is called the U.S. Patent application No.13/937 of " SOLUTIONTOGENERATEASCRIPTSETFORANAUTOMATEDDATABASEMIGRAT ION ", 988 (agency case 88325-870382 (138300US)); Synchronously submitted to by Buehne etc., the U.S. Patent application No.13/937 that name is called " ONLINEDATABASEMIGRATION ", 545 (agency case 88325-870410 (138400US)); Synchronously submitted to by Buehne etc., the U.S. Patent application No.13/937 that name is called " DYNAMICMIGRATIONSCRIPTMANAGEMENT ", 486 (agency case 88325-870409 (138500US)); And to submit to by Masterson etc. is synchronous, name is called the U.S. Patent application No.13/937 of " ADVANCEDCUSTOMERSUPPORTSERVICES – ADVANCEDSUPPORTCLOUDPORTAL ", 970 (agency case 88325-870401 (138600US)), whole disclosures of each patented claim are wherein merged in herein by reference.

Technical field

The present invention relates generally to database, and relate more specifically to the apparatus and method of tracking for providing software error, maintenance and sequencing tool.

Background technology

Modern Database Systems are very complicated, and it is made up of many assemblies and is normally used for performance-sensitive operation.Along with the increase of the complicacy of software application, the quantity of mistake (bug) may increase.The scope of software error can from having very little impact or not having influential inapparent fault to serious safety or performance deficiency.It is important for following the tracks of these mistakes guarantee the most serious mistake to obtain priority and to upgrade applicable system in time with reparation or patch.

Summary of the invention

By using system and method described herein, can make software error and tracking, the prioritization of renewal that are associated with mistake and sorting more reliably, more fast and more accurate.Propose mistake in score and tracker carrys out the system and method for software mistake.Described system and method can use the automatic score of mistake to determine the impact of mistake.Score can be used to wrong prioritization, and score can be easily extensible and adjustable, allows to add new argument easily, and allows to modify to system for different type of errors, software or client.

In certain embodiments, for comprising one or more processor to the system of wrong prioritization, and with the storer that couples of described one or more processor communication ground, described storer can be read by described one or more processor, and storer stores a series of instruction, when described instruction is performed by described one or more processor, make described one or more processor can pass through to perform series of steps to software error prioritization.Described step can comprise reception software error report, and described software error report can have the data division describing software error, and described data division can comprise the information of at least one impact describing software error.Another step can determine the codebases (codebase) of software error at least in part based on the impact of software error, and receive customer priorities further, customer priorities can define one group and describe the parameter of customer priorities for the importance of software mistake.Step calculates the one group parameter score (score) relevant to software error when can also be included in not artificial input, and described one group of parameter score can quantize this group parameter defined in customer priorities.In addition, the grouping to described one group of parameter score can be performed, be divided into first group and second group, after this, use first group and second group of miscount score.The error reporting that the priority with software error divides can be generated, and priority divides based on wrong score.

In certain embodiments, described one group of parameter score can comprise deployment parameters score.Deployment parameters score can summarize the number of times that codebases is deployed.Described one group of parameter score can also comprise the technical parameter score of the importance of the affecting parameters score of the seriousness of the impact of summarizing software error, the relevant error parameter score summarizing the quantity of the mistake relevant to software error and summary codebases.Can by getting to the parameter score of first group and second group the wrong score that inner product carrys out software for calculation mistake, and priority divide can based on the relative value of wrong score compared with the score of other mistakes.

Accompanying drawing explanation

With reference to the following drawings, the further understanding of essence to various embodiment and advantage can be realized.

Fig. 1 illustrates the block diagram of the embodiment of wrong scoring system;

Fig. 2 illustrates an embodiment of the method being used for generation error score;

Fig. 3 illustrates an embodiment of the method for the priority for determining mistake;

Fig. 4 illustrates an embodiment of the method for the priority for determining software patch;

Fig. 5 illustrates the embodiment of supporting platform system;

Fig. 6 illustrates the embodiment of computer system.

Embodiment

Mistake (bug) can be certain defect in software application, and it makes the whole of software application or certain section failure or performs with certain accident or unexpected mode.Many mistakes are difficult to found and keep hiding until found by terminal user.The scope of software error can from having very little impact or not having influential inapparent fault to serious safety or performance deficiency.

Usually (if not impossible) is difficult to large and repair all by the mistake reported in the system of complexity.Developer and software engineer only may have the resource of the medium and small subset of mis repair.Software error may need to be divided priority to guarantee, the subset of the mistake corresponding with mistake the most serious concerning system and/or client obtains repairing or being first repaired.

After software error is repaired, follows the tracks of with the wrong software upgrading that is associated or patch and can be important to its prioritization.About the type of client by the renewal of installation, client can be selectively.Partly due to the complicacy of system, therefore software patch or renewal self may introduce new mistake by them sometimes, and the mistake that new mistake may solve than original mistake or their intentions is more serious.Software upgrading needs to restart or the operation of Break-Up System or database sometimes, and this may the business operation of broken clients.Can be used to determine whether the range of selection of time when being employed, deployment or renewal will be deployed by patch by system manager to patch or software upgrading prioritization.

Method and system that is some complexity, manual and/or subjectivity is usually directed to the tracking of software error and the renewal that is associated with mistake, prioritization and sorting.In some cases, the order that mistake obtains repairing can based on the degree of difficulty of each mistake or complicacy.First some easily solve, have the mistake of less impact can be repaired, and other more grave error due to their complicacy, to their reparation may not be developed in time person postpone.Equally, the importance of the mistake that can be perceived based on individual by keeper or developer, subjectively distributes high priority to some mistakes.Everyone or developer can have the different know-how in the deployment characteristics of system, software or software, thus cause inconsistent sequence and priority to divide.Such as, in some cases, for the software of deployment with larger amt, it can be desirable for distributing high priority to the mistake affecting this software.Even other mistake of relatively low level and its not in any one separate payment (if being deployed in a large amount of systems) causes significant impact, but this mistake may affect many clients, causes overall considerable influence.If a mistake may produce serious influence in any separate payment, and the software of this erroneous effects has less deployment, then it can be desirable for distributing relatively low priority to this mistake.Such as, for individual, deployment information may be difficult to access exactly.In the system of complexity, code section, module, plug-in unit and/or analog may only be deployed in the software of particular version, only for particular customer or may be reused in other functions of system, this makes the accurate evaluation that divides the priority of mistake complicated further.Therefore depend on and trace tool that is manual, that divide based on sequence and the priority of user is carried out to mistake may have inconsistent and incomplete sequence.

In one aspect, propose for the method to software error score and prioritization.The method can use the automatic score to mistake at least in part.The method can comprise and receives data to determine the scope of the deployment of software, the impact of mistake, the history etc. of mistake from one or more database.The method is easily extensible and customizable, allows to add new argument easily for score.For different type of errors, software version, client etc., mistake score and priority can be divided and modify.

For following the tracks of and evaluate dissimilar software error exactly, affecting different clients and the mistake of software package, mistake point system and the customization of system be associated and extensibility are important.Such as, some Software deployments may always be comprised in private network or privately owned cloud environment.In such deployment, because software may be exposed in the external world of malice never, therefore client may find that the mistake of the security damaging software or software errors are not so serious.These clients may find that the mistake of influential system performance is the most serious.Extendible mistake score and trace tool can be that client or developer are customizable, allow the priority division, score etc. that customize software error.Mistake score and trace tool can provide more than one score and sequence for each mistake.Each mistake can be associated with more than one score, priority, sequence etc.Each mistake can be associated with more than one score, and wherein each score can correspond to different software version, different client, supposition, software developer etc. about mistake.

Software error score can also be used to score to the patch relevant to each mistake and software upgrading and follow the tracks of with trace tool.By using method described herein at least in part, each software patch or software upgrading can be scored or are divided priority.Depend on the type etc. of client, software version, deployment, each patch and software upgrading can have more than one score, rank etc.When patch is deployed to each client, automatically can be associated with patch for the score of each patch or priority, only relevant to the system, preference, deployment etc. of client self priority can be analyzed to make each client.Based on sequence, client can make they self the decision about the selection of time of installing patch.

In certain embodiments, multiple score of each mistake and sequence can be combined the overall scores of the impact providing for mistake.A described overall scores can will the software developer of mis repair or keeper be used, to assess the impact of software errors on multiple client, deployment, software version etc. and priority.

Term used herein " mistake (bug) ", when relating to software, means the mistake of certain type in computer software programs or system, defect or fault.Software error can produce incorrect or unexpected result.In some systems, mistake can make system run in unexpected mode." mistake " can also be found in computer hardware, structure or system.Mistake in the manufacture or design of hardware can also cause incorrect or unexpected result at the run duration of hardware.Although the disclosure describes the score of software error and tracking, it being understood that method and system goes for the score of mistake to the other types of such as hard error or system mistake and so on and mistake.

Term used herein " patch ", when relating to software, is a pieces of software of the supported data being designed to reparation problem or upgrading computer program or program.Patch can be that scale-of-two is executable, source code, code revision etc.In the context of this application, patch can comprise software upgrading or the service pack of any type being designed to update software and mis repair.Patch can repair one or more mistake, and update software may other parts incoherent with mistake.Although the disclosure describes the score of software patch and tracking, it being understood that method and system goes for the score to the patch revolving the relevant other types such as (boardspin) to hardware update, plate.

Fig. 1 shows the high level block diagram of an embodiment for mistake score and trace tool.As shown in Figure 1, error reporting (BugReport) is supplied to instrument.Error reporting can stem from client, developer, error database etc.If mistake stems from client, then error reporting can comprise the description to accident behavior, the description to erroneous effects, description etc. to the form of expression.Error reporting can be received together with customer information (CustomerInformation), upgrade information (UpgradeInformation) and any system information (SystemInformation), customer information provides the details of customer priorities, upgrade information is relevant to client, and system information is relevant to reported mistake.In some cases, error reporting can stem from developer or internal entity and not stem from client.Error reporting can comprise the vicious particular code district of identified tool, fragment, file etc.Under these circumstances, customer information can be relevant to the estimation of error range, and upgrade information can be relevant to the codebases that mistake may affect with system information.Instrument can output error priority list (BugPrioritylist) and patching first level list (PatchPrioritylist), and described two lists can specific to each client, software version or system.The client that instrument can generate specific to each client reports (CustomerReport), and it can provide the state of the seriousness of each mistake be identified and/or provide and the state relevant to the solution of each mistake.Client's report can also comprise the problem or mistake that the priority of the patch relevant to each client and patch and patch solve.

With reference to figure 1, mistake score and trace tool comprise some assemblies and module; One or more data processor 112 (being also referred to as processor), scoring engine 113, storer 114, some databases (such as, disposing database 118, error database 119 and patch database 115).Input/output module 116 also has and carries out mutual suitable function with external data base 120 or other external data sources, and described external data base 120 or other external data sources can be scored by mistake and trace tool 110 or third party operate.

Scoring engine 113 can receive and collect from inside and outside data source, relevant to mistake data.Data can be used to calculate the parameter score relevant to each mistake.Then parameter score can be used to miscount score, and mistake score can be used to patch prioritization that is wrong and that be associated with mistake.

Dispose database 118 can comprise such as, the information relevant with activity with the deployment history of each software version, module, storehouse, script or code.Dispose database 118 and can comprise the code dependent statistics having downloaded or used actively particular version with how many clients.How the software that statistics can comprise each version is used actively, and comprises the information about software service how many users etc.For each deployment of software, database can comprise the relevant information of the details that is deployed system thereon with software.Such as, whether database can comprise instruction software and be comprised in private network or privately owned cloud, or whether software is exposed to the information in the middle of the public.Each record of disposing can have the information be associated with the preference of each client and each deployment, and this information is about the priority of sixty-four dollar question or mistake for the customer.Dispose data can comprise with the operation for each deployment the key and code of each software or code is initialised or the frequency that is performed is relevant information.In some are disposed, software only can be mounted and never be used by client, and therefore, although certain code can have larger deployment amount, but the impact disposed may be relatively little.Dispose database 118 to store all deployment informations or externally in different systems, store all deployment informations in the system identical with trace tool from score in this locality.

Dispose data can be stored in various different database.Some databases can comprise with the software of particular version or only belong to the relevant information of the Software deployment of particular customer.This information can spread all over multiple groups, development teams, the marketing or business department.Mistake score and trace tool can receive information by input/output module 116 from external data base 120.

Turn back to Fig. 1, mistake score and the error database 119 of trace tool 110 can comprise about to by the information of the relevant history of the mistake reported and data.When mistake is reported, by mistake in database 119, the attribute of the state of mistake and mistake can be recorded and tracked.Error database can comprise the information that maybe must grade of priority of the software version that may affect about the associated software code of reporting errors person, mistake, mistake and client, the symptom of mistake, relevant mistake, relevant software patch, state, history, the individual being designated solving error or related side, mistake.

Mistake score and the patch database 115 of trace tool 110 can comprise the information of history about relevant to patch and errors repair and data.When new patch and code reparation are developed, by using patch database 115, the state of patch and the attribute of patch can be recorded and tracked.The mistake that patch database can comprise about generating the associated software code of patch person, patch, patch is designed to repair, the information of history, patching first level etc. of the possible result of patch, relevant patch, deployment is installed.

The customer database 117 of mistake score and trace tool 110 can comprise the information about customer priorities and customer historical.Database can comprise the information of the preference about the business and the marketing activity that can reflect client.Preference can define the type of the mistake of the business operation that may damage client.Such as, be active in the client in financial market, the even minimum mistake of the security aspect of influential system may be considered as having high priority.

Mistake score and trace tool 110 can comprise scoring engine 113 and distribute to mistake for by score and priority.Sequence can be used to needing the error listing paid close attention to carry out priority division, and is used to the importance of trail-and-error.Scoring engine 113 can be configured to the score of generation error.Scoring engine can by use based on mathematical principle, wrong score is created to the analysis of the data be associated with mistake.Scoring engine 113 can provide repeating of miscount score and at least part of automatically method, thus reduces the risk of the mistake miscount priority caused due to human error or qualitative evaluation.

In an embodiment, scoring engine 113 can use the parameter from one or more data source must to assign to miscount score.Scoring engine can receive data from disposing database 118 or external data base 120 or other external data bases, generally spends relevant parameter score to determine or to estimate to wrong.Scoring engine can from the data source visit data of one or more this locality or outside to collect the information relevant to mistake.

Such as, dispose database by using, scoring engine can calculate deployment parameters score, and deployment parameters score can summarize the deployment data relevant to each mistake.Once the codebases relevant to each mistake is determined, then the deployment data for each mistake just can be obtained.Dispose data by using, the deployment parameters score for the code of erroneous effects can be calculated by instrument.Deployment parameters score can be calculated termly or be estimated.Mistake score and trace tool 110 can calculate deployment parameters score for each software, code section or code module.Score can be saved and be used to miscount and patch priority or evaluation in.Deployment parameters score for each software can be regularly updated based on the change of deployment characteristics.Deployment parameters score can monthly, quarterly, with the selection of time of great software metric tools and renewal be calculated only once relatively etc.

Similarly, one or more by what use in Local or Remote data source, scoring engine can calculate correlative code parameter score, this correlative code parameter score summarize relevant software metric tools quantity or may be associated by the code of erroneous effects the quantity of code snippet.Similar or relevant code may be subject to similar fault or the impact of mistake, and may represent the mistake of more broad range.Relevant error parameter score also can be calculated.Relevant error parameter score based on the data from error database 119, can summarize the quantity of relevant mistake.

In an embodiment, scoring engine can from local or external data base or data sources data, to determine or to estimate the parameter score relevant to the result of wrong impact and mistake.Scoring engine can receive the technology that is associated with the mistake information relevant with sub-component.Some codes can be given the evaluation of high importance, and any minimum mistake in this code can be identified important.Some code techniques relevant to GUI or other features such as can be identified or be rated as has small significance.Score instrument can based on the data computing technique parameter score received.

Can also with the seriousness for erroneous effects must assign to obtain mistake impact.The impact of mistake can be received together with the report to mistake.The impact of mistake can describe as one and/or evaluation is provided.Describe and evaluate the instruction that can provide influence degree, the scope of influence degree is lost to the temporarily malfunctioning of graphical user interface completely from what serve.The impact of mistake can be determined from the diagnostic system dump be associated with mistake.The impact of mistake middlely can be determined to the independence of mistake or automatically reproduce.In certain embodiments, can be described based on the oral or text from user or client by individual, manually input evaluation.For different systems and configuration, the impact of mistake can be different.Symptom for the mistake of different system configuration also can be determined and is assigned with a score.Mistake score and trace tool can distribute affecting parameters score and seriousness parameter score by usage data, and it summarizes impact and the seriousness data of mistake respectively.

Scoring engine 113 can comprise additional parameter, and this parameter or can affect uncorrelated with the technical elements of mistake.In an embodiment, scoring engine can receive about the marketing of the software product relevant to mistake, product age, business activity or the information of chance of being correlated with the specific products that mistake may affect.Such as, impact is publicizing and a mistake of the new software product of marketing energetically can be considered to have higher importance.Even negative campaigning may be caused, because new issue can be subject to extra keeping under strict supervision close inspection usually to the minor error that the operation of new software does not have an appreciable impact.Scoring engine can receive or calculate the marketing score relevant to each mistake.The marketing score of higher number can represent higher activity or popularity.

Parameter score can be assigned with a value or numeral.In an embodiment, to be assigned with or the parameter score that is associated with mistake can be scaled or be assigned with non-constant scope.Such as, some parameters can be scaled to the scope had from 1 to 4, and other parameters can be scaled to the value had from 1 to 100.In an embodiment, the scope of parameter value can be changed or be modified to change these parameters to the significance level of gross errors score or evaluation or impact.For each client, the scope of each parameter or convergent-divergent can be adjusted based on the preference of client.Such as, value be 100 deployment parameters score can represent download or the deployment of the much larger number that the code relevant with mistake is associated, and the score that value is 1 can indicate without or more only.

Parameter score that is relevant to each mistake, that receive or calculate can be stored in storer or in showing, and is used to miscount score.

In certain embodiments, when each new mistake is reported to instrument, parameter score can be calculated or be estimated.Parameter score can be generated in different granular level.For each specific deployment, client, software version, software module, script, code snippet, code word, code library etc., parameter score can be generated.Granularity can depend on the granularity etc. of the validity of data, the structure of software or architecture, possible software upgrading.

In one embodiment, the parameter score of each mistake can be classified or be assigned in different groups.Group can be defined the parameter score obtained about the specific tolerance be associated with mistake or characteristic.Such as, some parameters can be classified into " mistake is generally spent " group.This group can comprise the score of the parameter be associated with the quantity of the quantity of download to the relevant software of mistake, the quantity of relevant software metric tools or relevant mistake.Another group can be used to obtain the parameter score relevant to " erroneous effects ".Erroneous effects group can comprise with mistake, system is produced impact, the technology component of erroneous effects, service that mistake can affect and assembly the score of parameter that is associated such as range.

The marketing, business activity, error result etc. can be assigned to other groupings of parameter score.

Miscount score can be used to the grouping of wrong parameter score.In one embodiment, the parameter score of each group can be disposed in a vector or matrix.The matrix of the parameter score of each parameter group or vector can be generated by scoring engine 113.Such as, generally spending parameter score that is relevant, that divide into groups to mistake can be disposed in matrix A=(ARURSRB), wherein ARU is the deployment parameters score that the quantity of the download of the software relevant with mistake is associated, RS is the code parameter score be associated to the quantity of relevant software metric tools, and RB is the relevant error parameter score be associated to the quantity of relevant mistake.Similarly, parameter score that is relevant to erroneous effects, grouping can be disposed in matrix B=(TCSBI), wherein TC be with erroneous effects to the technical parameter score that is associated of technology component, S is the seriousness parameter score be associated with the seriousness of the impact of mistake, and BI is the erroneous effects parameter score be associated with erroneous effects.

After the matrix of each group is defined, gross errors score (bugsscore) can be calculated as be multiplied (inner product) of matrix:

Equation 1

Wherein * is scalar multiplication.

Use the wrong score formula in equation 1, mistake scoring engine can calculate single scalar mistake score by operation parameter score.Such as, scoring engine can calculate or receiving parameter score: ARU=4, RS=5, RB=12, TC=10, S=4, BI=10.Parameter score can be grouped into two matrix: A=(4512) and B=(10410).Get inner product to matrix A and B, gross errors score can be calculated as: mistake score=4*10+5*4+12*15=240.Value be 240 wrong score can be stored in a database, and to be associated with mistake.

In an embodiment, the calculating of wrong score can be extended and be revised as the parameter score (that is, more than two matrixes) comprised more than two groups.In an embodiment, can be changed the grouping of parameter score, such as, the parameter score joined with a group or matrix correlation can depend on the context of mistake and be changed.The order of the parameter score in each group can be changed.The meaning of each parameter score in gross errors score can be changed to the arrangement of the value of the parameter score in group or matrix.In addition, the quantity of the parameter in each group also can change.Although the group with three parameter scores is exemplarily presented, in other embodiments, one group of parameter score can have a four or more score.In certain embodiments, each parameter score can be scaled by the one or more score in parameter score is added with a numeral, is multiplied or is divided by.Convergent-divergent can be used to improve or reduce the importance of a parameter score in gross errors score.

Comprising the calculating of gross errors score in the embodiment more than the parameter score of two groups, mistake score (bugsscore) can be calculated as:

bugsscore＝A·B·...·Z＝(A ₁A ₂...A _i)(B ₁B ₂...B _i)...(Z ₁Z ₂...Z _i)

＝A ₁*B ₁*...*Z ₁+A ₂*B ₂*...*Z ₂+…+A _i*B _i*...*Z _i

Equation 2

Wherein A, B, Z are the matrixes of parameter score, A _j, B _j, Z _jbe the parameter score of matrix, * is scalar multiplication.

In an embodiment, scoring engine can calculate more than one wrong score.Scoring engine can depend on customer priorities, software metric tools etc. and calculate different wrong scores.By using two groups of parameter scores can calculate a wrong score, and another wrong score can be calculated by use three groups of parameter scores.Such as, by using the two groups of parameter scores had with different values carries out the parameter score that convergent-divergent obtains can calculate the 3rd score.Each wrong score in different wrong scores can be stored in error database, and is associated with mistake.Each wrong score can be made marks or be tagged with the description of correspondence or identifier, to describe or identifier can be used to the parameter score determining to use in the calculation and parameter must be divided into groups.Can with customizing the break links score such as client, software, system of wrong score for it or tagging to wrong score.Metadata, data-base recording can be used, describe each score to the link etc. of oracle.

Fig. 2 illustrates the process flow diagram with the step 200 for generation error score used by wrong instrument.At block 202 place, mistake means accepts error reporting.Can from client, receive error reporting from error database or other sources.Error reporting can some attributes of identification error, the behavior of such as mistake, condition, relevant system or software metric tools etc.In some cases, error reporting can identify the software code relevant to mistake, version or issue.Do not comprise such relevant information at error reporting or only comprise in the embodiment of partial information, mistake instrument can be used to comformed information.At block 204 place, mistake instrument can be used to identify the software code relevant to mistake.Mistake instrument can be used, to determine the code relevant to mistake together with any amount of external tool, device, database, debugger, compiler etc.In some cases, relevant to mistake code can be determined via look-up table.The code determining responsible n-back test can be used to the description of mistake or selection of time, behavior etc.Such as, if mistake is described to the specific function affecting software, then look-up table can be used to determine which code is relevant to such function.In other embodiments, mistake the term of execution programmed dump can be used to the code determining to cause accident or mistake.In some cases, the granularity of the software code be associated with mistake can be determined exactly, and is associated with the set of specific module, class, storehouse or even code line.In the mistake that some are more complicated, the definite essence of mistake or reason may be difficult to find out, may be mutual by a variety of causes or various software code fragment causes.Therefore block 204 only can provide the high-level overview of the software code be associated with mistake, and only identifies such as software version or software metric tools.

In block 206, the data required for calculating parameter score can be collected and/or identify to mistake score instrument.Determine that the data required for each parameter score may change for each parameter.Some parameter scores may require collect or identify two or more values.Other parameter scores may only require to search a value.Parameter can comprise content discussed above, such as to the deployment of code, generally degree, the erroneous effects etc. of code.Mistake score instrument can be collected and/or identification data from any amount of local and remote database and data source.Such as, the deployment parameters score that software has been deployed how many times can be used to indicate, can be associated with some data sources.In order to determine that the code snippet relevant to mistake has been downloaded how many times, first mistake score instrument can collect data to determine that the code be associated with mistake is all possible product version of its part, software metric tools and module.Then, mistake score instrument can possibly from other data sources, collect the data relevant with the quantity of deployment of code is each product version of its part, software metric tools and module are associated download or activity.

In block 208, mistake score instrument can by being used in the supplemental characteristic collected in block 206, calculating parameter score at least in part.Some parameter scores can equal for the data collected by each parameter.In an embodiment, parameter score can by further standardization or convergent-divergent.Such as, to the calculating of deployment parameters score can relate to by all that collect, the quantity of the download of each product version, software metric tools and the module that are associated with mistake is added.Score instrument can pass through such as by the total quantity of the deployment parameters score calculated divided by the deployment to all possible product version, software metric tools and module, and the deployment parameters score that next further standardization calculates is not more than value 1 to make it.

In block 210, parameter score can be divided into one or more groups by mistake score instrument.In an embodiment, can based on the similarity of parameter score to the grouping of parameter score.Such as, relevant with the quantity of the quantity downloaded, quantity that related software is disposed and relevant error parameter score can all be assigned to together.Parameter score in each group can be used to generator matrix for calculated population mistake score.The order of the parameter score in each matrix and can being determined by customer priorities, system preference or other definition the grouping of parameter score.Customer priorities can be received from customer database, and can define which parameter and should be grouped into together.Grouping and the order of parameter score can affect the wrong score finally calculated.The preference of client in grouping and order can reflect that client is determining to make the weight of a parameter score higher than the preference of the weight of another parameter score in wrong score.In an embodiment, mistake score instrument for the one or more wrong score of calculating, can generate the group of parameter score and some various combinations of matrix.

In block 212, mistake score instrument can be used in the matrix computations gross errors score of the parameter score generated in 210.Mistake score instrument can according to equation 1 define such, calculate the inner product of two matrixes, or when relating to the matrix more than two, according to equation 2 define such, calculated population mistake score.Mistake score instrument can calculate more than one wrong score by using the various combination of matrix.Mistake score can be associated from the preference from different client, the preference for particular software package or version etc.

In block 214, mistake score can be stored in the database of score instrument this locality, or is stored in the database of external source.Each wrong score can be associated with additional data.Additional data can describe and how calculate the score, uses what customer priorities, relevant client etc.In certain embodiments, the independent parameter score for miscount score also can be stored by instrument.

After calculating wrong score, priority division can be carried out according to the wrong score of software error to software error.Priority divides the order that can be used to definition error and will be solved or be repaired.In an embodiment, the mistake with the highest wrong score can be given the highest priority, and is arranged first to carry out repairing or solving.In certain embodiments, based on the wrong score of each mistake, mistake can be divided priority, and is assigned in group.According to threshold value or the scope of wrong score, mistake score can be assigned to " high priority ", " medium priority ", " low priority ".In certain embodiments, have 300 or the mistake of the error score that is greater than 300 can be divided into high priority mistake, there is the mistake being less than 300 but being greater than the wrong score of 100 and can be divided into medium priority mistake, and have 100 or the mistake of the wrong score that is less than 100 can be divided into low priority mistake.Such as, the mistake being divided into high priority is repaired before can being arranged at medium priority mistake, and medium priority mistake is repaired before can being arranged at low priority mistake.But, for the mistake in each group, the particular order in priority groups can not be distributed in.Any amount of different priority groups can be defined.

In an embodiment, can based on relative wrong score, assignment error priority.Such as, based on the wrong score of mistake, mistake can be sorted, and front 20 mistakes can be assigned to high priority, and following 30 mistakes are assigned to low priority etc., and no matter absolute wrong score is how many.

In an embodiment, depend on and use which wrong score in prioritization, mistake can be assigned with more than one priority.According to a wrong score, mistake can be assigned to high priority, and according to another wrong score, mistake can be assigned to low priority.In an embodiment, use the wrong score calculated based on customer priorities, the wrong priority list corresponding to specific customer priorities can be generated.Priority list and priority evaluation can be generated for specific software metric tools, module, version, client etc.The priority of mistake can be stored by mistake instrument of scoring.Whether priority can with identification priority specific to special customer priorities (if general), be associated specific to the priority details of software metric tools etc.

Mistake score instrument can comprise the graphical interfaces for showing wrong score, parameter, description etc.In an embodiment, graphical interfaces can be used to the state of trail-and-error.Mistake score instrument can dock to show with other software, instrument etc. or trail-and-error, mistake state etc.

Fig. 3 show illustrate used by wrong instrument, in order to the process flow diagram of the method 300 to wrong prioritization.In block 302, mistake score and trace tool can receive wrong score.Mistake score can be stored locally in mistake score and trace tool or be stored in remote data base.Mistake score can comprise the information be associated with wrong score, if this information definition score is only relevant to particular customer, software metric tools, system etc., then how wrong score is calculated.In block 304, mistake score and trace tool can resolution data to determine correlativity or the applicability of wrong score.Can generate how much priority divides list instrument can be allowed to determine at the resolution data at 304 pieces of places.The wrong score generated based on the preference of different client can not compare mutually.As a rule, only for the wrong score using compatible preference, calculate in a similar fashion, relevant priority can be generated and divide list.In some cases, mistake score and priority instrument can be configured to generate only for the priority list of particular customer.At block 304 place, instrument can be resolved to the data that wrong score is associated to locate the wrong score relevant with particular customer.In block 306, the wrong score relevant to certain priority list can be classified.With from minimum to maximum or any other standard, the classification to list can be performed.In block 308, the wrong score that each priority divides in list can be divided into, such as, corresponding to high priority mistake, medium priority mistake, some groups of low priority mistake.Can based on the absolute value of wrong score, the relative value of mistake score in score list, predetermined threshold value etc. to the grouping of mistake and priority assign 310.High priority mistake can be aligned to and be repaired before medium priority mistake, and medium priority mistake can be aligned to and was repaired before low priority mistake.

When by mistake score and trace tool input or receive new wrong time, can perform termly based on the priority division of wrong score to mistake.Based on the wrong score of new mistake, new mistake can be added in each priority groups.

In an embodiment, mistake score and trace tool can be used to follow the tracks of and the wrong patch that is associated and software upgrading.An evaluation similar with score to the evaluation of the mistake of its reparation and score can be provided with the software patch of the wrong particular problem that be associated or mistake or renewal to solving.By wrong score and wrong priority propagation to software patch, this propagation can provide score and priority to patch.Can be important for the priority of patch and score, for identifying the patch needing to install immediately.Identical with the situation for mistake, for different clients, software metric tools etc., the priority preferences of patch can be different.Patch can have more than one priority or score, and each priority in its medium priority and score and score can be associated from different clients, software version etc.

In an embodiment, mistake score and trace tool can be used to generate the software upgrading according to customer priorities customization and patch report.Assessed to according to the preference of client and to be divided priority be that the software patch that the mistake of high priority mistake is relevant can be packaged as one or more regular software upgrading.Mistake score and trace tool can be configured to the report of the state generating the general introduction mistake relevant with software version to the system of each client and patch.Report can summarize the state of the mistake reported by client.

Fig. 4 shows the process flow diagram that the method 400 that the priority for generating for patch is evaluated is shown.The priority evaluation of the mistake that priority evaluation can be repaired with patch is associated.The different priorities evaluation of patch can be generated for different clients, if client wants to install this patch, then allow client can make decision of knowing the inside story.Mistake score and trace tool receive the data 402 be associated with each patch.Patch can not be that client or version are specific, and can not comprise the relevant information of any and specific customer priorities.Patch can comprise the information relevant with the mistake that patch is repaired.Mistake score and trace tool can read patch data, and receive the data 404 for the mistake be associated with patch.Mistake score and trace tool can determine the wrong score be associated with mistake.Each mistake can have more than one wrong score, score and trace tool can resolution data to determine the score being applicable to particular customer, software metric tools etc.Instrument can determine the highest relevant error score and priority 406 for patch.Instrument can by the highest wrong score and priority assign to patch 408.Patch can have more than one score and priority.Each patch can have the multiple score relevant from different clients, software version etc. and priority.For each client, software version etc., mistake score and trace tool can generate report and be divided the list of patches of priority.

One or more in mistake score and trace tool or its module and assembly can be software module, hardware module, virtual unit, code, script etc.Mistake score and trace tool can be can by the service of Platform deployment.In an embodiment, mistake score and trace tool can be developed, dispose and monitor at source server place, and use support cloud platform.Support the door of cloud platform can be used to gateway remotely to dispose, manage with Monitoring Service error reporting, patch deployment, system monitoring and score to mistake other function and services relevant with trace tool.Support that the embodiment at Yunmen family is being submitted to by Masterson etc. is synchronous, name is called jointly co-pending, the commonly assigned U.S. Patent application No.13/937 of " ADVANCEDCUSTOMERSUPPORTSERVICES – ADVANCEDSUPPORTCLOUDPORTAL ", be described in the patent of 970 (agency case 88325-870401 (138600US)), its entirety is merged in herein by reference.Support Yunmen family gateway embodiment some aspects also on March 20th, 2009 submit to, name is called the U.S. Patent application No.12/408 of " METHODANDSYSTEMFORTRANSPORTINGTELEMETRYDATAACROSSANETWOR K ", 170, with to submit on June 14th, 2005, name is called the U.S. Patent application No.11/151 of " METHODANDSYSTEMFORRELOCATINGANDUSINGENTERPRISEMANAGEMENT TOOLSINASERVICEPROVIDERMODEL ", 645, and on June 14th, 2005 submit to, name is called the U.S. Patent application No.11/151 of " METHODANDSYSTEMFORREMOTEMANAGEMENTOFCUSTOMERSERVERS ", be described in 646, wherein the entirety of each application is merged in herein by reference.

Fig. 5 describes the block diagram of the embodiment supporting cloud platform 500.Platform can be used to the one or more goal systems 516,518 remotely will be deployed to the service that mistake is scored and trace tool is associated, function and method in the data center 502 of client.Can dispose and Monitoring Service, function and method from long-range production cloud (productioncloud) 504 via network 512.Service, function and method can be deployed to the gateway 514 of the data center 502 of client from door 506.Gateway can be used to service arrangement to the server in the data center of client and goal systems 516,518.Gateway 514 can collection system data, customer data, performance data and/or class likelihood data, and data are sent to and produce cloud 504, in production cloud 504, these data can be used to further analysis, and are used to evaluate mistake for each client to mis-classification.Serve the term of execution, gateway can Monitoring Service and collect data.By using door 506, data can be stored, analyze and show.The report of error reporting, patch, can be shown via door 506 with the mistake of score and evaluation and/or the list of patch, and can for client.

The production cloud 504 of cloud platform 500 can comprise can be passed to the available service 508 of gateway 514 and the set of content library 510.For mistake score and the different function of trace tool or module, different services can be provided.Such as, a service can provide patch to install and following function, and another service can provide error tracking function.By using door 506, each service can be selected, disposed and monitored.By producing, cloud 504 is evaluated in mistake, is found, the data of installing and/or collecting during similar operations are disposed in path, can be used to improve the service at customer data center 502, performance and/or reliability by other services.Such as, data can be used to improve modeling service.

Fig. 6 illustrates the embodiment of computer system.Computer system as shown in Figure 6 can be included as a part for the computerized system of the system 100 of previously described such as Fig. 1 and so on.Computer system 600 can represent some or all assemblies in the assembly of computer system and/or the remote computer system discussed in this application.Computer system 600 can execution analysis instrument.Fig. 6 provides schematically illustrating the embodiment of computer system 600, and computer system 600 can perform as described herein, the method that provided by various embodiment.It should be noted that Fig. 6 is only intended to provide the general description to various assembly, any or all of assembly in various assembly can suitably be utilized.Therefore, Fig. 6 broadly understands how independent system element can be implemented with relative separation or relative more integrated mode.

Computer system 600 is illustrated that comprise can via bus 605 (or can otherwise communicate, depend on the circumstances) by the hardware element electrically coupled.Hardware element can comprise one or more processor 610, includes but not limited to one or more general processor and/or one or more application specific processor (such as digital signal processing chip, figure OverDrive Processor ODP and/or similar processor); One or more input equipment 615, it can include but not limited to mouse, keyboard and/or similar input equipment; And one or more output device 620, it can include but not limited to display device, printer and/or other equipment.

The memory device 625 of one or more non-transitory that computer system 600 can also comprise (and/or communicating with), memory device 625 can include but not limited to the memory storage of this locality and/or network-accessible, and/or can include but not limited to it can is programmable, that flash is renewable and/or similar disk drive, drive array, optical storage apparatus, solid storage device, such as random access memory (" RAM ") and/or ROM (read-only memory) (" ROM ").Such memory device can be configured to implement any applicable data and store, and includes but not limited to various file system, database structure and/or analog.

Computer system 600 can also comprise communication subsystem 630, and it can include but not limited to modulator-demodular unit, network interface card (wireless or wired), infrared communication device, Wireless Telecom Equipment and/or chipset (such as bluetooth ^tMequipment, 802.11 equipment, Wi-Fi equipment, WiMax equipment, cellular device etc.) and/or analog.Communication subsystem 630 can license data and network (such as network described below provides an example), other computer systems and/or any other equipment described herein exchange.In many examples, computer system 500 also can comprise working storage 635, and it can comprise above-mentioned RAM or ROM equipment.

Computer system 600 can also comprise the software element being illustrated and being currently located within working storage 635, working storage 635 comprises operating system 640, device driver, can perform storehouse and/or other codes, such as one or more application program 645, application program 645 can comprise the computer program provided by various embodiment, and/or application program 645 can be designed to implement the method that provided by other embodiments as herein described and/or configure the system provided by other embodiments as herein described.Only in an illustrative manner, may be implemented as computing machine (and/or the processor in computing machine) executable code and/or instruction about the one or more flow processs described by method discussed above; In one aspect, then such code and/or instruction can be used to configuration and/or adapting universal computing machine (or other equipment), to perform one or more operation according to described method.

The set of these instructions and/or code can be stored on the computer-readable recording medium of non-transitory, all non-transitory memory devices 625 as described above.In some cases, storage medium can be contained in the computer system of such as computer system 600 and so on.In other embodiments, storage medium can be separated with computer system (such as, removable media, such as CD), and/or storage medium may be provided in installation kit, programme with the program/code making storage medium can be used to it stores, configure and/or adapting universal computing machine.These instructions can adopt the form of executable code, executable code is that computer system 600 is executable, and/or these instructions can adopt source and/or can install the form of code, when compiling in computer system 600 and/or installing (such as, use any one in various usually available compiler, installation procedure, data compressing/decompressing apparatus etc.), then can adopt the form of executable code.

To those skilled in the art clearly, according to specific requirement, a large amount of changes can be made.Such as, the hardware of customization also can be used, and/or specific element may be implemented within hardware, software (comprising portable software, such as small routine etc.) or both in.In addition, can being used with the connection of other computing equipments of such as network input-output apparatus and so on.

As mentioned above, in one aspect, some embodiments can use computer system (such as computer system 600) to perform method according to various embodiments of the present invention.According to one group of embodiment, (it can be contained in operating system 640 and/or other codes the one or more sequences performing in the one or more instructions being comprised in working storage 635 in response to processor 610, such as application program 645), the some or all of flow processs in method are according to various embodiments of the present invention performed by computer system 600.Can from one or more and so on the computer-readable medium such as non-transitory memory device 625, by such instruction fetch in working storage 635.Only in an illustrative manner, processor 610 can be made to perform one or more flow processs in method as herein described to the execution of the sequence of the instruction be comprised in working storage 635.

Term as used herein " machine readable media " and " computer-readable medium ", refer to any medium participating in providing the data that machine can be operated in a particular manner.In the embodiment using computer system 600 to implement, various computer-readable medium can relate to provides instructions/code for execution to processor 610, and/or various computer-readable medium can be used to store and/or carry such instructions/code.In many embodiments, computer-readable medium is physics and/or tangible storage medium.Such medium can adopt the form of non-volatile media or Volatile media.Non-volatile media comprises such as CD and/or disk, such as non-transitory memory device 625.Volatile media includes but not limited to dynamic storage, such as working storage 635.

The common type of physics and/or tangible computer-readable medium comprises such as, and floppy disk, flexible disk, hard disk, tape or any other magnetic medium, CD-ROM, any other optical medium, card punch, paper tape, any other has the physical medium of sectional hole patterns, RAM, PROM, EPROM, FLASH-EPROM, any other memory chip or box or computing machine can any other medium of therefrom reading command and/or code.

Various forms of computer-readable medium can relate to the one or more sequences in one or more instruction are carried to processor 610 for execution.Only in an illustrative manner, on the instruction disk that can be carried at remote computer at first and/or CD.Instruction can be loaded in the dynamic storage of remote computer by remote computer, and will be sent as signal by the instruction that computer system 600 receives and/or performs by transmission medium.

Computer subsystem 630 (and/or assembly wherein) understands Received signal strength usually; and signal (and/or the data, instruction etc. entrained by signal) then can be carried to working storage 635 by bus 605, processor 610 is retrieved and is performed instruction from working storage 635.The instruction received by working storage 635 before or after processor 610 performs it, can be stored on non-transitory memory device 625 alternatively.

Should be understood that further, the assembly of computer system can distribute in a network.Such as, some process can be performed by use first processor a position, and other process can perform by first processor another processor at a distance.Other assemblies of computer system 600 can distribute similarly.

Method discussed above, system and equipment are examples.Various configuration can be omitted, substitute or increase various flow process or assembly, depend on the circumstances.Such as, in alternative arrangements, method can be performed with the order different from described order, and/or the various stage can be increased, omits and/or combine.Equally, can be incorporated in other configurations various about the feature described by some configuration.Different aspect and the element of configuration can be combined in a similar fashion.Similarly, technology is in development, and therefore many elements are examples, and do not limit the scope of the disclosure or claim.

Give specific details in the de-scription, to provide the deep understanding to example arrangement (comprising embodiment).But, when there is no these specific detail, configuration can be implemented.Such as, without unnecessary detail, the circuit known, process, algorithm, structure and technology are illustrated, to avoid making configuration indigestion.This description merely provides example arrangement, does not limit the scope of the claims, applicability or configuration.On the contrary, the above description to configuration will be provided for the attainable description implementing the technology that is described for those skilled in the art.When not deviating from spirit or scope of the present disclosure, various change can be made in the layout of function and element.

In addition, configuration can be described to process, and this process can be depicted as process flow diagram or block diagram.Although operation can be described as the process of order by each figure, the many operations in operation can be performed concurrently or side by side.In addition, the order of operation can be re-arranged.Process can have the additional step be not included in the accompanying drawings.In addition, the example of method can be implemented by hardware, software, firmware, middleware, microcode, hardware description language or these any combination.When implementing in software, firmware, middleware or microcode, can be stored in the computer-readable medium of the non-transitory of such as storage medium and so on for the program code or code segment performing necessary task.Processor can perform described task.

Describe some example arrangement, and when not deviating from spirit of the present disclosure, various amendment, alternative constructions and equivalent can have been used.Such as, above element can be the assembly compared with Iarge-scale system, and wherein other rules may be dominant, or otherwise revise the application.In addition, can above element be considered before, be considered period or be considered after, carry out some steps.Therefore, above description does not retrain the scope of claim.

Claims

1., for the system to wrong prioritization, described system comprises:

One or more processor; With

Storer, couple itself and described one or more processor communication, and can be read by described one or more processor, and store a series of instruction on a memory, when described a series of instruction is performed by described one or more processor, make described one or more processor by performing following steps to software error prioritization:

Receive software error report, described software error report has the data division describing described software error, and wherein said data division comprises the information of at least one impact describing described software error;

At least partly based on the impact of described software error, determine the codebases of described software error, wherein said codebases is the software code comprising coding error, and described coding error causes the impact of described software error;

Receive customer priorities, described customer priorities defines one group of parameter, and described parameter describes the preference of the client of the importance for evaluating described software error;

When inartificial input, calculate the one group parameter score relevant to described software error, described one group of parameter that wherein said one group of parameter Score quantifies defines in described customer priorities;

Described one group of parameter score is grouped into first group and second group;

Use described first group and described second group of miscount score; And

Generate the error reporting of the priority division with described software error, described priority divides based on described wrong score.

2. system according to claim 1, wherein said one group of parameter score comprises:

Deployment parameters score, wherein said deployment parameters score summarizes the number of times that described codebases has been deployed;

Affecting parameters score, wherein said affecting parameters score summarizes the seriousness of the impact of described software error;

Relevant error parameter score, wherein said relevant error parameter score summarizes the quantity of the mistake relevant to described software error; With

Technical parameter score, wherein said technical parameter score summarizes the importance of described codebases.

3. system according to claim 2, also comprises and receives at least one additional parameter score relevant to described software error.

4. system according to claim 1, wherein by getting inner product to the parameter score of described first group and described second group, calculates the wrong score of described software error.

5. system according to claim 3, wherein also comprises the grouping of described one group of parameter score and is divided at least one additional parameter group.

6. system according to claim 3, at least one wherein relevant to described software error additional parameter score comprises the parameter score of the marketing activity of summarizing the codebases of being correlated with described software error.

7. system according to claim 1, wherein said priority divides the absolute value based on described wrong score.

8. system according to claim 1, wherein said priority divides the relative value based on described wrong score.

9., for the method to wrong prioritization, described method comprises:

Use described first group and described second group of miscount score; And

10. method according to claim 9, wherein said one group of parameter score comprises:

Technical parameter score, described technical parameter score summarizes the importance of described codebases.

11. methods according to claim 9, wherein by getting inner product to the parameter score of described first group and described second group, calculate the wrong score of described software error.

12. methods according to claim 11, wherein also comprise the grouping of described one group of parameter score and are divided at least one additional parameter group.

13. methods according to claim 11, wherein said one group of parameter score comprises the score of the marketing activity of summarizing the codebases relevant to described software error.

14. methods according to claim 9, wherein said priority divides the relative value based on described wrong score.

15. 1 kinds of computer programs, it is present on non-transient state processor readable medium, and comprises the processor instructions being configured such that one or more processor execution following steps:

Use described first group and described second group of miscount score; And

16. computer programs according to claim 15, wherein said one group of parameter score comprises:

17. computer programs according to claim 15, wherein by getting inner product to the parameter score of described first group and described second group, calculate the wrong score of described software error.

18. computer programs according to claim 17, wherein also comprise the grouping of described one group of parameter score and are divided at least one additional parameter group.

19. computer programs according to claim 17, wherein said one group of parameter score comprises the parameter score of the marketing activity of summarizing the codebases relevant to described software error.

20. computer programs according to claim 15, wherein said priority divides the relative value based on described wrong score.