Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW

Re: Re: The qq{worse is better} approach (discussion) - Length of Code vs. Errors in Code

by clemburg (Curate)
on Jul 02, 2001 at 22:17 UTC ( #93263=note: print w/ replies, xml ) Need Help??

in reply to Re: The qq{worse is better} approach (discussion)
in thread The qq{worse is better} approach (discussion)

Accoring to Damian Conway there is a linear relationship between the length of a piece of code and the munber of bugs it will have and that shell script is shorter...

A better reference for this can be found in Code Complete, chapter 21, "How Program Size Affects Construction", page 523, from a study done in 1977 (Jones, T. Capers. 1977. Program Quality and Programmer Productivity. IBM Technical Report TR 02.764, January, 42-78.).

In short:

Project Size in Lines of CodeError Density in Errors per 1K lines of code
< 2K0 - 25
2K - 16K0 - 40
16K - 64K0.5 - 50
64K - 512K2 - 70
> 512K4 - 100

Page 610 (in Chapter 25, "Unit Testing") cites "15 to 50 errors per 1000 lines of code for delivered software" as "industry average experience".

Note however that this data is very old, and new methods for software construction may give better results. Also, some organizations, most notably NASA projects, have achieved much, much better error rates, mostly by introducing rigorous testing and code review schemes. Also note the enormous variance in the data above.

Christian Lemburg
Brainbench MVP for Perl

Comment on Re: Re: The qq{worse is better} approach (discussion) - Length of Code vs. Errors in Code

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://93263]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others examining the Monastery: (15)
As of 2014-09-01 08:47 GMT
Find Nodes?
    Voting Booth?

    The best computer themed movie is:

    Results (299 votes), past polls