Establishing quality targets (e.g., defects per Function Point) and then tracking defects against those targets in order to track progress during testing activities.
Case Studies (2)
- Many papers report analyses of software defects from one project or another. Many of these papers, however, do not give quantitative data on the benefits derived from adopting defect tracking against quality targets. Some (for example, [bib516953], [bib517061], and [bib517063]) report case studies that applied this practice, but provide qualitative results or have another direction. The table summarizes two papers which do contain quantitative statements.
Tools (8)
- A plethora of automated tools, both proprietary and open source, are available for tracking problem reports. Many Configuration Management (CM) tools have integrated problem reporting systems. Some CM tools, such as CVS, do not have bug tracking capabilities but can be integrated with some existing problem reporting tools. The European Computer Manufacturers Association (ECMA) reference model [bib517065] provides one way of thinking about tool capabilities.
Desirable Capabilities for Problem Tracking Tools
Tracks problems reported by customers over telephone lines, e-mail, Web forms, etc.
Receives input from geographically dispersed locations
Allows assignment of report to responsible person
Monitors and reports status of problem reports
Provides development process management and change management authorization
Implements defined and configurable workflow
Includes statistics and metrics gathering and reporting
Archives historical records
Integrates with configuration management and test tools
Provides a Graphical User Interface front end, such as forms-based Web pages
Training Opportunities (8)
- The fact that a course is listed (or not listed) here does not constitute an evaluation or endorsement of the course by the DACS. These are simply links to currently available courses that are relevant to the subject practice.
DACS Gold Practice Initiative
