From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.5-pre1 (2020-06-20) on ip-172-31-74-118.ec2.internal X-Spam-Level: X-Spam-Status: No, score=0.0 required=3.0 tests=BAYES_40,MSGID_SHORT autolearn=no autolearn_force=no version=3.4.5-pre1 Date: 15 Aug 91 14:26:23 GMT From: tfsg!dennis@uunet.uu.net (Dennis Gibbs) Subject: LOC estimates for Ada Command and Control projects Message-ID: <1234@tfsg.UUCP> List-Id: <> We are trying to produce coding estimates for our project and we would like to solicit input to get an estimate for the number of lines of code (LOC) per day per developer. Our definition of LOC per day is code that is developed, debugged, tested, and documented. The project in question is a small Command and Control project with an estimated total code size of 50,000 lines. Our system is event driven with heavy Man-Machine Interfaces (MMI). We are using OpenWindows for the MMI, on Sun Sparcstation 2's. For the purposes of this estimate we would like to assume our programmers have average proficiency with Ada (not Ada wizards, but not novices either). Can anyone out there involved in an Ada Command and Control project tell us what a reasonable figure would be for LOC per day would be? Of course we realize that these figures are not always meaningful. I remember another net contributor comparing LOC/per day to the number pounds of airplane Boeing builds in a day, which, of course, is not very meaningful. Nevertheless, we still need some examples from some real-world Command and Control Projects to help with our estimates. Just to throw out a figure, our current estimate is around 20-25 LOC per day on average, but other examples would help us determine if this is a good or bad estimate. Can anyone help us? This is an urgent need, so if you think you can help please do! Thanks, Dennis Gibbs TRW Systems Integration Group AWHQ Project Office Chantilly, VA (703) 802-1961 -- -------------- Dennis Gibbs ...uunet!tfsg!dennis