Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!samsung!usc!wuarchive!udel!rochester!rit!ritcv!mjl
From: mjl%ritcv@cs.rit.edu
Newsgroups: comp.software-eng
Subject: Re: Predicting Software Ship Dates
Message-ID: <1420@cs.rit.edu>
Date: 1 Dec 89 20:09:01 GMT
References: <15030@joshua.athertn.Atherton.COM>
Sender: news@cs.rit.edu
Reply-To: mjl%ritcv@cs.rit.edu (Michael Lutz)
Organization: Rochester Institute of Technology, Rochester, NY
Lines: 18

In article <15030@joshua.athertn.Atherton.COM>, joshua@athertn.Atherton.COM (Flame Bait) writes:
> I have a simple question, I'm looking for a simple answer :-)
> 
> Given any information you want, predict when a software project will have
> fewer than N bugs, and make the prediction after "new" coding has stopped,
> but while debugging and testing is still going on.

Sounds like you should be looking at "Software Reliability: Measurement,
Prediction, and Application" by John Musa, et. al. (McGraw-Hill, 1987).
They address these problems and several others from a statistical profile
viewpoint.  The underlying math is heavy duty indeed, but it can be
skipped initially, as they provide some basic parameters you can fit
to your own project.  I heartily recommend it.

Mike Lutz
Mike Lutz	Rochester Institute of Technology, Rochester NY
UUCP:		{rutgers,cornell}!rochester!rit!mjl
INTERNET:	mjlics@ultb.isc.rit.edu


Brought to you by Super Global Mega Corp .com