Software Project Estimation Model Of Research And Practice

Estimation of software project is the precondition for controlling properly and managing scientifically software products. The estimation of software project is usually complex, which is caused by many reasons, such as complexity of software itself, lacking of experience and data, shorting of estimate tools and approaches, and some man-made mistakes, thus resulting in great difference between the estimation and the practical case.Estimation of software project is one of the most difficult and important activities during the management of project. Estimations of a project's scale, workload, time, cost, key resources is also an indispensable work for making plan and adjusting plan, tracking and supervising projects. How to estimate the scale, cost, time required of the project on the base of previous projects' developing experiences is the problem of estimation that has to be solved. The problem to be solved for software project estimation is how to utilize the mathematical model to make project estimation according to previous experiences. The ultimate goal of software estimation is to confirm the development cost, development period by estimation of software management and development workload, to lay basis for project bid, proposal and development. At the same time, The project management competencies and software productivity is improved, the project cost and development period is reduced, through the analysis and the summarization of quantitative data, so that the expense caused by wrong estimation is reduced to the fullest extent.Current estimation models DELPHI approach, analogy approach, tri-point technique approach, LOC estimate approach, function point analyzing approach and COCOMO model has been analyzed in this paper. On the basis, the approach of program unit estimation is proposed, and its application, including the advantages and the shortcomings, has been studied.For the approach of program unit estimation, according to the" The classification rules for program unit", the system requirement of the whole software project is divided into three class "simple", " moderate"...