[ajug-members] Java Software Metrics
tmccune at crosslogic.com
Wed Jun 15 16:40:44 EDT 2005
Thanks Joe. I was actually trying to avoid the shameless plug. The original question was framed in a way that sounded like "how do I measure our output" so our ESLOC scanner seemed like a fit.
You are exactly right, the point of the tool is more about reuse than volume of code. Before we can gather meaningful data on reuse (and the effective use of OO) we have to know what has been produced, that was the genesis of the tool. David Pitt is all about good OO reuse strategy. I'm glad someone read that article.
From: ajug-members-bounces at ajug.org [mailto:ajug-members-bounces at ajug.org]On Behalf Of Joe Sam Shirah
Sent: Wednesday, June 15, 2005 4:30 PM
To: General AJUG membership forum (100-200 messages/month)
Subject: Re: [ajug-members] Java Software Metrics
I agree with Brian. To be short and maybe sweet, percentage of
individual and total function points completed may be the most honest
measure of progress to a client. "Completed" means the whole ball of wax -
readiness for production including testing, documentation and so on.
To be longer:
Unfortunately for us developers ( and often end users ), managers want
to measure what they *can* measure. That's unfortunate because true
productivity is often determined by quality, which can't be measured until
well into the project's production lifetime: Does it work? Does it break?
How much maintenance? How many rewrites? Is it flexible? Is it reusable?
How about "Is it a ton of ugly ( in the sense of efficient, understandable,
etc. ) code that may have to be refactored and cleaned up to be *smaller*
and more efficient?" And on.
We often see "shameless plug" on mailing lists, but I think Tony would
have been proper to mention that his colleague David Pitt has an article in
the July, 2005 Dr. Dobb's Journal entitled "Measuring Java Reuse,
Productivity and ROI". I don't agree with all of his points, but IMO it
becomes clear that: The tool is probably a pretty good one when used in a
proper context; The results are probably useful only over several projects
and a fairly long time period with similar projects; One measure of
productivity ( and a primary one for the article ) is more reuse and *fewer*
effective source lines of code ESLOC.
Joe Sam Shirah - http://www.conceptgo.com
conceptGO - Consulting/Development/Outsourcing
Java Filter Forum: http://www.ibm.com/developerworks/java/
Just the JDBC FAQs: http://www.jguru.com/faq/JDBC
Going International? http://www.jguru.com/faq/I18N
Que Java400? http://www.jguru.com/faq/Java400
----- Original Message -----
From: "Brian Lee" <brian_a_lee at hotmail.com>
To: <ajug-members at ajug.org>
Sent: Wednesday, June 15, 2005 12:58 PM
Subject: RE: [ajug-members] Java Software Metrics
> Do people still believe that number of lines of code mean anything?
> >From: "Tony McCune" <tmccune at crosslogic.com>
> >To: "General AJUG membership forum (100-200
> >messages/month)"<ajug-members at ajug.org>
> >Subject: RE: [ajug-members] Java Software Metrics
> >Date: Wed, 15 Jun 2005 12:05:42 -0400
> >We have a free utility we call ESLOC (Effective Source Lines of Code)
> >scanner. You can download it off our website at:
> >This provides not only a 'super' javadoc but also provides you with reuse
> >statistics and source code lines per hour (productivity) data.
> >Hope that helps.
> >Tony McCune
> >Director of Software Solutions
> >CrossLogic Inc.
> >Mobile 770-335-3241
> >Crosslogic - Crossing the gap between business and technology
> >-----Original Message-----
> >From: ajug-members-bounces at ajug.org
> >[mailto:ajug-members-bounces at ajug.org]On Behalf Of Tom Apulach
> >Sent: Wednesday, June 15, 2005 11:53 AM
> >To: ajug-members at ajug.org
> >Subject: [ajug-members] Java Software Metrics
> >I'm looking for a java-based program to calculate
> >basic statistics on java code at the class and package
> >levels. I'd like to use something that is open
> >source if possible. I want to be able to quantify the
> >progress of the project for a client. I understand
> >lines of code and such isn't a perfect measure but
> >it's better than "oh yes , we are making progress".
> >Any recommendations?
ajug-members mailing list
ajug-members at ajug.org
More information about the ajug-members