From: John Richard Moser <nigelenki@comcast.net>
To: V13 <v13@priest.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [RFC] Bug zapper? :)
Date: Tue, 10 Aug 2004 19:35:29 -0400 [thread overview]
Message-ID: <41195BC1.2030107@comcast.net> (raw)
In-Reply-To: <200408110030.37601.v13@priest.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
V13 wrote:
| On Monday 09 August 2004 23:07, John Richard Moser wrote:
|
|>What I found interesting was that it described bugs as
|>pseudo-quantitative based on the KLOC (thousands of lines of code) for a
|>code body. The basic theory boils down to 5-50 bugs per 1000 LOC,
|>approaching 5 for QA audited code. Thus, 10000 LOC executable, 50 bugs.
|
|
| I believe that you should not believe such things. They are just
statistics
| and nothing more.
|
Statistics are as a whole, not as a part. This makes statistics a
powerful art.
| If you have a 1000 lines project and:
|
| a) Remove all empty lines means that you remove bugs?
| b) Split it to 5 libraries and 5 utilities (10 projects) means that
you'll
| have less bugs?
| c) ....
|
| I don't take generalizations like this seriously and I believe that noone
| should do. It may be true that 10.000 lines of code contain 50 bugs as an
| average of all the code that has be written so far but it doesn't mean
that:
|
| a) 50 bugs require 10.000 lines
| b) 50 bugs will always exist on 10.000 lines
| c) All the projects out there have the same number of bugs/line
|
No, but it means in a sample of one hundred and twenty eight billion
lines, there will be approximately fifty bugs per 10000 lines of code.
|
|>--John
|
| <<V13>>
|
- --
All content of all messages exchanged herein are left in the
Public Domain, unless otherwise explicitly stated.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBGVvBhDd4aOud5P8RAlwKAJ0Ut0XoyibvkQ9THUT1YvcoufebdwCeJmNC
PqZqaKCTrdpA2DyZydcT9Cw=
=pAJZ
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-08-10 23:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 20:07 [RFC] Bug zapper? :) John Richard Moser
[not found] ` <200408100042.37159.vda@port.imtp.ilyichevsk.odessa.ua>
2004-08-09 23:09 ` John Richard Moser
2004-08-10 0:58 ` Bernd Eckenfels
2004-08-10 1:55 ` Tommy Reynolds
2004-08-10 2:47 ` Rik van Riel
2004-08-10 3:13 ` John Richard Moser
2004-08-10 8:35 ` Jakob Oestergaard
2004-08-10 15:19 ` John Richard Moser
2004-08-10 21:43 ` Bernd Eckenfels
2004-08-10 21:30 ` V13
2004-08-10 23:35 ` John Richard Moser [this message]
2004-08-11 4:50 ` Bernd Eckenfels
-- strict thread matches above, loose matches on Subject: below --
2004-08-10 21:13 Nick Warne
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41195BC1.2030107@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=v13@priest.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox