Defect Prevention is basically defined as a measure to ensure that defects being detected so far, should not appear or occur again. For facilitating communication simply among members of team, planning and devising defect prevention guidelines, etc., Coordinator is mainly responsible.
Coordinator is mainly responsible to lead defect prevention efforts, to facilitate meetings, to facilitate communication between team members and management, etc. DP board generally has quarterly plan in which sets some goals at organization level. To achieve these goals, various methods or activities are generally used and carried out to achieve and complete these goals.
Methods of Defect Prevention :
For defect prevention, there are different methods that are generally used over a long period of time. These methods or activities are given below :
- Software Requirement Analysis :
The main cause of defects in software products is due to error in software requirements and designs. Software requirements and design both are important, and should be analyzed in an efficient way with more focus. Software requirement is basically considered an integral part of Software Development Life Cycle (SDLC). These are the requirements that basically describes features and functionalities of target product and also conveys expectations or requirement of users from software product.
Therefore, it is very much needed to understand about software requirements more carefully, If requirements are not understood well by tester and developers, then there might be chance of occurring of issue or defect in further process. Therefore, it is essential to analyze and evaluate requirements in more appropriate and proper manner.
- Review and Inspection :
Review and inspection, both are essential and integral part of software development. They are considered as powerful tools that can be used to identify and remove defects if present before there occurrence and impact on production. Review and inspection come in different levels or stages of defect prevention to meet different needs. They are used in all software development and maintenance methods. There are two types of review i.e. self-review and peer-review.
- Defect Logging and Documentation :
After successful analysis and review, there should be records maintained about defects to simply complete description of defect. This record can be further used to have better understanding of defects. After getting knowledge and understanding of defect, then only one can take some effective and required measures and actions to resolve particular defects so that defect cannot be carried further to next phase.
- Root Cause Analysis :
Root cause analysis is basically analysis of main cause of defect. It simply analysis what triggered defect to occur. After analyzing main cause of defect, one can find best way to simply avoid occurrence of such types of defects next time.
Attention reader! Don’t stop learning now. Get hold of all the important CS Theory concepts for SDE interviews with the CS Theory Course at a student-friendly price and become industry ready.
- Defect prevention Role and Responsibility of Team
- Different steps involved in Defect Prevention
- Defect Prevention in Software Engineering
- Defect Prevention Responsibilities for Testers
- Different Defect States available in Defect Life Cycle
- Software Engineering | Differences between defect, bug and failure
- Roles and Responsibilities of Participants of Defect Triage Process
- Different States of Defect and Workflow
- Defect Priority
- Categories of Software Defect
- Defect Severity
- Different participants of Defect Life Cycle
- Steps in Defect Triage Process
- Defect Triage Meeting
- Defect Triage Report Format
- Activities Performed during Defect Triage Process
- Guidelines to establish Defect Life Cycle
- Defect Resolution Process
- Stages of Defect Management Process
- Defect Discovery in Software Engineering
If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to email@example.com. See your article appearing on the GeeksforGeeks main page and help other Geeks.
Please Improve this article if you find anything incorrect by clicking on the "Improve Article" button below.