Method and system for quantitatively estimating code size of new requirements based on weight adjustment

Abstract

The invention discloses a method and a system for quantitatively estimating the code size of new requirements based on weight adjustment. The method comprises the following steps of: performing characteristic extraction according the conventional N requirements of a software project; selecting the characteristic extraction data of m requirements, setting the characteristic extraction data of each requirement to be RSi, setting an adjustment parameter gamma of the software project to be 1 and calculating an estimated value ESi of the code size of the requirement RSi; calculating the ratios gammai of each estimated value to a real value, and taking the value of the adjustment parameter gamma as an average value of all the ratios gammai; performing the characteristic extraction on the new requirements of the software project; calculating distances Dij between each new requirement Rnewi and the conventional requirements; calculating the weight Wij of influence among the requirements; and calculating the estimated value Ei of the code size of the new requirements Rnewi according to a formula. In the method of the invention, similarity between the new requirements and the conventional requirements of the software project is calculated, and the characteristic data of all the conventional requirements is used, so the to-be-generated code size of the new requirements can be accurately quantized.

Description

technical field [0001] The invention belongs to the technical field of computer software development, and relates to a quantitative evaluation method and a system for code quantity generated by new requirements. Background technique [0002] The Standish Group analyzed 8,000 projects in 1995, and the results showed that 31% of the projects were canceled before completion, 52.7% of the projects were in trouble, and only 16.2% of the projects were successful. In 2004, Standish Group surveyed 13,522 software projects, and the results showed that 18% of the projects failed, 53% of the projects were questioned, and only 29% of the projects were successful. Software projects often end in failure, one of the important reasons is that requirements are often in the process of evolution. Existing research shows that the evolution of requirements in software projects is very frequent and largely determines the success or failure of software projects. [0003] Developers of software p...

AI Technical Summary

Problems solved by technology

[0010] When estimating the impact of the above two types of methods, it is necessary to first determine the code corresponding to the evolving requirements. For the added new requirements, it is impossible to establish an effective association between the new requirements and the existing codes, so it is impossible to accurately estimate the new requirements. the amount of code that will be generated

Images