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=1.9 required=5.0 tests=BAYES_50,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!tut.cis.ohio-state.edu!rutgers!mcnc!uvaarpa!vger.nsu.edu!g_harrison
From: g_harrison@vger.nsu.edu (George C. Harrison, Norfolk State University)
Newsgroups: comp.lang.ada
Subject: Re: LOC discussion
Message-ID: <794.27f4de7d@vger.nsu.edu>
Date: 30 Mar 91 22:52:45 GMT
References: <399@wrdis01.af.mil>
Distribution: usa
List-Id: <comp.lang.ada>

In article <399@wrdis01.af.mil>, 
cfranz@wrdis01.af.mil (Claus Franzkowiak) writes:
> In article <"910326054349.71660.412.CHE55-1"@CompuServe.COM>, 
71660.412@CompuServe.COM (Eric C Aker) writes:
>> When I was working for a major airplane company some years ago all of
etc.
>>The problem is measuring the progress of an intellectual product.  LOC is often
>>used in management metrics; they, after all, have to be concerned about the
>>bottom line.  
> 
etc.
>>So, the question remains (and I'd like to have some answers for my Software
>>Engineering class)....  What is a good measure of programmer productivity?
> 
>>(The only one I can think of is the amount of coffee/Mountain Dew/JOLT consumed
>>per hour.)
> 
>> -- George C. Harrison                              -----------------------
> I like this discussion.  But first of all, a manager should be interested in 
> how many LOC are working.  A "finished" program with 10K of LOC and 50% of 
> rework does not make the programmer more productive, but they should be
> subtracted from the 10k LOC.   

The keyword is "should."  What IS good management practice in this situation? 
Maybe this ought to be in comp.softwareengineering... whatever, but after all
this is what Ada is all about. 

 > Here are some of them:  1. People Factors (years of experience, language
etc.
 > There are a lot more factors.  

Sounds like COCOMO.  I agree, these are important factors, but how does
the management of programmers on a day-to-day basis reflect these things? 

> Is anyone interested in quality programming?
> Quality programming as described by M. Fagan will reduce the amount of rework
> and naturally increases productivity. 
> 
> claus franzkowiak

Perhaps we are still in the bind of not really thinking that software
production is still an intellectual process.

George....
-- George C. Harrison                              -----------------------
----- Professor of Computer Science                -----------------------
----- Norfolk State University                     -----------------------
----- 2401 Corprew Avenue, Norfolk, Virginia 23504 -----------------------
----- INTERNET:  g_harrison@vger.nsu.edu ---------------------------------