Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!emory!ogicse!milton!yoda.eecs.wsu.edu!pcooper
From: pcooper@eecs.wsu.edu (Phil Cooper - CS495)
Newsgroups: comp.software-eng
Subject: Re: Software Cost Estimation
Message-ID: <1990Dec14.205534.22674@eecs.wsu.edu>
Date: 14 Dec 90 20:55:34 GMT
References: <5676@taylord> <1990Dec12.215401.27859@ashtate>
Reply-To: pcooper@yoda.UUCP (Phil Cooper - CS495)
Organization: Washington State University, Pullman
Lines: 20

In article <1990Dec12.215401.27859@ashtate> alanw@ashtate (Alan Weiss) writes:
>
>I would STRONGLY suggest you look into Function Point Analysis.
>When tied into your already previously done :-)  Quality Function
>Deployment Analysis (House of Quality), F(x) Point Analysis is MUCH
>more predictive, IMHO.  The problem is two-fold in adaptation:
>
>	1.  It is a LOT of up-front work, and requires very
>	    detailed Functional and Design specifications.
>	2.  Political:  it requires a LOT of up-front work :-)
>	    In short, you must have management and staff buy-in
>	    that this is worthwhile.  The Urge to Code always
>	    comes ....
>
      Ever try to do a FP analysis on the "hello, world" program?  You might
be surprised to find out that it will take about 250 LOC (in 'C') to do.
At least according to the FP analysis conversion specs (from FP's to LOC).
      I suppose it MUST be more accurate for larger projects though.

      Phil Cooper