Investigating software measures to improve product reliability

ABSTRACT

Inevitably, faults are introduced whilst software is being developed. If we can catch the faults before the system goes live we can improve the quality of the system and reduce the cost of maintaining the system. In this paper we have calculated software metrics from the testing and maintenance phases of the development of a software system. We are going to analyse this data and suggest some improvements that can be made to the software process to reduce the number of faults that are getting into the maintenance phase.

REFERENCES

• 1: Watts S. Humphrey, "Personal Software Process Overview, Practice, and Results", http://www.sei.cmu.edu/pulications/documents/95.reports/95.ar.psp.over.prac.res.html, 1995.
• 2: B. W. Boehm , R. K. McClean , D. B. Urfrig, Some experience with automated aids to the design of large-scale reliable software, ACM SIGPLAN Notices, v.10 n.6, p.105-113, June 1975
• 3: Niclas Ohlsson , Hans Alberg, Predicting Fault-Prone Software Modules in Telephone Switches, IEEE Transactions on Software Engineering, v.22 n.12, p.886-894, December 1996 [doi>10.1109/32.553637]
• 4: Shari Lawrence Pfleeger, Software engineering: theory and practice, Prentice-Hall, Inc., Upper Saddle River, NJ, 1998
• 5: Tom Gilb , Dorothy Graham , Susannah Finzi, Software Inspection, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1993
• 6: Ian Sommerville, Software Engineering, Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1989
• 7: Shari Lawrence Pfleeger, "Software Quality", Dr. Dobbs Journal, March 1998.
• 8: Norman E. Fenton, "Software Measurement Programs", Software Testing and Quality Engineering, May/June 1999.
• 9: Tim Dyes, "Tracking Severity Assessing and Classifying the Impact of Issues", Software Testing and Quality Engineering, March/April 1999.

INDEX TERMS

General Terms:
Measurement, Reliability

Keywords:
failures, faults, metrics, process improvement, quality, software