Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!emory!mephisto!mcnc!duke!romeo!crm
From: crm@romeo.cs.duke.edu (Charlie Martin)
Newsgroups: comp.software-eng
Subject: Re: Predicting Software Ship Dates
Message-ID: <16273@duke.cs.duke.edu>
Date: 30 Nov 89 21:00:02 GMT
References: <15030@joshua.athertn.Atherton.COM>
Sender: news@duke.cs.duke.edu
Reply-To: crm@romeo.UUCP (Charlie Martin)
Organization: Duke University CS Dept.; Durham, NC
Lines: 11

I don't have the exact reference right at hand, but the IBM Software
Clean Room work on statistical testing might offer an attack.  You would
basically develop an empirical for the number of remaining bugs given
the time to find a bug, then use that.

On the other hand, for a massive project you can deal with this, both in
terms of the workload testing jig and the statistical munging of the
data; on a one-person project, it may not be a valid model or worth the
trouble.  Have you considered playing Michaelangelo and saying "whem I'm
done!"
Charlie Martin (crm@cs.duke.edu,mcnc!duke!crm) 


Brought to you by Super Global Mega Corp .com