Contemporary Trends in Defect Prevention: A Survey Report <s> Preparation, Definition of Defect Type, Defect Prevention Process and Support for Defect Prevention. <s> A well-organized defect management process is one of the success factors for implementing software projects in time and in budget. The defect management process includes defect prevention, defect discovery and resolution, defect causal analysis, and the process improvement. However, establishing an organization-wide defect management process is a complicated task. The main research question in this paper is what kind of difficulties organizations have regarding the defect management process. Our findings show that problems are related to defect resolution reports, limited project resources for fixing defects, and challenges in creating a test environment. Results are based on our observations from four case organizations. The main contribution of this study is to help organizations to identify and avoid typical problems with defect management. <s> BIB001 </s> Contemporary Trends in Defect Prevention: A Survey Report <s> Preparation, Definition of Defect Type, Defect Prevention Process and Support for Defect Prevention. <s> Advancement in fundamental engineering aspects of software development enables IT enterprises to develop a more cost effective and better quality product through aptly organized defect detection and prevention strategies. Software inspection has proved to be the most thriving and proficient technique for defect detection and prevention.The work analyzes data obtained for five different projects from progressive software company of varying software production capabilities. The defect prevention technique involves proactive, reactive and retrospective moves to uncover 70% of defects during inspections and developer unit testing. The validation testing uncovers 29% of defects. Inspection becomes imperative in creating much more ideal software in factories through enhanced methodologies of aided and unaided inspection schemes. <s> BIB002 </s> Contemporary Trends in Defect Prevention: A Survey Report <s> Preparation, Definition of Defect Type, Defect Prevention Process and Support for Defect Prevention. <s> It is well known that software production organizations spend a sizeable amount of their project budget to rectify the defects introduced into the software systems during the development process. An in depth understanding of the mechanisms that give rise to defects is an essential step towards the reduction of defects in software systems. In line with this objective, we conducted a case study of defect introduction mechanisms on three major components of an industrial enterprise resource planning software system, and observed that external factors including incomplete requirements specifications, adopting new, unfamiliar technologies, lack of requirements traceability, and the lack of proactive and explicit definition and enforcement of user interface consistency rules account for 59% of the defects. These findings suggest areas where effort should be directed. <s> BIB003
The splitting of defect types is presented using the Histogram and Pareto diagrams. The study shows that the defect prevention activities bring product quality improvement by removal of the defect density and better environment in the organization for the project stakeholders. Suma and Nair BIB002 focus on inspection technique of defect prevention and detection by carrying out inspection on five dissimilar projects of different sizes. The study reports that 70% of defects are uncovered during the inspection and developer unit testing process while 29% defects are detected during the validation phase. These statistics are helpful to improve confidence level in terms of quality of the product.  The study highlighted the utility of inspection as a solution for defect prevention and detection. Chang and Chu  propose an action based defect prevention (ADBP) for the implementation of defect prevention in the software development process. ABDP includes activities like first classifying the actions which becomes the reason for the defect introduction in the system. Dataset is collected and feature subset selection technique is applied on the dataset which filters out attributes which are not useful in the dataset. Data sampling is further applied to sample the major classes of dataset using the undersampling technique. After analysis phase, the prediction model is generated which is helpful for the defects blocking. The data set of AMS-COMFT project is presented and ABDP approach is applied in which accuracy of defect based actions are predicted. Mujtaba et al.  discuss software quality metrics and propose Defect Fixation Efficiency (DFE) technique that quantitatively measures the defect fixation process. The defect fixation is calculated by using the formula: The higher DFE percentage indicate high number of defects A 2×2 matrix is defined after calculating the DFE, to indicate quality of the software. The matrix encompasses four scenarios: High-High, High-Low, Low-High and Low-Low to reflect the relationship of DFE to the wrong defects and shows the customer satisfaction with the product's quality. A new software quality assurance metric is defined to show relationship among software quality attributes. Gerard et al.  describe that simplicity and reliability are the two main factors to prevent the failure of the application. Reliability is achieved through implementation of two strategies -one of them includes simplicity and sturdiness and the second is takes advantage of idleness. Through probability techniques, importance of individual and whole system failure is described. Ghazarian BIB003 conducted a case study on defect introduction mechanisms and highlights the importance of causal analysis. Case study is conducted on three ERP software systems and shows that external factors including incomplete requirements specifications, adopting new unfamiliar technologies, lack of requirements traceability and the lack of proactive and explicit definition and enforcement of user interface consistency causes 59% of the defects. Jantti et al. BIB001 argue that a well-organized defect management process is one of the success factors for implementing software projects in time and in budget. The defect management process activities are defect prevention, defect discovery and resolution, defect causal analysis and the process improvement. However, establishing a defect management process is not much easier. The reported problems are related to defect resolution reports, limited project resources to fix defects and challenges in creating a test environment. A summary of critical analysis of different defect prevention techniques is provided in Table I . ODC The contribution of the study is that it describes the importance of ODC in project life cycle and how it introduces the quality in product. How the improvement of processes are conducted and evaluated. The study only focuses on only one area.