• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Tim Cooke
  • paul wheaton
  • Ron McLeod
  • Jeanne Boyarsky
Sheriffs:
  • Paul Clapham
Saloon Keepers:
  • Tim Holloway
  • Roland Mueller
Bartenders:

Any tools to rate quality of codebase

 
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi,

does anybody know of any tools (or eclipse plugins) that goes thru the codebase and basically rates the quality of the code?

We have made substantial improvements to our codebase in the last 12months, but am struggling to convince management of this - so any suggestions here are appreciated!

thanks-

Jac
 
author & internet detective
Posts: 42173
937
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jac,
You could use a static analysis tool like PMD or FindBugs and show the # things flagged went down.
 
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Why do you need to convince management?
 
Jac Jones
Greenhorn
Posts: 17
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Jeanne,

thanks for the suggestion - shall look into pmd.

Ilja, the reason is to help justify the amount of refactoring we have had to do - so it would be nice to have something 'objective'.


thanks.
 
Ilja Preuss
author
Posts: 14112
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Originally posted by Jac Jones:
the reason is to help justify the amount of refactoring we have had to do - so it would be nice to have something 'objective'.



I my limited experience, management isn't very interested in code quality directly. What would probably help more are the benefits of the improved code quality, such as

"If we would have had to do X two years ago, it would have taken us weeks, but because of the improved code quality, it is now only taking hours."

or

"Implementing feature X is a breeze today. Two years ago it would have been near to impossible to implement, because the code was so much more rigid."

Having numbers for your code quality might be able to support those statements, but if my experience is typical, it's unlikely to work if standing alone.

Hope this helps...
 
author and iconoclast
Posts: 24207
46
Mac OS X Eclipse IDE Chrome
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Also note that the word "quality" has a formal definition when it comes to software, and it has nothing to do with anything mentioned so far in this thread. A manager is likely to understand "software quality" to mean "the degree to which the software meets the requirements."
 
No matter. Try again. Fail again. Fail better. This time, do it with this tiny ad:
Clean our rivers and oceans from home
https://www.kickstarter.com/projects/paulwheaton/willow-feeders
reply
    Bookmark Topic Watch Topic
  • New Topic