ABSTRACT
A long-standing problem with measuring software quality is defining what software quality actually means. Definitions for quality can encompass subjective aesthetic quality and also precise quantitative units such as numbers of defects and their severity levels. Over the years software has tried a number of alternate definitions for quality that are not actually useful. Requirements themselves are filled with bugs or errors that comprise about 20" of the overall defects found in software applications. An important and useful metric for software quality is that of defect potentials. Defect potentials can be predicted before projects start, and of course bugs will be measured and reported as they are found. Most of the defect origins are self-explanatory. Needless to say, identifying error-prone modules (EPM) is an important aspect of software bug reporting. The possible record for duplicate defects was a word processor that had a bug in the installation procedure so customers could not install the application.
