Xref: utzoo comp.software-eng:3951 comp.realtime:754
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!bbn.com!orc!inews!iwarp.intel.com!psueea!eecs!warren
From: warren@eecs.cs.pdx.edu (Warren Harrison)
Newsgroups: comp.software-eng,comp.realtime
Subject: Re: Cost of developing embedded software reported
Keywords: cost, estimating, software engineering, embedded software, development
Message-ID: <3149@psueea.UUCP>
Date: 19 Jul 90 15:47:46 GMT
References: <12577@june.cs.washington.edu>
Sender: news@psueea.UUCP
Reply-To: warren@eecs.UUCP (Warren Harrison)
Organization: Portland State University, Portland, OR
Lines: 24

In article <12577@june.cs.washington.edu> jon@cs.washington.edu (Jon Jacky) writes:
>Here are excerpts from R&D magazine (a controlled-circulation trade magazine),
>July 1990, p. 68, in an article "Five Steps to Successful Software Development"
>by Roger Woodward of Woodward Design Associates, San Francisco:

... a description of how they obtained their data

>Thus a project that must fit in 64K should cost, start to finish, about 
>$180,000.
>

Does this mean that a project which needs to fit in 16K should cost $44,000?
I guess the best way to reduce the cost of that 64K system is to get rid of
some ROM :-) It seems it would make more sense to include the expected
functionality in the estimation procedure - (IMHO)

Warren



==========================================================================
Warren Harrison                                          warren@cs.pdx.edu
Department of Computer Science                                503/725-3108
Portland State University