CN102591774B - Method for determining severity levels of software defects - Google Patents
Method for determining severity levels of software defects Download PDFInfo
- Publication number
- CN102591774B CN102591774B CN201110448608.7A CN201110448608A CN102591774B CN 102591774 B CN102591774 B CN 102591774B CN 201110448608 A CN201110448608 A CN 201110448608A CN 102591774 B CN102591774 B CN 102591774B
- Authority
- CN
- China
- Prior art keywords
- software
- variable
- quantized value
- quality defect
- defect
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Landscapes
- Stored Programmes (AREA)
- Investigating Or Analysing Biological Materials (AREA)
Abstract
The invention provides a method for determinating severity levels of software defects, comprising the following steps: 1) sending a determination request for software quality defects by an operator via network; 2) responding to the determination request by a determination terminal; 3) operating a software quality defect determination module; 4) respectively selecting a quantization value to assign to a corresponding software quality defect determination standard variable so as to enable each software quality defect determination standard variable to have a quantization value; 5) judging whether each software quality defect determination standard variable has a quantization value; if not, alarming and applying a prompt; if so, performing the next step; 6) calculating quantization values of the software quality defect variables; 7) judging severity levels of software defects according to the quantization values of the software quality defect variables; and 8) releasing the software quality defect determination module.
Description
Technical field
The present invention relates to software field, particularly relate to a kind of method for determinating severity levels of software defects.
Background technology
Along with the development of domestic software industry and product I Tization, speed measuring with software is more and more paid attention to, and the defect of software product also plays conclusive impact to quality, and the severity level assay method of each company to quality defect of software exists certain difference.General is all measured by the experience of tester, and this artificial mensuration is more subjective, and owing to testing the difference of experiences and backgrounds, the measurement result of acquisition also exists each species diversity, can not accurately measure quality defect of software.Simultaneously, each software producer is to the mensuration of the speed measuring with software defect of producing separately, all that the mass defect of angle to this software standing in developer measures, thus some deviations appear in the measurement result that final user may be caused to provide with manufacturer in this software product process of use, thus final user may be made to produce certain suspection to the prestige of the manufacturer of this software product.Meanwhile, the cost of follow-up maintenance may be caused significantly to increase the error measurement of software defect severity level.
Visible, invent a kind of centered by final user, can method that is objective, that measure quality defect of software be accurately very important.
Summary of the invention
The object of the present invention is to provide a kind of method for determinating severity levels of software defects, it, by unified bioassay standard, objectively measures quality defect of software, determination efficiency and accuracy high.
For achieving the above object, the invention provides a kind of method for determinating severity levels of software defects, it comprises the steps:
Step 1, operator send the mensuration request of quality defect of software by network;
Step 2, mensuration terminal response measure request;
Step 3, operating software mass defect measure module, and this step 3 comprises:
The dimension variable of step 3.1, definition quality defect of software variable, quality defect of software bioassay standard variable and each quality defect of software bioassay standard, described quality defect of software bioassay standard variable comprises: disturbance degree variable, frequency variable, perception difficulty variable and reparation difficulty variable;
Step 3.2, the value of each dimension variable to be quantized;
Step 4, select a quantized value assignment to corresponding quality defect of software bioassay standard variable respectively, thus make described quality defect of software bioassay standard variable have a quantized value respectively;
Step 5, judge whether all quality defect of software bioassay standard variablees all have a quantized value, if not, then report to the police and point out, if so, then performing next step;
Step 6, pass through formula: quantized value=0.8* (quantized value of the quantized value+frequency variable of disturbance degree the variable)/2+0.2* (quantized value of the quantized value+reparation difficulty variable of perception difficulty variable)/2 of quality defect of software variable, calculates the quantized value of quality defect of software variable;
Step 7, judge software defect severity level according to the quantized value of quality defect of software variable, and the quantized value of this quality defect of software variable and this software defect severity level are shown to user;
Step 8, release quality defect of software measure module.
Described step 3.1 also comprises calls init (), each variable that initialization defines.
In described step 3.2, the quantized value of the dimension variable of disturbance degree variable is respectively: almost without impact be 1, on function without impact but client can realize to be 2, have impact to be 3 on function, may become fatal is 4, fatal be 5; The quantized value of the dimension variable of frequency variable is respectively: to there will not be 1, to there will be 2, actually extremely easily appear as 3 when using; The quantized value of the dimension variable of perception difficulty variable is respectively: extremely embarrass 1, embarrass 2, be easily 3; The quantized value repairing the dimension variable of difficulty variable is respectively: be easily 1, embarrass 2, extremely embarrass 3.
Software defect severity level in described step 7 comprises slight, general, serious and fatal.
Corresponding relation between the quantized value of described software defect severity level and described quality defect of software variable is: when the quantized value of quality defect of software variable is more than or equal to 3.4, and this software defect severity level is fatal; The quantized value of quality defect of software variable is less than 3.4, and when being more than or equal to 2.9, this software defect severity level is serious; The quantized value of quality defect of software variable is less than 2.9, and when being more than or equal to 2.4, this software defect severity level is general; The quantized value of quality defect of software variable is less than 2.4, and when being more than or equal to 1.0, this software defect severity level is slight.
Described step 6 is by calling bugLevelCount () to run described formula.
Described step 8 measures the release of module by calling doCancel () to realize quality defect of software.
Described step 7 shows quantized value and this software defect severity level of this quality defect of software variable by display.
Beneficial effect of the present invention: method for determinating severity levels of software defects provided by the present invention, it is by the bioassay standard centered by final user, objectively quality defect of software is measured, thus ensure accuracy and the high efficiency of mensuration, while guarantee product quality, the maintenance cost in later stage can also be effectively reduced.
In order to further understand feature of the present invention and technology contents, refer to following detailed description for the present invention and accompanying drawing, but accompanying drawing only provides reference and explanation use, is not used for being limited the present invention.
Accompanying drawing explanation
Below in conjunction with accompanying drawing, by the specific embodiment of the present invention describe in detail, will make technical scheme of the present invention and other beneficial effect apparent.
In accompanying drawing,
Fig. 1 is the process flow diagram of method for determinating severity levels of software defects of the present invention.
Embodiment
For further setting forth the technological means and effect thereof that the present invention takes, be described in detail below in conjunction with the preferred embodiments of the present invention and accompanying drawing thereof.
Refer to Fig. 1, the invention provides a kind of method for determinating severity levels of software defects, it comprises the steps:
Step 1, operator send the mensuration request of quality defect of software by network;
Step 2, mensuration terminal response measure request;
Step 3, operating software mass defect measure module, and this step 3 comprises:
Step 3.1, call init (), initializers mass defect measures module, the pattern file that cited system is unified, its method is <link href=" css/base.css " rel=" stylesheet " type=" text/css "/>; Definition quality defect of software variable is the dimension variable of var leve, quality defect of software bioassay standard variable and each quality defect of software bioassay standard, and initialization is carried out to defined variable, described quality defect of software bioassay standard variable comprises: disturbance degree variable E, frequency variable P, perception difficulty variable α and reparation difficulty variable β.
Step 3.2, the value of each dimension variable quantized, the quantized value of the dimension variable of described disturbance degree variable is respectively: almost without impact be 1, on function without impact but client can realize to be 2, have impact to be 3 on function, may become fatal is 4, fatal be 5; The quantized value of the dimension variable of frequency variable is respectively: to there will not be 1, to there will be 2, actually extremely easily appear as 3 when using; The quantized value of the dimension variable of perception difficulty variable is respectively: extremely embarrass 1, embarrass 2, be easily 3; The quantized value repairing the dimension variable of difficulty variable is respectively: be easily 1, embarrass 2, extremely embarrass 3.
Step 4, select a quantized value assignment to corresponding quality defect of software bioassay standard variable respectively, thus make described quality defect of software bioassay standard variable have a quantized value respectively.
Step 5, judge whether all quality defect of software bioassay standard variablees all have a quantized value, if not, then report to the police and point out, as: winMsg (" warning ", " note that 4 standards are essential option! "); , wherein first character string is the title of dialog box, and second character string is the content of dialog box; If so, then next step is performed.
Step 6, call bugLevelCount (), by formula: quantized value=0.8* (quantized value of the quantized value+frequency variable of disturbance degree the variable)/2+0.2* (change of perception difficulty variable is worth+repairs the quantized value of difficulty variable)/2 of quality defect of software variable, that is, var leve=0.8* (E+P)/2+0.2* (alpha+beta)/2 calculates the quantized value of quality defect of software variable.
Step 7, judge software defect severity level according to the quantized value of quality defect of software variable, and the quantized value of this quality defect of software variable and this software defect severity level are shown to user by display; In the present embodiment, the corresponding relation between the quantized value of described software defect severity level and described quality defect of software variable is: when the quantized value of quality defect of software variable is more than or equal to 3.4, and this software defect severity level is fatal; The quantized value of quality defect of software variable is less than 3.4, and when being more than or equal to 2.9, this software defect severity level is serious; The quantized value of quality defect of software variable is less than 2.9, and when being more than or equal to 2.4, this software defect severity level is general; The quantized value of quality defect of software variable is less than 2.4, and when being more than or equal to 1.0, this software defect severity level is slight.
The method for closing doCancel () that step 8, calling system share, release quality defect of software measures module, and its concrete grammar is top.frames [" Iframe "] .doCancel ().
In sum, method for determinating severity levels of software defects provided by the present invention, it is by the bioassay standard centered by final user, objectively quality defect of software is measured, thus ensure the accuracy of mensuration, while guarantee product quality, the maintenance cost in later stage can also be effectively reduced, improve detection efficiency.
The above, for the person of ordinary skill of the art, can make other various corresponding change and distortion according to technical scheme of the present invention and technical conceive, and all these change and be out of shape the protection domain that all should belong to the claims in the present invention.
Claims (5)
1. a method for determinating severity levels of software defects, is characterized in that, comprises the steps:
Step 1, operator send the mensuration request of quality defect of software by network;
Step 2, mensuration terminal response measure request;
Step 3, operating software mass defect measure module, and this step 3 comprises:
The dimension variable of step 3.1, definition quality defect of software variable, quality defect of software bioassay standard variable and each quality defect of software bioassay standard, described quality defect of software bioassay standard variable comprises: disturbance degree variable, frequency variable, perception difficulty variable and reparation difficulty variable;
Step 3.2, the value of each dimension variable to be quantized; The quantized value of the dimension variable of disturbance degree variable is respectively: almost without impact be 1, on function without impact but client can realize to be 2, have impact to be 3 on function, may become fatal is 4, fatal be 5; The quantized value of the dimension variable of frequency variable is respectively: to there will not be 1, to there will be 2, actually extremely easily appear as 3 when using; The quantized value of the dimension variable of perception difficulty variable is respectively: extremely embarrass 1, embarrass 2, be easily 3; The quantized value repairing the dimension variable of difficulty variable is respectively: be easily 1, embarrass 2, extremely embarrass 3;
Step 4, select a quantized value assignment to corresponding quality defect of software bioassay standard variable respectively, thus make described quality defect of software bioassay standard variable have a quantized value respectively;
Step 5, judge whether all quality defect of software bioassay standard variablees all have a quantized value, if not, then report to the police and point out, if so, then performing next step;
Step 6, pass through formula: quantized value=0.8* (quantized value of the quantized value+frequency variable of disturbance degree the variable)/2+0.2* (quantized value of the quantized value+reparation difficulty variable of perception difficulty variable)/2 of quality defect of software variable, calculates the quantized value of quality defect of software variable;
Step 7, judge software defect severity level according to the quantized value of quality defect of software variable, and the quantized value of this quality defect of software variable and this software defect severity level are shown to user;
Described software defect severity level comprises slight, general, serious and fatal;
Corresponding relation between the quantized value of described software defect severity level and described quality defect of software variable is: when the quantized value of quality defect of software variable is more than or equal to 3.4, and this software defect severity level is fatal; The quantized value of quality defect of software variable is less than 3.4, and when being more than or equal to 2.9, this software defect severity level is serious; The quantized value of quality defect of software variable is less than 2.9, and when being more than or equal to 2.4, this software defect severity level is general; The quantized value of quality defect of software variable is less than 2.4, and when being more than or equal to 1.0, this software defect severity level is slight;
Step 8, release quality defect of software measure module.
2. method for determinating severity levels of software defects as claimed in claim 1, it is characterized in that, described step 3.1 also comprises calls init (), each variable that initialization defines.
3. method for determinating severity levels of software defects as claimed in claim 1, it is characterized in that, described step 6 is by calling bugLevelCount () to run described formula.
4. method for determinating severity levels of software defects as claimed in claim 1, is characterized in that, described step 8 measures the release of module by calling doCancel () to realize quality defect of software.
5. method for determinating severity levels of software defects as claimed in claim 1, it is characterized in that, described step 7 shows quantized value and this software defect severity level of this quality defect of software variable by display.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110448608.7A CN102591774B (en) | 2011-12-28 | 2011-12-28 | Method for determining severity levels of software defects |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201110448608.7A CN102591774B (en) | 2011-12-28 | 2011-12-28 | Method for determining severity levels of software defects |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102591774A CN102591774A (en) | 2012-07-18 |
| CN102591774B true CN102591774B (en) | 2015-05-13 |
Family
ID=46480468
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201110448608.7A Active CN102591774B (en) | 2011-12-28 | 2011-12-28 | Method for determining severity levels of software defects |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102591774B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108829576A (en) * | 2018-04-14 | 2018-11-16 | 温州职业技术学院 | A kind of software defect detection method and its detection system |
| CN110225543B (en) * | 2019-05-30 | 2021-11-30 | 上海交通大学 | Mobile terminal software quality situation perception system and method based on network request data |
| CN111290969B (en) * | 2020-05-09 | 2021-10-22 | 四川新网银行股份有限公司 | Software quality analysis method based on characteristic frequency statistics |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599013A (en) * | 2009-06-26 | 2009-12-09 | 中国科学院软件研究所 | A kind of iteration project quantification monitoring method and system thereof based on defect driven |
| CN101968768A (en) * | 2010-10-22 | 2011-02-09 | 中国人民解放军理工大学 | Defect-based software security test requirement acquisition and classification method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2004086319A (en) * | 2002-08-23 | 2004-03-18 | Hitachi Information Systems Ltd | Software quality evaluating method and quality evaluating system |
| CN101819617A (en) * | 2010-05-06 | 2010-09-01 | 天津大学 | Software defect based method for quantificationally estimating software credibility |
-
2011
- 2011-12-28 CN CN201110448608.7A patent/CN102591774B/en active Active
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101599013A (en) * | 2009-06-26 | 2009-12-09 | 中国科学院软件研究所 | A kind of iteration project quantification monitoring method and system thereof based on defect driven |
| CN101968768A (en) * | 2010-10-22 | 2011-02-09 | 中国人民解放军理工大学 | Defect-based software security test requirement acquisition and classification method |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102591774A (en) | 2012-07-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8271961B1 (en) | Method and system for predictive software system quality measurement | |
| CN104375912B (en) | The measuring method and device of mobile terminal interim card | |
| CN102073006B (en) | Calibration method of electrical properties of solar cells | |
| CN104850495A (en) | Automatic detection method and device | |
| CN103246600A (en) | Fast verification method for software testing and evaluation | |
| CN102591774B (en) | Method for determining severity levels of software defects | |
| CN104360922A (en) | Method for automatically monitoring BMC working state based on ipmitool | |
| CN109142445B (en) | Enameled wire defect online detection method and detection device, computer device and computer readable storage medium | |
| TW200713485A (en) | Production system, production method, management device, management method and program | |
| CN110672019A (en) | Full-automatic MSA measuring tool for laser online thickness gauge and detection method thereof | |
| CN108344936B (en) | Test method of power semiconductor device | |
| CN110991124B (en) | Integrated circuit repairing method and device, storage medium and electronic equipment | |
| CN107423221A (en) | A kind of web applies sustainable method of testing and system | |
| CN114138581A (en) | Mainboard test method and system | |
| CN103217558A (en) | Probe card maintaining method | |
| CN117574200A (en) | Membership-based transformer health state evaluation method and system | |
| CN101673200A (en) | Method and device for detecting user input model | |
| CN110535997A (en) | A kind of calibration method, device, equipment and the storage medium of terminal screen light leakage | |
| CN113704871B (en) | Method and device for determining wheel bending fatigue, terminal equipment and medium | |
| CN107786264B (en) | ONT power calibration method based on data analysis | |
| CN106093222A (en) | Chromatographic detection apparatus stratification appraisal procedure in a kind of electrical network system | |
| CN101308016B (en) | Electric products panel light transmission checking method | |
| CN104483613A (en) | LED test method | |
| CN204630542U (en) | Based on the pressure vessel ellipsoidal head testing instruments of ellipsograph | |
| JP6964790B2 (en) | Quantitative test method for fringes of optical material |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C53 | Correction of patent for invention or patent application | ||
| CB03 | Change of inventor or designer information |
Inventor after: Li Yunlong Inventor after: Wang Dongsheng Inventor after: Hu Lingli Inventor after: Ma Xiaopeng Inventor after: Li Xiankun Inventor after: Liu Jing Inventor before: Li Yunlong Inventor before: Wang Dongsheng Inventor before: Hu Lingli Inventor before: Ma Xiaopeng Inventor before: Li Xiankun |
|
| COR | Change of bibliographic data |
Free format text: CORRECT: INVENTOR; FROM: LI YUNLONG WANG DONGSHENG HU LINGLI MA XIAOPENG LI XIANKUN TO: LI YUNLONG WANG DONGSHENG HU LINGLI MA XIAOPENG LI XIANKUN LIU JING |
|
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |