Win a copy of The Journey To Enterprise Agility this week in the Agile and Other Processes forum! And see the welcome thread for 20% off.
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Jeanne Boyarsky
  • Liutauras Vilda
  • Campbell Ritchie
  • Tim Cooke
  • Bear Bibeault
Sheriffs:
  • Paul Clapham
  • Junilu Lacar
  • Knute Snortum
Saloon Keepers:
  • Ron McLeod
  • Ganesh Patekar
  • Tim Moores
  • Pete Letkeman
  • Stephan van Hulst
Bartenders:
  • Carey Brown
  • Tim Holloway
  • Joe Ess

Analyzing Java source code  RSS feed

 
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi All,
I am looking for a tool that analyzes Java/C++ source code to identify design and other issues associated with the code. The tool should be able to identify the reusability ,extensibility of the source code with good report generation features.
I did some lookup on the internet and found some tools like JDepend, Lexient Surveyor.
If any of you came across tools like this and have any suggestions, it would be appreciated
Thanks in advance,
Param
 
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
See JTest too.
 
Param Yanamandra
Ranch Hand
Posts: 33
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks Stan,
I checked out this tool and found it very useful. Do you know of any other tools.
 
Stan James
(instanceof Sidekick)
Ranch Hand
Posts: 8791
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I did a paper for grad school and just googled for "java static source code analysis" and found a bunch of things. One of the trade journals just had an article about how little value these tools and and a nice rebuttal from a vendor. I considered JTest and one of the others seriously for enforcement of team standards and found most of what they point out is pretty trivial or even counter productive - like too many required comments. JTest is interesting in that it points out things that are often invitations to bugs and suggests corrections. That might be worth while.
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!