NetNews Usenet Archive 1992 #27/NN_1992_27.iso/spool/comp/software/4452

Text File | 1992-11-21 | 1.6 KB | 37 lines

Newsgroups: comp.software-eng
Path: sparky!uunet!usc!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!csn!raven!rcd
From: [e-mail] (Dick Dunn)
Subject: Re: Estimating Large S/W Development Efforts
Message-ID: <[e-mail]>
Organization: eklektix - Boulder, Colorado
References: <[e-mail]> <[e-mail]> <[e-mail]>
Date: Sun, 22 Nov 1992 01:10:19 GMT
Lines: 26

[e-mail] (James S Murphy) writes:
>[e-mail] ( Marty Leisner) writes:
>|> If you considering so much code, you should take a good, hard look at
>|> what your doing...[size figures for a couple large-ish programs]

>  I'm not sure of your point.  If you are saying that anything larger than
>about 150K to 200K LOC is excessive, I must disagree...

Marty didn't say that 150-200k LOC was excessive; he said that if you're
looking at so much code, you ought to consider whether you really need so
much.

The anticipation that a project will be very large is often self-fulfilling.

>  Applications on the order of >1MLOC are quite common,...
Empirical evidence says this is all too true, but...
>...as well as being
>appropriately sized for the tasks at hand.
This is at best conjecture.  There *are* tasks that require >1MLOC, but
nowhere near as many as the number of tasks which have been afflicted
with >1MLOC "solutions".  One need not search too far to find large appli-
cations which contain an order of magnitude more code than was needed to
do the job.
--
Dick Dunn    [e-mail]   -or-   raven!rcd    Boulder, Colorado
    ...Simpler is better.