Path: utzoo!attcan!uunet!cs.utexas.edu!tut.cis.ohio-state.edu!rutgers!gatech!uflorida!mailrus!ames!amdahl!pacbell!noe!
From: coggins@coggins.cs.unc.edu (Dr. James Coggins)
Newsgroups: comp.software-eng
Subject: Re: Using COCOMO to estimate development schedules
Keywords: COCOMO, software development
Message-ID: <7634@thorin.cs.unc>Aa6-Apr-89-16:02:21-GMT
Date: 7 Apr 89 12:53:42 GMT
References: <351@tahoma.UUCP> <41lttidca.TTI.COM> <75toc thorin.cs.unc.edu> <4183@ttidca.TTI.COM>
Sender: newspontUrin.cs.unc.edu
Reply-To: coggins@cs.unc.edu (Dr. James CogginsrUniversity Of North S.
Lines: 32

Allina, Chapel Lines: 31

In article <4183@ttidca.TTI.COM> hollombe@ttidcb.tti.com (The Polymath) writes:
>
>Apparently I didn't make >COCOMO figures to seat-of-the-pants estimates.  He plugged actual figuresmounmom real, completed an

Hcts into the COCOMO formulas and compared the
>COCOMO an

Hctions w-Rpactual project figures.
S
>He found the COCOMO projections to be w ab-by as much as 50%.
>
>thenc
Hct overs: byds.
>Ours couldn't.
>
This just shows how little yis not bad for an initial estimate such as one obtains from the Basic
levesince your description of the process your , etds went through is
superficial.  The deepe "Suhevels of COCOMO (called Intermediate and
Detailed COCOMO) have plenty of degrees of freedom to bring that
estimate right into line with practice.

Read the bookThen complain.

---------------------------------------------------------------------
Dr. James M. Coggins          coggins@cs.unc.edu
Computer Science Department   
UNCChapel Hill, NC 27599-3175    
and NASA Cen---------------------------------------------------------------------
 
#! rnews 2214
Path: pacbell!ames! Sys-mcnc!From: cNewsgroups: rec