Checklist for Software Metrics

The process metrics questions focus on the degree to which the software engineering process is quantified and measured. Typical metrics concern software quality, the amount of code developed, resources used, and such progress indicators as review coverage, test coverage, and test completion.

  1. Are software staffing profiles maintained of actual staffing versus planned staffing?

  2. Are productivity and effort measured and recorded for each phase of the project?

  3. Are profiles of software size maintained for each software configuration item?

  4. Are profiles of software complexity maintained for each software item?

  5. Are statistics on software design errors gathered?

  6. Are statistics on software code and test errors gathered?

  7. Are profiles maintained of actual versus planned software units designed, over time?

  8. Are profiles maintained of actual versus planned software units completing unit testing, over time?

  9. Are profiles maintained of actual versus planned software units integrated, over time?

  10. Are target computer memory utilization estimates and actuals tracked?

  11. Are target computer throughput utilization estimates and actuals tracked?

  12. Are design and code review coverages measured and recorded?

  13. Is test coverage measured and recorded for each module tested?

  14. Are software problem reports tracked to closure?

  15. Are the cost and effort needed to correct errors measured and recorded?

  16. Are any metrics defined and applied for measuring the quality of the software product?

  17. Are there any metrics to rate the quality of the software process?

  18. Are quality measures used to identify weak points of the product and the process and to verify quality criteria?

  19. Are measures used for initiating corrective actions, if a measurement value deteriorates or exceeds given boundaries?

  20. Are measures used for introducing product and process improvements?

  21. Are all data collected during the project recorded and evaluated?

  22. Are process and product metrics (e.g. productivity and effort) used to plan following projects?

  23. Are there any mechanisms to regularly review whether the defined metrics are still adequate and representative?

  24. Do you plan for measurement activities?


Literature:

Boehm, B.W.: Verifying and Validating Software Requirements and Design Specifications. IEEE Software, January 1984.