On the use of software cost models

The authors oppose the idea that a model is the solution to the estimation problem, but are convinced that the use of a model can contribute to the control of software development, if it is used properly.

Abstract

A number of methods and tools have been developed over the years to meet the increasing need to control software development. Among the tools are software cost estimation models. Well-known examples are COCOMO, PRICE S, Estimacs, and Function point analysis. The limited and often unsuccessful use of cost models is the motivation behind this paper. The authors oppose the idea that a model is the solution to the estimation problem, but are convinced that the use of a model can contribute to the control of software development, if it is used properly. The model should be used to generate a second opinion. It will have value as a means of communication, as a checklist, and as it forces the user to collect data on the development process. Certain organizational requirements should be fulfilled to be able to use the model properly. The proper use of the model and the organizational requirements are the main subjects of this paper.