TEAM-ADA Archives

Team Ada: Ada Programming Language Advocacy

TEAM-ADA@LISTSERV.ACM.ORG

Options: Use Forum View

Use Proportional Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Sender:
"Team Ada: Ada Advocacy Issues (83 & 95)" <[log in to unmask]>
Date:
Sun, 6 Oct 2002 18:27:13 -0700
Reply-To:
Ed Colbert <[log in to unmask]>
Content-Transfer-Encoding:
7bit
Subject:
From:
Ed Colbert <[log in to unmask]>
X-cc:
Content-Type:
text/plain; charset="us-ascii"
Organization:
USC Center for Software Engineering
MIME-Version:
1.0
Parts/Attachments:
text/plain (66 lines)
Hi,

Does any one know of a tool for Ada that does code counting as described
in the following?  (FYI: CSE is USC's Center for Software Engineering.)

>>         Hi.  I'm trying to get a handle on a problem that is central
to
>> the mission of the CSE.  One of the biggest problems confronting
efforts
>> to manage software projects, is the question of how to quantify
software
>> engineering output, so that costs can be estimated and managed.
Several
>> configuration control challenges are also related to the
quantification
>> of changes across multiple generations of software modules.
>>         I've already examined the Code Counting tools preserved by
the
>> CSE (which measure the size of a single version of a file), but have
>> come to recognized that the core of the problem really focuses on the

>> changes between different versions of a file.  There will be a
natural
>> desireability to have code counting logic that is consistent between
a
>> 'first version, baseline counter' and a 'later version, delta
>> counter'.  A solution developed for a 'baseline counter' would not
>> necessarily be supportable within a delta counting scenario, because
of
>> its substantially greater complexity.  On the other hand, code
counting
>> logic that works for delta applications would be easy to extend to
the
>> much simpler, baseline applicaiton.  For this reason a delta code
>> counting methodology would be better developed first, as the template

>> for single file, code counting logic.
>>
>>         It appears that other companies might be addressing the
problem
>> I've identified.  A company called "Power Software" in England is
>> marketing a piece of software that, on the surface, appears to do
>> everything that we'd need it to do.  Unfortunately, it appears that
it's
>> only available for C and C++ source code evaluations.  Since Ada is
one
>> of our primary aerospace languages, that doesn't help us out in those
cases.
>>         However, we might be able to learn from their
>> accomplishment.  I've even considered that they might be able to make

>> contributions to the CSE, or even offer their products to CSE
>> members.  They already claim an impressive clientele, including
Cisco,
>> Citicorp, Ericsson, General Dynamics, Hewlett Packard, Hitachi, IBM,
>> Lockheed Martin, Lucent Technologies, Marconi, Nokia, Nortel,
Raytheon,
>> Sony, Tellabs, TRW, US Govt, Xerox, etc.  I notice that Boeing is
>> conspicuously missing from this list.

Please copy Rod in any response.  I don't think that he is on the
team-Ada mailing list.

Take care,
Ed

ATOM RSS1 RSS2