Appropriate Bug Value

How many bugs occured will be considerd appropriate over 1000 steps when inspecting software? Describle an approriate Bug value.

Questions by conlocnho18

Showing Answers 1 - 6 of 6 Answers

Bug Rate or Bug Value are not be Constant. Its depend full and fully on the overall quality basis. If the Quality is bad the bug rate is more. If the Quality is good and high, the bug rate is very low. The Bug Values is not calculated according to the individual steps or as much of steps. so there is no proper value for Appropriate Bug Value.

  Was this answer useful?  Yes

This is a useful metric to consider when assessing the quality of software development.  In the book "Code Complete" by Steve McConnell, there is a section that describes industry averages for errors per 1000 software lines of code (SLOC).  He claims that this industry standard is between 15 to 50 errors per 1000 SLOC.  This figure sets the baseline for McConnell's comparison with Microsoft software development, where on the average there are 10 to 20 errors per 1000 SLOC.  He attributes this improvement to a combination of coding techniques and independent testing discussed in later chapters of his book.  McConnell goes on to describe how Harlan Mills pioneered a process called 'cleanroom development' which is able to achieve rates as low as 3 defects per 1000 SLOC.  He also describes a few projects (eg. the software used for the space shuttle) acheived a level of 0 defects in 500,000 SLOC using a system of format development processes, peer reviews and statistical testing methodologies.

Of course, as software development improves, the industry standard for errors in 1000 SLOC will continue to decrease.  Also, as mentioned in a previous answer to this question, there is no actual set value.  It varies widely from company to company and even within companies, from project to project. 

  Was this answer useful?  Yes

Give your answer:

If you think the above answer is not correct, Please select a reason and add your answer below.