From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!convex!linac!att!cbnewsl!arny
From: arny@cbnewsl.att.com (arny.b.engelson)
Newsgroups: comp.lang.ada
Subject: How large are your Ada CSUs?
Keywords: CSU 2167A
Message-ID: <1991Jan31.215838.4711@cbnewsl.att.com>
Date: 31 Jan 91 21:58:38 GMT
Distribution: na
Organization: AT&T Bell Laboratories
List-Id: <comp.lang.ada>


I have heard a lot of discussion, and read several articles, on mapping
an Ada design into DoD-STD-2167A terminology.  What I'd really like to
see is some actual data from people on programs that are at least past
the detailed design phase, and whose Ada CSCI/CSC/CSU structure has been
accepted by the customer.  If you have any real data, PLEASE respond to
the following questions (I will summarize to the net if I get enough data).
(note: I'm not doing scientific research here, approximations are fine).

How many lines of code (LOC) were your CSUs (average, maximum)?

How did you measure lines of code?

Did your customer have a fixed maximum number of LOC per CSU?

What Ada program units are (or could be) CSUs?

How many CSUs per CSC are there (average, maximum)?

How large (in terms of LOC) was your effort?

What program, and for what customer?

Thank you.
  -- Arny Engelson   att!wayback!arny (arny@wayback.att.com)