A Survey on Effective Defect Prevention - 3T Approach <s> Pillars of Defect Prevention -T3 <s> Defect measurement plays a crucial role when assessing quality assurance processes such as inspections and testing. To systematically combine these processes in the context of an integrated quality assurance strategy, measurement must provide empirical evidence on how effective these processes are and which types of defects are detected by which quality assurance process. Typically, defect classification schemes, such as ODC or the Hewlett-Packard scheme, are used to measure defects for this purpose. However, we found it difficult to transfer existing schemes to an embedded software context, where specific document- and defect types have to be considered. This paper presents an approach to define, introduce, and validate a customized defect classification scheme that considers the specifics of an industrial environment. The core of the approach is to combine the software engineering know-how of measurement experts and the domain know-how of developers. In addition to the approach, we present the results and experiences of using the approach in an industrial setting. The results indicate that our approach results in a defect classification scheme that allows classifying defects with good reliability, that allows identifying process improvement actions, and that can serve as a baseline for evaluating the impact of process improvements <s> BIB001 </s> A Survey on Effective Defect Prevention - 3T Approach <s> Pillars of Defect Prevention -T3 <s> Tracking of a reported bug for fixing is a fascinating area of research in software engineering. Many open source, free and commercial bug tracking tools have been developed and are currently under development. The industry needs criteria to select the best tool among the available set of tools that will help in fixing and tracking the progress of bug fixes. In this paper, we use BugZilla, Jira, Trac, Mantis, BugTracker.Net, Gnats and Fossil for comparative study. We present a comprehensive classification criteria to review the available tools and propose a new tool named Bug Tracking and Reliability Assessment System (BTRAS) for the bug tracking/reporting and reliability assessment. BTRAS helps in reporting the bug, assigning the bug to the developer for fixing, monitoring the progress of bug fixing by various graphical/charting facility and status updates, providing reliability bug prediction and bug complexity measurements, and distributing fixes to users/developers. <s> BIB002
Based on the learning"s from a set of papers, three T"s have been identified which are three important pillars for the improvement of the Defect Prevention approach as shown in Training is identified as one critical point that needs attention. A proper training is required to all the stakeholders so that they understand the use of proper defect tracking and technique of defect prioritization, classification and prevention. Defect Prevention is applied everywhere, but the manner of application is important. Hence adequate training should be given to everybody involved in projects like tester or developer or manager about how important Defect Prevention is, how it can help to reduce the rework when applied properly. Tracking of all the defects is important as we want everybody to get complete and consistent information about them like the origin of the defect, phase of detection, priority, defect types etc. Defect tracking provides valuable information to improve software processes and streamline the process of reporting, handling and fixing issues. They should be chosen based on user"s requirement and constraint BIB002 . There are various defect tracking system, however, more important is users must be motivated to make the correct use of defect tracking system by refilling the data after the defect is re-examined or updated. Another important point is the use of the proper defect classification technique that can be applied on the defect. There are different types of defect classification techniques like IBM"s Orthogonal Defect Classification or HP approach called Defect Origins, Types and Modes. Stefan Wagner and Huber have summarized these two classification techniques along with the comparison and current challenges in this aspect   . Defect classification helps in deciding which defect to correct firstly and which one can be ignored for later correction. There are lots of case studies which demonstrated the use of ODC for improving software quality  . The approach is to analyse defects by categorizing them and creating a distribution chart about the process However, it has also been found that general defect type classifications are difficult to use and need to be developed or modified for specific project domain and environment BIB001 . Some of the learnings of this study are also listed below: 1. Make developers, testers and managers realize the importance of Defect Prevention. 2. Use simplified but Elaborative Defect Tracking system. 3. A case study of defect detection and analysis techniques in previous projects should be given to stakeholders. 4. One good defect classification technique should be applied in projects.