San Diego, California August 14-19, 2016

Defect Prevention



The term defect stands for error or fault. Defect prevention is the most important aspect of software quality assurance. Defect in software application can lead to messed up situation not in one, but all the phases of software development. Occurrence of defects can sometimes be sole contributor towards a significant increase in product cost because of correction and rework time. In fact, due to rework time the stipulated time of release gets pushed back.

Defect prevention is a strategy that must be opted by the IT organization to ensure that software meets all requirements and the target customers remain happy. In fact, the earlier a defect is identified the easier, cheaper and time-saving affair becomes the rectification procedure. The end result in prevention or the early detection is a software application with zero or most minimal defects.

Defect prevention is a structured problem-solving procedure that identifies, analyzes and prevents the further occurrence of defects. It is a framework as well as on-going process of accumulating the defective data, conducting analysis on the root causes of defect, determining and implementing the right actions and lastly sharing the experience gained from the procedure to avoid occurring future defects.

Defect prevention is not an individual work but a consistent team effort. Successful defect prevention includes a series of important activities staring with software requirement analysis, self-review and peer review, logging and documenting defects, analyzing root cause and ending with implementing procedures in the path of software development.

Compared to errors in source code, errors in software requirement as well as in design documents tend to be more. Defects during the requirement and design stage are severe and difficult to remove. Thus, a proper analyzing o requirement is must.

Self-review is extremely effective to detect the defects that might be later uncovered by testing team or the customer himself. Peer-review is review of the work but only with a fresh pair of eyes possessing sound knowledge of the concerned area.

Thorough defect logging as well as documentation paves a way to manage the defects and reduce it successfully resulting minimizing cost and completing the project right on time. After the defects are documented, the next important activity is analyzing it to understand the root cause.

Among the various defect prevention activities implementing all the procedures to reduce or prevent the defect is the toughest. The project manager can deploy a plan of action as a way to modification to improve the work and prevent defects from occurring.

Contact Us
© 2016 International Institute for Software Testing