CN102902622A - Multi-computing-based software project test quantitative evaluating method and system - Google Patents
Multi-computing-based software project test quantitative evaluating method and system Download PDFInfo
- Publication number
- CN102902622A CN102902622A CN2012103428604A CN201210342860A CN102902622A CN 102902622 A CN102902622 A CN 102902622A CN 2012103428604 A CN2012103428604 A CN 2012103428604A CN 201210342860 A CN201210342860 A CN 201210342860A CN 102902622 A CN102902622 A CN 102902622A
- Authority
- CN
- China
- Prior art keywords
- test
- stage
- score value
- software
- demand point
- 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.)
- Granted
Links
Images
Landscapes
- Stored Programmes (AREA)
Abstract
The invention discloses a multi-computing-based software project test quantitative evaluating method and system. The multi-computing-based software project test quantitative evaluating method comprises the steps of: aiming at demand points of a software test project in each stage, presetting a test case; allocating a stage score and a demand point score for each stage according to a total score of the software test project; testing a software product by using all unsanctioned test cases in a stage to which the current test belongs, recording the quantity of sanctioned or unsanctioned test cases of the software product in the local test; when the software product passes all test cases in the stage to which the current test belongs, scoring the stage according to a preset scoring formula; and when the software product completes all stages of test, accumulating according to stage scores obtained in all stages, so as to obtain an evaluating fraction of the software test project by a software manufacturer. By adopting the method and the system, the staging evaluation of the project can be realized through a quantitative evaluating factor, and the software completing quality and the project test evaluating level are improved.
Description
Technical field
The present invention relates to software testing technology, particularly relate to Software project testing quantitative estimation method and system based on multiple calculating.
Background technology
Be born so far from computing machine, computing machine becomes the swiftest and the most violent science and technology of contemporary development undoubtedly.Today, computing machine has been penetrated into the various aspects of people's life, such as industry, agricultural, finance, science and education health, national defence, the lives of the people etc.Along with increasing severely with day of computer requirements and dependence, scale and the complicacy of computer system sharply increase.Its software development cost and the economic loss that causes owing to software fault also increase, and the software quality problem has become the common focus of paying close attention to of people.The software developer is in order to occupy market, software quality as one of important goal of enterprise, in order to avoid in keen competition, be eliminated.The user also wishes to select the software of high-quality certainly in order to guarantee own professional finishing smoothly.Some crucial application are had higher requirement to software quality such as Airline Reservation System, bank settlement system, securities exchange system, automatic Flight Control Software, military defense, nuclear plant safety control system.The software that service property (quality) is not good enough also may cause catastrophic consequence.2003, software issue caused Northeastern United States and Canada to have a power failure, and causes 5,000 ten thousand people influenced, 3 people forfeiture, and various estimated amounts of damage are about 6,000,000,000 dollars.2004, North America bank was owing to the defective of a new software of installing, so that millions of clients receives impact, the reparation of this defective has spent the time of whole fortnight, and the loss that causes is in hundred million yuan.United States Naval Aircraft fell in 2000, caused 4 people die (control software issue).Korea S's airplane crash in 1997 causes 225 people die (radar control software issue).In April, 2003, company that offers a loan for the student specially of the U.S. makes mistakes owing to software, and 800,000 loan interest rates of erroneous calculations have caused 8,000,000 dollars interest rate loss.Therefore, many scientists are placed on software quality the status that has precedence over raising software function and performance when 21 st Century computer science developing direction and measurement.
No matter from which kind of angle, software test all is requisite activity of software development process, is the final reexamination to software requirement analysis, design specification and coding; It is the committed step of software quality assurance.Software test is according to the stipulations in each stage of software development and the inner structure of software, well-designed a collection of test case (Output rusults that comprises input data and expection thereof), and utilize these test cases to remove working procedure, to find the not meeting process that mass property requires (being defective or mistake) in the software.At present, many software developments mechanism will develop putting into more than 40% among the software test of strength, embody the requirement of abundant attention software quality.
But there are two large defectives in traditional software test wire examination method: the first, and use-case test wire examination method is simple.Test case with " by " with " by " expression test result, for the test case of " by " by repeatedly revising, after the correction problem " by " test.This Assessment is difficult to reasonably examine the software test situation; The second, the Software project testing examination is not comprehensive.Software test is only for software acceptance testing, for unit testing, integration testing and system testing only as the Acceptance Test entry criteria, and as Software project testing examination statistical considerations.This type of examination appraisal procedure is too simple, is difficult to the whole development process of project is carried out omnibearing assessment, and is difficult to the integrality of reflection system self and developer for the ability of the software maintenance in later stage.
Summary of the invention
Based on this, be necessary that for the problems referred to above a kind of Software project testing quantitative estimation method and system based on multiple calculating is provided, and the assessment that can carry out comprehensively, quantize the Software project testing quality provides the foundation of reference for reducing the software quality risk.
A kind of Software project testing quantitative estimation method based on multiple calculating comprises:
For the demand point of Software Testing Project at stages, default test case;
Total points score value according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages;
Utilize all unsanctioned test cases in the stage under the current test that software product is tested, record this software product in this test by or the quantity of unsanctioned test case;
When software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
When software product is finished the test of stages, accumulate according to the stage mark that stages is obtained, obtain the software manufacturer to the examination mark of described Software Testing Project.
Correspondingly, a kind of Software project testing quantitative evaluation system based on multiple calculating comprises:
The exam pool creating unit is used for for the demand point of Software project testing at stages, default test case;
The score value allocation units that link to each other with described exam pool creating unit, the total points score value that is used for according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages;
The test record unit, be used for this software product of record this test by or the quantity of unsanctioned test case;
Be connected to the use-case screening unit between described exam pool creating unit and the described test record unit, be used for utilizing all unsanctioned test cases in affiliated stage of current test that software product is tested;
Stage of linking to each other with described test record unit scoring unit, be used at software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
Overall examination unit with described stage scoring unit links to each other is used for accumulating according to the stage score value that stages is obtained when software product is finished the test of stages, and acquisition software manufacturer is to the examination mark of described software project.
Implement the present invention, have following beneficial effect:
This method is applied to process and the result of test on the basis of analysis software test basic procedure, and for the shortcoming of off-the-shelf item testing evaluation, proposes to test from demand point and two levels of use-case, namely formulates the multiple testing method.According to standards of grading and the step that the project situation is divided test phase, formulation stages, the quantizing examination factor is set up science examines mechanism evaluation item.
Description of drawings
Fig. 1 is the process flow diagram that the present invention is based on the Software project testing quantitative estimation method of multiple calculating;
Fig. 2 is the embodiment process flow diagram that the present invention is based on the Software project testing quantitative estimation method of multiple calculating;
Fig. 3 is the synoptic diagram that the present invention is based on the Software project testing quantitative evaluation system of multiple calculating;
Fig. 4 is the embodiment synoptic diagram that the present invention is based on the Software project testing quantitative evaluation system of multiple calculating.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, the present invention is described in further detail below in conjunction with accompanying drawing.
Software test: move or measure the process of certain system with artificial or automatic means, its purpose be to check it whether to satisfy the demand of regulation or understand fully expected results and actual result between difference.
Software test should test to guarantee justice, just, correct by the third party in principle.But numerous items has been ignored the importance of test at present, not according to standard and the basic procedure of Software project testing, but arbitrarily works out testing process, test case and test oracle result by the side of undertaking the construction of.Cause operating the problems such as lack of standardization, testing process freeing, use-case personalization.Undertaking the construction of after developer's project winning a bid of some project, and half-hearted carrying out the work, whether normally only surprise is finished surface work when the stage of project is tested, conscientiously do not check the operation of software and system afterwards, brings serious threat for the persistence application of software and system.Along with the demand of software quality raising and the widespread use of software test, the quality of Software project testing and examination also more and more are concerned by people.But mainly rest on the research of paying close attention to software test, software quality, quality management and quality assurance and software process maturity at present, and relatively lack about the wire examination method of Software project testing quality.Method provided by the invention has been filled up above-mentioned blank, as shown in Figure 1.
Fig. 1 is the process flow diagram that the present invention is based on the Software project testing quantitative estimation method of multiple calculating, comprising:
S101: for the demand point of Software Testing Project at stages, default test case;
S102: the total points score value according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages;
S103: utilize all unsanctioned test cases in the stage under the current test that software product is tested, record this software product in this test by or the quantity of unsanctioned test case;
S104: when software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
S105: when software product is finished the test of stages, accumulate according to the stage mark that stages is obtained, obtain the software manufacturer to the examination mark of described Software Testing Project.
At first, the present invention has set up the mechanism of loop test, launch test from demand point and two levels of test case, multiple testing method and step have namely been formulated: on the one hand, demand point for stages arranges test case, can reach each demand point of omnibearing test, check the requirement in the description that whether can satisfy the demands.
Wherein, described test case: be a group of test input, executive condition and expected results working out for certain special objective, in order to test certain Program path or examine and whether satisfy certain particular demands.
The stage of software test comprises unit testing, integration testing, affirmation test, system testing and Acceptance Test.Be described below,
Unit testing: refer to the I test cell in the software is checked and verifies.For the implication of unit in the unit testing, in general, remove to judge its concrete meaning according to actual conditions, refer to a function such as unit in the C language, the unit refers to a class in the Java, can refer to a window or a menu etc. in the patterned software.Generally speaking, the unit is exactly the tested functional module of the minimum of artificial regulation.Unit testing is other test activity of lowermost level that will carry out in software development process, the separate unit of software will with the isolated situation of other parts of program under test.
Integration testing: also be assembling test or joint test.On the basis of unit testing, all modules are assembled into subsystem or system according to designing requirement (as according to structural drawing), carry out integration testing.Practice shows, although some modules can be worked individually, can not guarantee to couple together also can work normally.Program probably comes out on the overall situation in some local reflection out problem not, affects the realization of function.
Confirm test: purpose is that the user to future shows that system can work as pre-provisioning request.Behind integration testing, according to design all module assembleds are become complete software systems, interface error has also been got rid of substantially, the further validity of verifying software with that, the task of affirmation test that Here it is, namely the function of software and performance are as user institute reasonable comtemplation.
System testing: be that other elements such as the software that will confirm, computer hardware, peripheral hardware, network combine, carry out the various assembling tests of infosystem and confirm test, system testing is the test of carrying out for whole product systems, purpose is the definition whether verification system has satisfied requirement specification, find out and be not inconsistent with requirement specification or the place of contradiction with it, thereby propose more perfect scheme.After pinpointing the problems, system testing to through debugging locate errors reason and position, then correct.Be based on the black box class testing of entire system statement of requirements book, answer the parts of all associatings of covering system.Object not only comprises the software that needs test, also will comprise hardware, the peripheral hardware that software relies on even comprise some data, some support software and interface thereof etc.
Acceptance Test: in a stage of system development life cycle methodology, at this moment relevant user and/or independent test personnel test and receive system according to test plan and result.It allows system user whether determine receiving system.It is the test whether a definite product can satisfy contract or user's defined demand.This is managerial and defensive control.
The present invention is directed to Software Testing Project in the demand point of above-mentioned stages, default test case utilizes described test case to realize the science to software product, comprehensive test.Total points score value according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages, then can quantize standards of grading, realizes the quantitative evaluation to software test.Utilize all unsanctioned test cases in affiliated stage of current test that software product is tested, require the software business man must pass through all test cases, otherwise the software business man needs make amendment repeated test to its software product.This method record this software product in each test by or the quantity of unsanctioned test case, use it as score basis.Obviously, outstanding software business man can be at less number of times, spend the short time to finish the test case in all stages.On the contrary, the weak or careless software business man who deals with of strength will manifest more mistake in test, need repeatedly to revise, and spends the more time.So last quantizing examination mark will show each software business man's strength, and the quality of assessing its software product of producing, be conducive to realize follow-up maintenance and risk profile for software.
On the other hand at software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked, can check the stage performance of software project, deal with the task that formula is finished each stage to prevent the developer.The project check appraisal procedure of a kind of science that the present invention sets up than traditional project testing, only needs just can carry out next stage test preliminary work by the test in this stage, by that analogy, tests at last examination.The influence factor that the test case in each stage and test result are only carried out the work as the next stage test and not as the considerations of the whole performance of project.Also have, traditional approach in the test result in each stage with " by " do not weigh with " by ", this simple and crude Assessment is also failed the difficulty action accomplishment of measurement project of science.This method is for traditional project testing shortcoming, this method proposes by the quantizing examination factor, realize the stage by stage examination of project testing and the quantification test of use-case, when software product is finished the test of stages, accumulate according to the stage mark that stages is obtained, obtain the software manufacturer to the examination mark of described Software Testing Project, to improve the project testing appreciable levels, improve the project difficulty action accomplishment.
Fig. 2 is the embodiment process flow diagram that the present invention is based on the Software project testing quantitative estimation method of multiple calculating.Compared to Figure 1, Fig. 2 is the process flow diagram of the specific embodiment of the invention, below in conjunction with Fig. 2 present embodiment is launched to specify.
S201: for the demand point of Software Testing Project at stages, default test case;
S202: the score value according to total points is stages mean allocation mark, as the stage score value of stages;
S203: be demand point mean allocation mark in this stage according to the score value of the stage score value of current generation, as the demand point score value of each demand point;
S204: utilize all unsanctioned test cases in the stage under the current test that software product is tested, record this software product in this test by or the quantity of unsanctioned test case;
S205: when software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
S206: after described software product is by all test cases in the stage under the current test, just carry out the test of next stage;
S207: when software product is finished the test of stages, accumulate according to the stage mark that stages is obtained, obtain the software manufacturer to the examination mark of described Software Testing Project.
First, in the demand point of stages test case is set for this Software Testing Project, especially, can demand point be checked according to the requirement in the Specification that the test case that must preset can satisfy the demand in each stage of software test in all directions.
The second, by the quantizing examination factor, realize the stage by stage examination of project testing and the quantification test of use-case.The quantizing examination factor:
(1) quantize each test score value in stage, if total points is S, total Z test phase, each stage divide equally total score value then each stage score value be
The test in each stage is of equal importance like this, avoids some developer only to assault last test, and deals with the test assignment of finishing other stages of formula;
(2) score value of quantification demand point is if the demand point that the K stage need to test has N
KIndividual, each demand point is total points value stage by stage all, and namely each demand point score value is the k stage
(3) quantize the score value of test case, suppose that the use-case quantity that M demand point for the K stage designs is
Each use-case is divided equally the demand point score value, and namely each test case score value of M demand point in K stage is
(4) quantize every score value of taking turns test, suppose K stage M demand point process
Wheel repeatedly test just passes through, and every quantity of testing by test of taking turns is
Wherein not yet begin test for the 0th time, therefore
Then K stage M demand point i wheel test score value is:
Namely
Present each wheel test to the influence degree of this demand point score by the proportion mode of successively decreasing herein, obviously previous round tests affect degree is taken turns test greater than rear one, and therefore use-case test in early stage is by more, and total points is then higher.
Obviously, except the score value in each stage of mean allocation, can also be according to the importance in each stage, have with stressing and give higher score value to some stage, make this appraisal procedure pointed.
According to the score value of the stage score value of current generation, in conjunction with the weight proportion of each demand point in this stage, be each demand point distribution requirements point score value by described weight proportion.In certain one-phase, some have the demand point of material impact to this software product, can give higher score value by weight proportion, catch the principal contradiction of this stage demand, and the emphasis of the outstanding demand of identification is held essence.
The 3rd, utilize all unsanctioned test cases in affiliated stage of current test that software product is carried out repeated test.All test cases that demand point is corresponding, the use-case that does not pass through for test identifies, and represents that this use-case needs repeated test.If all use-case tests are passed through, then the test of this demand point is finished, and finishes the test of this demand point.When this stage also had unsanctioned test case, the software business man must make amendment for this demand point perfect, the correction problem.Test case is opaque for the developer, can be encapsulated within this software testing system, and system only returns and demonstrates which demand point and fail to reach expected results.Be conducive to like this prevent the developer from dealing with the single use-case demand of satisfying of formula and data falsification and professional or develop dead function corresponding to single use-case.
Test last time sign fail use-case by test, again identify for the use-case of again failing by test, represent that this use-case also need carry out repeated test.If the use-case that identified all last time all passes through test in this test, then the test of this demand point is finished.For example:
M demand point process
Wheel is tested to such an extent that be divided into:
This formula has taken into full account each demand point test case, both with testing time as the calculating factor, also will test by quantity at every turn and add up, considered the impact of these two factors.
In K stage, test to such an extent that be divided into:
Through the test in Z stage, the test total points is:
Above formula has considered the test case of each each demand point of stage, with testing time and testing by quantity as the calculating factor at every turn, in addition, the last examination total points of project is comprised of each stage mark, and each stage proportion is identical, like this, whole performance that can more rational statistical item.
After described software product is by all test cases in the stage under the current test, just carry out the test of next stage.Carry out the test in each stage according to unit testing, integration testing, affirmation test, system testing, Acceptance Test successively, can prevent the situations such as software business man's leapfrog, omission, also be convenient to monitoring software merchant's job schedule simultaneously.In the middle of the above-mentioned stages, some demand point is separate, relevance is little, in the middle of the conventional art, sometimes in order to accelerate completion of works, at one time the demand point in a plurality of stages is tested, and this way has often been ignored the demand point examination of preliminary stage.So the present invention is than having more science.At last, when software product is finished the test of stages, accumulate according to the stage mark that stages is obtained, obtain the software manufacturer to the examination mark of described Software Testing Project.
Below exemplifying concrete example is illustrated:
Total points is 500, totally 5 stages, each stage divide equally total score value then each stage score value be 100;
There are 10 demand points in the 1st stage, and each demand point is total points value stage by stage all, and namely each demand point score value is 10 the k stage.
The use-case quantity of the 1st demand point design is 5 for the 1st stage, and each use-case is divided equally the demand point score value, and namely the 1st each use-case score value of demand point is the 1st stage: 2
5 test cases of the 1st stage the 1st demand point are taken turns to test through 3 and are just passed through, and test being respectively by the use-case number:
The 1st test is by 3 use-cases (totally 5 use-cases, take turns test at this and need test 5-0=5 use-case), the 2nd test is by 1 use-case (totally 5 use-cases, 3 use-cases in last round of test, have been passed through, the epicycle test needs 5-0-3=2 use-case of test), the 3rd test is by 1 use-case (totally 5 use-cases have passed through 3+1=4 use-case in upper two-wheeled test, and the epicycle test needs 5-0-3-1=1 use-case of test).
Then this demand point must be divided into after taking turns test through 3:
Other demand point test scores are also so calculated; This stage test to such an extent that be divided into the total points of this stage all demand points test scores;
And the test total points is the total points of all stage test scores.
This method is abandoned in the past Software project testing and is only examined assessment for the software test acceptance phase, but takes into full account the test case in each stage, by the quantizing examination factor, realizes that the stage by stage examination of project testing and the quantification of use-case test.The software pilot project often has a plurality of developers to participate at present, and namely a project is finished respectively by a plurality of developers, compares at last the preferred development merchant, and perhaps a plurality of developers participate in integrated popularization, but need to distribute according to developer's finished item situation.Therefore, can contrast each developer's project check mark by this method, for can not be by not adopting without exception that standard is divided, select outstanding developer and carry out project later stage work and integrated popularization for the mark ordering of then carrying out that divides by standard.
Fig. 3 is the synoptic diagram that the present invention is based on the Software project testing quantitative evaluation system of multiple calculating, comprising:
The exam pool creating unit is used for for the demand point of Software project testing at stages, default test case;
The score value allocation units that link to each other with described exam pool creating unit, the total points score value that is used for according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages;
The test record unit, be used for this software product of record this test by or the quantity of unsanctioned test case;
Be connected to the use-case screening unit between described exam pool creating unit and the described test record unit, be used for utilizing all unsanctioned test cases in affiliated stage of current test that software product is tested;
Stage of linking to each other with described test record unit scoring unit, be used at software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
Overall examination unit with described stage scoring unit links to each other is used for accumulating according to the stage score value that stages is obtained when software product is finished the test of stages, and acquisition software manufacturer is to the examination mark of described software project.
Fig. 3 is corresponding with Fig. 1, identical among the figure in the method for operation of unit and the method.Need to prove that method of the present invention can be achieved on the software test evaluating system as shown in Figure 3, the computer system is with the use-case test and the integrated combination of testing evaluation of software.
Fig. 4 is the embodiment synoptic diagram that the present invention is based on the Software project testing quantitative evaluation system of multiple calculating.
As shown in Figure 4, described score value allocation units comprise:
Stage score value dispensing unit, the score value that is used for according to total points is stages mean allocation mark, as the stage score value of stages.
As shown in Figure 4, described score value allocation units comprise:
Demand point score value the first dispensing unit is used for score value according to the stage score value of current generation and is the demand point mean allocation mark in this stage, as the demand point score value of each demand point.
Described score value allocation units can also comprise:
Demand point score value the second dispensing unit is used for the score value according to the stage score value of current generation, in conjunction with the weight proportion of each demand point in this stage, is each demand point distribution requirements point score value by described weight proportion.
As shown in Figure 4, present embodiment also comprises:
Be connected to the stage monitoring unit of described test record unit and described stage scoring between the unit, be used for after described software product is by all test cases in the stage under the current test, just carrying out the test of next stage.
Fig. 4 is corresponding with Fig. 2, identical among the figure in the method for operation of unit and the method.
The above embodiment has only expressed several embodiment of the present invention, and it describes comparatively concrete and detailed, but can not therefore be interpreted as the restriction to claim of the present invention.Should be pointed out that for the person of ordinary skill of the art without departing from the inventive concept of the premise, can also make some distortion and improvement, these all belong to protection scope of the present invention.Therefore, the protection domain of patent of the present invention should be as the criterion with claims.
Claims (10)
1. the Software project testing quantitative estimation method based on multiple calculating is characterized in that, comprising:
For the demand point of Software Testing Project at stages, default test case;
Total points score value according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages;
Utilize all unsanctioned test cases in the stage under the current test that software product is tested, record this software product in this test by or the quantity of unsanctioned test case;
When software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
When software product is finished the test of stages, accumulate according to the stage mark that stages is obtained, obtain the software manufacturer to the examination mark of described Software Testing Project.
2. the Software project testing quantitative estimation method based on multiple calculating according to claim 1 is characterized in that, is the step of stages allocated phase score value according to the total points score value of described Software Testing Project, comprising:
Score value according to total points is stages mean allocation mark, as the stage score value of stages.
3. the Software project testing quantitative estimation method based on multiple calculating according to claim 1 and 2 is characterized in that, is the step of each demand point distribution requirements point score value according to the demand point quantity of stages, comprising:
Be demand point mean allocation mark in this stage according to the score value of the stage score value of current generation, as the demand point score value of each demand point.
4. the Software project testing quantitative estimation method based on multiple calculating according to claim 1 and 2 is characterized in that, is the step of each demand point distribution requirements point score value according to the demand point quantity of stages, comprising:
According to the score value of the stage score value of current generation, in conjunction with the weight proportion of each demand point in this stage, be each demand point distribution requirements point score value by described weight proportion.
5. according to claim 1 to 4 each described Software project testing quantitative estimation methods based on multiple calculating, it is characterized in that:
After described software product is by all test cases in the stage under the current test, just carry out the test of next stage.
6. the Software project testing quantitative evaluation system based on multiple calculating is characterized in that, comprising:
The exam pool creating unit is used for for the demand point of Software project testing at stages, default test case;
The score value allocation units that link to each other with described exam pool creating unit, the total points score value that is used for according to described Software Testing Project is stages allocated phase score value, and is each demand point distribution requirements point score value according to the demand point quantity of stages;
The test record unit, be used for this software product of record this test by or the quantity of unsanctioned test case;
Be connected to the use-case screening unit between described exam pool creating unit and the described test record unit, be used for utilizing all unsanctioned test cases in affiliated stage of current test that software product is tested;
Stage of linking to each other with described test record unit scoring unit, be used at software product during by all test cases in the stage under the current test, according to the testing time in this stage, the each quantity of the test case of passing through and demand point score value that each demand point is distributed tested, according to default evaluate formula this class is marked;
Overall examination unit with described stage scoring unit links to each other is used for accumulating according to the stage score value that stages is obtained when software product is finished the test of stages, and acquisition software manufacturer is to the examination mark of described software project.
7. the Software project testing quantitative evaluation system based on multiple calculating according to claim 6 is characterized in that described score value allocation units comprise:
Stage score value dispensing unit, the score value that is used for according to total points is stages mean allocation mark, as the stage score value of stages.
8. according to claim 6 or 7 described Software project testing quantitative evaluation systems based on multiple calculating, it is characterized in that described score value allocation units comprise:
Demand point score value the first dispensing unit is used for score value according to the stage score value of current generation and is the demand point mean allocation mark in this stage, as the demand point score value of each demand point.
9. according to claim 6 or 7 described Software project testing quantitative evaluation systems based on multiple calculating, it is characterized in that described score value allocation units comprise:
Demand point score value the second dispensing unit is used for the score value according to the stage score value of current generation, in conjunction with the weight proportion of each demand point in this stage, is each demand point distribution requirements point score value by described weight proportion.
10. according to claim 6 to 9 each described Software project testing quantitative evaluation systems based on multiple calculating, it is characterized in that, also comprise:
Be connected to the stage monitoring unit of described test record unit and described stage scoring between the unit, be used for after described software product is by all test cases in the stage under the current test, just carrying out the test of next stage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210342860.4A CN102902622B (en) | 2012-09-14 | 2012-09-14 | Based on Software project testing quantitative estimation method and the system of multiple calculating |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201210342860.4A CN102902622B (en) | 2012-09-14 | 2012-09-14 | Based on Software project testing quantitative estimation method and the system of multiple calculating |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN102902622A true CN102902622A (en) | 2013-01-30 |
| CN102902622B CN102902622B (en) | 2015-11-18 |
Family
ID=47574867
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201210342860.4A Active CN102902622B (en) | 2012-09-14 | 2012-09-14 | Based on Software project testing quantitative estimation method and the system of multiple calculating |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN102902622B (en) |
Cited By (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104317725A (en) * | 2014-11-18 | 2015-01-28 | 电信科学技术第十研究所 | Computer implementation method of software testing, computer and system |
| CN104376419A (en) * | 2014-11-20 | 2015-02-25 | 中国南方电网有限责任公司 | Quantitative evaluation statistic method for safety assessment on scheduling operation work of power plant |
| CN106528101A (en) * | 2016-10-31 | 2017-03-22 | 努比亚技术有限公司 | Repair rate calculation method and device |
| CN106649079A (en) * | 2015-11-03 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Evaluation method and device for testing requirements of software system |
| CN107844423A (en) * | 2017-11-10 | 2018-03-27 | 郑州云海信息技术有限公司 | A kind of appraisal procedure of software test completeness |
| CN107871189A (en) * | 2016-09-23 | 2018-04-03 | 国家电网公司 | Sulfur hexafluoride gas management method and system |
| CN108874676A (en) * | 2018-06-27 | 2018-11-23 | 北京金山安全软件有限公司 | Method and device for distributing test resources |
| CN112395148A (en) * | 2019-08-14 | 2021-02-23 | 北京国双科技有限公司 | Quantification method and device for micro-service evaluation, computer equipment and storage medium |
| CN113077120A (en) * | 2021-03-10 | 2021-07-06 | 山东英信计算机技术有限公司 | Server assembly quality scoring method, system, terminal and storage medium |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107122302A (en) * | 2017-04-28 | 2017-09-01 | 郑州云海信息技术有限公司 | A kind of software test measure of effectiveness and appraisal procedure |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101604288A (en) * | 2009-07-10 | 2009-12-16 | 北京航空航天大学 | A kind of method for evaluating software quality based on test data |
| CN101976222A (en) * | 2010-11-03 | 2011-02-16 | 北京航空航天大学 | Framework-based real-time embedded software testability measuring method |
| CN102279793A (en) * | 2011-08-05 | 2011-12-14 | 清华大学 | Method for measuring dependability of component based on entropy |
-
2012
- 2012-09-14 CN CN201210342860.4A patent/CN102902622B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101604288A (en) * | 2009-07-10 | 2009-12-16 | 北京航空航天大学 | A kind of method for evaluating software quality based on test data |
| CN101976222A (en) * | 2010-11-03 | 2011-02-16 | 北京航空航天大学 | Framework-based real-time embedded software testability measuring method |
| CN102279793A (en) * | 2011-08-05 | 2011-12-14 | 清华大学 | Method for measuring dependability of component based on entropy |
Cited By (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104317725A (en) * | 2014-11-18 | 2015-01-28 | 电信科学技术第十研究所 | Computer implementation method of software testing, computer and system |
| CN104376419A (en) * | 2014-11-20 | 2015-02-25 | 中国南方电网有限责任公司 | Quantitative evaluation statistic method for safety assessment on scheduling operation work of power plant |
| CN106649079A (en) * | 2015-11-03 | 2017-05-10 | 阿里巴巴集团控股有限公司 | Evaluation method and device for testing requirements of software system |
| CN106649079B (en) * | 2015-11-03 | 2019-10-25 | 阿里巴巴集团控股有限公司 | Software system test need assessment method and device |
| CN107871189A (en) * | 2016-09-23 | 2018-04-03 | 国家电网公司 | Sulfur hexafluoride gas management method and system |
| CN106528101A (en) * | 2016-10-31 | 2017-03-22 | 努比亚技术有限公司 | Repair rate calculation method and device |
| CN107844423A (en) * | 2017-11-10 | 2018-03-27 | 郑州云海信息技术有限公司 | A kind of appraisal procedure of software test completeness |
| CN108874676A (en) * | 2018-06-27 | 2018-11-23 | 北京金山安全软件有限公司 | Method and device for distributing test resources |
| CN112395148A (en) * | 2019-08-14 | 2021-02-23 | 北京国双科技有限公司 | Quantification method and device for micro-service evaluation, computer equipment and storage medium |
| CN113077120A (en) * | 2021-03-10 | 2021-07-06 | 山东英信计算机技术有限公司 | Server assembly quality scoring method, system, terminal and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN102902622B (en) | 2015-11-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102902622B (en) | Based on Software project testing quantitative estimation method and the system of multiple calculating | |
| Amland et al. | Risk based testing and metrics | |
| Park et al. | Remaining and emerging issues pertaining to the human reliability analysis of domestic nuclear power plants | |
| Charalambous et al. | Water balance-the next stage | |
| CN101236136A (en) | Curve plotting method characterizing aeroplane service lifetime degree and applications | |
| Ashby et al. | An approach for conducting a cost benefit analysis of aircraft engine prognostics and health management functions | |
| Cotter | Structural analysis of Hfacs in unmanned and manned air vehicles | |
| Nikkhah et al. | Evaluating the implementation of strategies in plants using balanced scorecard (BSC): A case study | |
| Metzger | Measuring quality cost effects on productivity using data envelope analysis | |
| Khattak et al. | Risk management in construction projects: Perspective of contractors and owners | |
| Ramesh et al. | Airplane system design for reliability and quality | |
| Jang et al. | Development of a regulatory framework for risk-informed decision making | |
| US20060259443A1 (en) | Systems engineering parametric cost model | |
| Vaurio | Developments in importance measures for risk-informed ranking and other applications | |
| Serbanescu | A PSA practitioner and safety decision making person view on some issues related to multiple unit psa analyses | |
| Fan et al. | A Quality Measurement Method For Maintenance of Space TT&C Software Based on Objective Data | |
| Putra et al. | Competitiveness Enhancement and MSME Performance Through Development of Internal, External, and Entreprenual Skills in Bali Province | |
| Ouanouki et al. | IT Process Conformance Measurement: A Sarbanes-Oxley Requirement | |
| Sullivan et al. | Defense acquisitions: Measuring the value of DOD’s weapon programs requires starting with realistic baselines | |
| Shahid Saheb et al. | Factors Affecting on Budget Utilization in Bahirdar City Administration Health Department, Ethiopia | |
| Swanepoel et al. | A structured approach to risk identification for projects in a research environment | |
| Mohammed et al. | The Impact of Government Expenditure on Economic Growth in Ethiopia | |
| Apostolakis et al. | Decision analysis and its application to the frequency of containment integrated leakage rate tests | |
| Malinen et al. | MS-E2177 COVID-19 impact on credit loss modelling | |
| Ghanim | Risk-based test estimation |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 510699 No. 75 Meihua Road, Guangzhou, Guangdong, Yuexiu District Patentee after: ELECTRIC POWER DISPATCHING CONTROL CENTER OF GUANGDONG POWER GRID Co.,Ltd. Address before: 510699 No. 75 Meihua Road, Guangzhou, Guangdong, Yuexiu District Patentee before: ELECTRIC POWER DISPATCH CONTROL CENTER OF GUANGDONG GRID Co. |
|
| CP01 | Change in the name or title of a patent holder |