TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Classic View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Topic: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Sender: "Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
From: Ed Falis <[log in to unmask]>
Date: Wed, 12 Feb 1997 09:38:46 -0500
X-To: "Mike F. Brenner" <[log in to unmask]>
Reply-To: Ed Falis <[log in to unmask]>
Parts/Attachments: text/plain (28 lines)
Mike Brenner writes:

> There are two main reasons people on the web claim to measure lines of
code.
> The first is to approximate the volume of work involved in developing
> software. The second is to approximate the volume of work involved in
> maintaining software.
>

There's a third reason - sizing resource requirements for embedded
applications.  I think it's reasonable in an Ada context state the
following limitations: "excluding generic instantiations and calls to
runtime routines" as a way of making the estimate of code expansion more
meaningful.  One then measures expansion for some set of code sequences
that approximate the application code, estimates runtime system
contribution under various conditions, and comes out with something
semi-meaningful, while remaining aware that the standard deviation for the
first measurement can be equal to the mean.  The results can still be
useful, taken with a grain of salt or two.

- Ed


Ed Falis
Aonix   (617) 221-7341

Question "Reality"

ATOM RSS1 RSS2