A Survey on Effective Defect Prevention - 3T Approach <s> Defect Prevention Flow <s> Orthogonal defect classification (ODC), a concept that enables in-process feedback to software developers by extracting signatures on the development process from defects, is described. The ideas are evolved from an earlier finding that demonstrates the use of semantic information from defects to extract cause-effect relationships in the development process. This finding is leveraged to develop a systematic framework for building measurement and analysis methods. The authors define ODC and discuss the necessary and sufficient conditions required to provide feedback to a developer; illustrate the use of the defect type distribution to measure the progress of a product through a process; illustrate the use of the defect trigger distribution to evaluate the effectiveness and eventually the completeness of verification processes such as inspection or testing; provides sample results from pilot projects using ODC; and open the doors to a wide variety of analysis techniques for providing effective and fast feedback based on the concepts of ODC. > <s> BIB001 </s> A Survey on Effective Defect Prevention - 3T Approach <s> Defect Prevention Flow <s> By employing the Orthogonal Defect Classification scheme, the authors are able to support management with a firm handle on technical decision making. Through the extensive capture and analysis of defect semantics, one can obtain information on project management, test effectiveness, reliability, quality, and customer usage. The article describes three real-life case studies, and demonstrates the applicability of their techniques,. <s> BIB002 </s> A Survey on Effective Defect Prevention - 3T Approach <s> Defect Prevention Flow <s> In today's business where speed is of essence, an iterative development approach that allows the functionality to be delivered in parts has become a necessity and an effective way to manage risks. Iterative development allows feedback from an iteration to influence decisions in future iterations, thereby making software development more responsive to changing user and business needs. In this paper we discuss the role of defect analysis as a feedback mechanism to improve the quality and productivity in an iteratively developed software project. We discuss how analysis of defects found in one iteration can provide feedback for defect prevention in later iterations, leading to quality and productivity improvement. We give an example of its use and benefits on a commercial project <s> BIB003 </s> A Survey on Effective Defect Prevention - 3T Approach <s> Defect Prevention Flow <s> Most large software products have elaborate quality control processes involving many tasks performed by different groups using a variety of techniques. The defects found are generally recorded in a database which is used for tracking and prioritizing defects. However, this defect data also provides a wealth of information which can be analyzed for improving the process. In this paper, we describe the when-who-how approach for analyzing defect data to gain a better understanding of the quality control process and identify improvement opportunities. At the component level, the analysis provides the capability to assess strength of dependency between components, and new ways to study correlation between early and late defects. We also discuss the experience of applying this approach to defect data from an earlier version of Windows, and the improvement opportunities it revealed. <s> BIB004 </s> A Survey on Effective Defect Prevention - 3T Approach <s> Defect Prevention Flow <s> This paper describes a test application development tool designed with a high degree of defect prevention and detection built-in. While this tool is specific to a particular tester, the PT3800, the approach that it uses may be employed for other ATE. The PT3800 tester is the successor of a more than 20 year-old tester, the PT3300. The development of the PT3800 provided an opportunity to improve the test application development experience. The result was the creation of a test application development tool known as the PT3800 AM creation, revision and archiving tool, or PACRAT (AM refers to automated media, specifically test application source code). This paper details the built-in defect prevention and detection techniques employed by PACRAT. <s> BIB005 </s> A Survey on Effective Defect Prevention - 3T Approach <s> Defect Prevention Flow <s> Default causal analysis (DCA) or defect prevention is required by higher-maturity-level software development processes such as the Brazilian Software Process Improvement Reference Model and Capability Maturity Model Integration. The authors ask and answer questions about implementing it in lower-maturity organizations. In the related web extra entitled “Evidence-Based Guidelines on Defect Causal Analysis,” authors Marcos Kalinowski, David N. Card, and Guilherme H. Travassos discuss the basics of research protocol. <s> BIB006
Defect prevention is a quality assurance method for improving the quality of the software product which makes it one of the most important activities in any software project  . Defect Prevention is identified as a level 5 Key Process Area (KPA) in the Capability Maturity Model (CMM) by the Software Engineering Institute, which involves analysing defects and take action to prevent the recurrence of similar type of defects in the future [49] . Analysis of defects at early stages reduces time, cost and resources and in the end enhances the overall productivity. From the logical viewpoint, the flow of Defect Prevention can be elaborated as shown in Fig The various steps of DP flow are elaborated below:  Data from past projects, UAT reports, meetings and inspections are taken, and defects are identified.  All the defects should be logged through the Defect logging system regularly and a considerable amount of information is recorded to facilitate tracking or resolution BIB004 .  Defects are classified using some good classification scheme like Orthogonal Defect Classification (ODC). ODC attributes extracted from the defects provide an enormous amount of information from individual defect BIB001 and defect type distribution i.e. defect signature would be generated. If adequate information is collected on each defect found and fixed, one can easily exploit ODC-based analysis in a very short time BIB002 .  With the use of ODC, it is possible to arrive at patterns and do Root Cause Analysis (RCA) on them. RCA plays an important role in finding the root cause of the problem and initiate action or corrective measures to eliminate the source of defect BIB006 .  Apply the learning"s of the projects as precautionary ideas in similar projects  . Through the study of various papers, it has been observed that ODC in conjunction with RCA is quite advantageous, ODC can alter the economics and viability of root cause analysis by reducing the time it takes to perform the work and allow for greater coverage of the defect space  . RCA is a staple diet for the improvement of software development process and ODC helps reduce the cost of RCA while increasing its coverage  . Defect Prevention is one ignored part in some of the projects. In actual practice, DP teams should be identified, and a kick-off meeting should be held in starting to raise awareness and identify solutions, training on DP and causal analysis should be given BIB003 . DP teams should meet often to identify the problems and find the root cause of the problems. The aim is to improve software quality by using readily available data to decrease defects injected and increase defects detected which can be done by applying ODC to DP process  . An automated tool like Performance and Continuous Re-Commissioning Analysis Tool (PACRAT) is created for implementation of DP and defect detection activities BIB005 .