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 autolearn=ham autolearn_force=no version=3.4.5-pre1 Date: 15 Aug 91 18:11:44 GMT From: ads.com!saturn!bhanafee@decwrl.dec.com (Brian Hanafee) Subject: Re: LOC estimates for Ada Command and Control projects Message-ID: List-Id: In article <1234@tfsg.UUCP> dennis@tfsg.UUCP (Dennis Gibbs) writes: >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. >[description of project deleted] >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. >[...] >Dennis Gibbs >...uunet!tfsg!dennis Ask yourself if one developer working full time for 12-15 months could complete the project: developed, debugged, tested, and documented. How about two developers for 6-8 months? If you can't answer those questions, or if you think the answer might be no, then your estimate is going to get you in trouble. Also ask yourself what "develop" means. Is the design completed already? -- Brian Hanafee Advanced Decision Systems bhanafee@ads.com 1500 Plymouth Street (415) 960-7300 Mountain View, CA 94043-1230