Saturday, 23 January 2016

MT - 61 - Defect Density !

Defects are considered to be the unexpected behaviour of the system with respect to the client requirements. The purpose of testing is to bring the confidence in the built system by mapping them with requirements. During testing we log lot of defects, some of them gets cancelled and some of them gets approved. From the management's perspective we need to have a track over the defects , its density and occurrence.

Defect Density is defined as the number of confirmed defects in software/module during a specific period of testing\development divided by the size of the software/module. The count may be used to ensure the correct time for release.

defect density image

Here, size may be the number of lines of code or may be measured using FP(Funtion Points).

Number of defects represents the count of confirmed defects.

The defect density is calculated over a period based on the organisation standards.


Defect density can be affected by : 

- The complexity of code
- Less time to test more code
- Unskilled testers


Advantages 

-  To compare the relative no of defects in various components so that risky components may be identified

-For comparing software/products so that quality of each software/product can be quantified and resources focused towards those with low quality.

-It helps measure the testing effectiveness

-It can be helpful in estimating the testing and rework due to bugs

-It can estimate the remaining defects in the software

-Before the release we can determine whether our testing is sufficient

No comments:

Post a Comment