Stages of Defect Management Process

Defect Management Process (DMP) is basically defined as a process where identification and resolution of defect take place. Software development is not an easy process. It is very complex process so constant occurring of defects is normal. DMP usually takes place at stage of testing products. It is also not possible to remove all defects from software. We can only minimize number of defects and their impact on software development. DMP mainly focuses on preventing defects, identifying defects as soon as possible, and reducing impact of defects.

Stages of DMP :
There are different stages of DMP that takes place as given below :

  1. Defect Prevention :
    Defect elimination at early stage is one of the best ways to reduce its impact. At early stage, fixing or resolving defects required less cost, and impact can also be minimized. But at a later stage, finding defects and then fixing it requires very high cost and impact of defect can also be increased. It’s not possible to remove all defects but at least we can try to reduce its effects and cost required to fix the same. This process simply improves quality of software by removing defects at early stage and also increases productivity by simply preventing injection of defects into software product.

  2. Deliverable Baseline :
    When deliverable such product or document reaches its pre-defined milestone then deliverable is considered as baseline. Pre-defined milestone generally defines what the project or software is supposed to achieve. If there is any failure to reach or meet pre-defined milestone, it simply means that project is not proceeding towards plan and generally triggers corrective action to be taken by management. When a deliverable is baselines, further changes are controlled.



  3. Defect Discovery :
    Defect discovery at early stage is very important. Afterword’s, it might cause greater damage. A defect is only considered ‘discovered” if developers have acknowledged it to be valid one.

  4. Defect Resolution :
    Defect is being resolved and fixed by developers and then places it in the same place from where the defect was initially identified.

  5. Process Improvement :

    All defects that are identified are critical and cause some impact on system. It doesn’t mean that defects that have a low impact on system are not critical. For process improvement, each and every defect that is identified are needed to fixed. Identification and analysis of process should be done in which defect was occurred so that we can determine different ways to improve process to prevent any future occurrence of similar defects.

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.

My Personal Notes arrow_drop_up

Check out this Author's contributed articles.

If you like GeeksforGeeks and would like to contribute, you can also write an article using contribute.geeksforgeeks.org or mail your article to contribute@geeksforgeeks.org. 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.


Article Tags :

Be the First to upvote.


Please write to us at contribute@geeksforgeeks.org to report any issue with the above content.