Open In App

Different steps involved in Defect Prevention

Last Updated : 08 Sep, 2020
Like Article

Defect Prevention (DP) is usually considered as a process of simply preventing defects from their re-occurrence in Software Development Life Cycle (SDLC). Here, defects are basically defined as errors that might occur in different stages of SDLC. It is one of best methods to remove defects at an early stage of testing rather than identifying it at later stage and then resolving it.

Steps involved in DP :
There are basically three steps of defect prevention process as given below :

  1. Identifying Critical Defect :
    Identification of defect is one of major part of defect prevention. During SDLC, different types of defects are encountered. Each defect has different impact on system. Some of them have severe impact i.e. largely affects system, some of them are less severe i.e. have less impact on system, and some of them have very less impact on system that can be considered as negligible. Therefore, it is very important to identify critical and more severe defects in system at soon as possible. Critical defects are very severe and have more impact on system as on their occurrence, they might stop the functioning of overall system or can cause some other problems on greater level. So, it is very much essential to identify critical defects.

  2. Estimate Expected Impact :
    Estimating expected impact of defect on cost is also important part of defect prevention. Whenever defect is encountered in system, main questions arises is what are measures that are needed to be taken to resolve it and amount required to resolve it. More critical defect is, more will be amount required to resolve it as more effort and resources will be required to resolve it. Therefore, it’s better to estimate expected impact of defect on cost if defect somehow encounters or occurs. After that, some measures should be taken to minimize their occurrence.

  3. Minimize Expected Impact :
    After identifying and estimating impact of critical defects, one should take some measures actions to minimize or eliminate defects permanently before its occurrence. Minimizing expected impact is also important part of defect prevention. If one could not eliminate defect, then he/she should try to reduce possibility of its occurrence and its impact.

Advantages of DP :

  • Number of defects in a system is reduced or minimized by taking some measures required.
  • Checklist that is being developed for review is improved.
  • Amount of work required to fix defect is reduced as number of defects is minimized.
  • Overall cost of production is reduced as cost required to resolve defect is minimized by taking some measures to prevent defect from re-occurrence.
  • Helps in making software defect-free as much as possible.
  • Increase overall quality of software products.
  • Improves software process by backing up testing process and minimizing cost required of resolving errors.

Similar Reads

Different Defect States available in Defect Life Cycle
Defect life cycle, also known as Bug life cycle, is a life cycle of various stages through which a defect or bug simply passes or went right from the moment it is identified by software testers to point till when tester declares that particular defect has been resolved completely and it would never reproduce again. Different Defect States : Defect
3 min read
Defect Prevention Responsibilities for Testers
Defect prevention is a very crucial but important step in Software Development Life Cycle (SDLC). Defects generally cause software to fail to meet requirements and decrease software quality. It also involves different structured problem-solving methodologies simply to identify, analyze, and prevent occurrence of defects. DP basically involves follo
2 min read
Defect Prevention Methods and Techniques
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 effo
4 min read
Defect Prevention in Software Engineering
Software quality is one of the most important and essential factors from the last few years. This is due to forces from several sectors of the computer industry. Companies and organizations face many problems that have increased difficulty in obtaining and achieving rapid and successful development of software systems. The main challenge in any sof
3 min read
Defect prevention Role and Responsibility of Team
Defect is a flaw that can cause a very harmful situation in different phases or stages of the Software Development Life Cycle (SDLC). Defect Prevention (DP) is basically a process of simply identifying defects, and their root causes, and taking appropriate measures to prevent them from re-occurrence in further processes and the future. It also ensu
2 min read
Steps in Defect Triage Process
Triage is usually a medical term whose meaning is trial or trial out. Defect Triage is basically a process where all the issues are generally screened or evaluated and are then prioritized to ensure following things : Is the issue actual or not? All the resources are used most effectively Maintain and handle a healthier system The main aim of Defec
2 min read
Different participants of Defect Life Cycle
Defect life cycle generally varies from one organization to another and is governed and controlled by software testing process the organization or project follows or defect tracking tool generally being used. There are different participants to defect life cycle that make process successful. These participants are given below : Defect Reporter : De
3 min read
Different States of Defect and Workflow
Defect is something that cannot be neglected. In software, defect management is usually the main goal of developers. Keeping track of defects that are found throughout defect lifecycle and to manage and handle defect reports should be done to maintain performance and quality of software. Different tools are used by various organizations and compani
3 min read
Activities involved in Software Requirement Analysis
Software requirement means requirement that is needed by software to increase quality of software product. These requirements are generally a type of expectation of user from software product that is important and need to be fulfilled by software. Analysis means to examine something in an organized and specific manner to know complete details about
2 min read
Defect Priority
Prerequisite - Defect Severity A defect is the representation of a misunderstanding of specification or syntax error, where representation is mode of expression. Defect Priority is classification of a defect based on its importance or precedence to be fixed. Defects that force software system to become ineffectual are given higher priority over def
3 min read