This is the fourth in a series of articles that provide insight into how various software tools support the collection, analysis, and reporting of metrics. Accurately tracking software defects and changes is a challenge for software managers.
Most organizations track software defects and changes via a defect or change report.
The name and information included on the report varies from organization to organization depending on the organization's software process and project type. For example, one organization may use two reports, one to record defects or problems and another to track changes resulting from defects and enhancements, while others will use one report that has a unique identifier to distinguish the report type. Common names for these reports include Software Problem Report, Trouble Report, Error Report, Bug Report, Software Discrepancy Report, Defect Report, and Software Change Request. Because these reports contain inconsistent information, using the data to collect defect metrics may lead to confusion and incorrect interpretation of the data. The report provides guidance to implement a defect measurement system and defines a set of attributes and attribute values commonly recorded in a defect report.