The software industry lacks standard metric and measurement practices. Almost every software metric has multiple definitions and ambiguous counting rules. There are also key topics with no metrics at all, such as quantifying the volume or quality levels of data bases, data warehouses, and web sites. The result of metrics problems is a lack of solid empirical data on software costs, effort, schedules, quality, and other tangible matters. This report analyzes some of the key software size metrics and the underlying technical problems associated with software measurement.
9. Measures for Success, US Army
Excellent presentation produced by the US Army on lessons learned from software measurement and software process improvement initiatives.
10. Software Quality Profile, Watts Humphrey
The software community has been slow to use data to measure software quality. This paper by Watts Humphrey discusses the reasons for this problem and describes a way to use process measurements to assess product quality. The basic process measures are time, size, and defects. When these data are gathered for every engineer and for every step of the development process, a host of quality measures can be derived to evaluate software quality. Read on...