Defect management Process

Introduction   Defect can be defined as an unexpected behavior of the software. No software exists without a defect or bug. The elimination of bugs from the software depends upon the efficiency of testing done on the software. A defect is basically the difference between the expected result and the actual result.

A defect is a specific concern about the quality of an Application under Test (AUT).

The cost of finding and correcting defects represents one of the most expensive software development activities. Defect should be finding as early as possible in the software to reduce the cost of fixing of the bugs. If a defect found later phase in the software, the cost of the fixing that bug becomes high.

It is fact that it will not be possible to eliminate all defects from the software. While defects may be inevitable, we can minimize their number and impact on our projects. To do this, project management team needs to implement a defect management process (DMP) that focuses on preventing defects, finding defects as early as possible in the process, and minimizing the impact of defects.

Defect Management Process: The defect management process is based on the following general principles:

There are following parts to manage the process:

Defect Prevention, Baseline delivery, Defect Discovery, Defect Resolution and Process Improvement.

Defect management process can be understood by diagrammatically: