Topic
Defect tracking
About: Defect tracking is a research topic. Over the lifetime, 124 publications have been published within this topic receiving 1128 citations.
Papers published on a yearly basis
Papers
Patent•
1 Oct 1996
TL;DR: In this article, the authors present a disk controller for a disk drive array which maintains two representations of all drive defects, a logical defect list and a physical defect list that is used to preserve known defect information on a physical disk basis.
Abstract: A disk controller for a disk drive array which maintains two representations of all drive defects. The controller maintains a logical defect list that is used to maintain the sector remapping structure when reconstructing redundancy information. The controller also maintains a physical defect list that is used to preserve known defect information on a physical disk basis. The physical defect list stores the defects even if the logical configuration of the disks changes. When the controller of the present invention determines that a block of data is bad, the controller allocates space for the respective stripe in an alternate block, recovers the data in the stripe and writes the recovered data to the newly allocated stripe. The controller then updates the remap tables in memory with the remap information. On each disk access, the controller searches the logical defect list to determine if the access involves one or more bad blocks. When a failed disk is replaced, the controller rebuilds the data from the failed drive using the remaining data and parity. The controller also uses both the logical and physical defect lists to unmap remapped sectors which were originally remapped due to defective sectors on the replaced disk drive.
111 citations
18 May 2013
TL;DR: This paper proposes the Eclipse and Mozilla Defect Tracking Dataset, a representative database of bug data, filtered to contain only genuine defects and designed to cover the whole bug-triage life cycle, used ourselves for predicting bug severity, for studying bug-fixing time and for identifying erroneously assigned components.
Abstract: The analysis of bug reports is an important subfield within the mining software repositories community. It explores the rich data available in defect tracking systems to uncover interesting and actionable information about the bug triaging process. While bug data is readily accessible from systems like Bugzilla and JIRA, a common database schema and a curated dataset could significantly enhance future research because it allows for easier replication. Consequently, in this paper we propose the Eclipse and Mozilla Defect Tracking Dataset, a representative database of bug data, filtered to contain only genuine defects (i.e., no feature requests) and designed to cover the whole bug-triage life cycle (i.e., store all intermediate actions). We have used this dataset ourselves for predicting bug severity, for studying bug-fixing time and for identifying erroneously assigned components. Sharing these data with the rest of the community will allow for reproducibility, validation and comparison of the results obtained in bug-report analyses and experiments.
79 citations
Patent•
21 Nov 2005TL;DR: In this article, an automation infrastructure which automatically analyzes software faults and/or bugs related to a product defect is provided, which can automatically analyze and detect symptoms in the forms of crash dump, memory leak, corruption and test issues.
Abstract: An automation infrastructure which automatically analyzes software faults and/or bugs related to a product defect is provided. More particularly, the system can automatically analyze and detect symptoms in the forms of crash dump, memory leak, corruption and test issues etc. In accordance therewith, aspects can automatically search for and locate existing defect reports, if such existing reports are available. Moreover, aspects can automatically report new defects in a defect tracking database or other tracking mechanism.
76 citations
TL;DR: The author offers nine best practices to improve the management of large software systems: risk management, agreement on interfaces, formal inspections, metrics-based scheduling and management, and binary quality gates at inch/pebble level.
Abstract: As our industry undertakes ever larger development projects, the number of defects occurring in delivered software increases exponentially. Drawing on his experiences in the defense industry, the author offers nine best practices to improve the management of large software systems: (1) risk management; (2) agreement on interfaces; (3) formal inspections; (4) metrics-based scheduling and management; (5) binary quality gates at inch/pebble level; (6) program-wide visibility of progress vs. plan; (7) defect tracking against quality targets; (8) configuration management; and (9) people-aware management accountability.
68 citations
TL;DR: A framework for tracking multiple sewer defects in CCTV videos based on defect detection and metric learning is proposed, which can assist with counting unique defects in inspection videos.
61 citations
Related Topics (5)
Performance Metrics
| Year | Papers |
|---|---|
| 2021 | 4 |
| 2020 | 4 |
| 2019 | 5 |
| 2018 | 5 |
| 2017 | 8 |
| 2016 | 6 |