Open Source Java Source Code Analysis Tools for BSD

The Eclipse Checkstyle plug-in integrates the Checkstyle Java code auditor into the Eclipse IDE. The plug-in provides real-time feedback to the user about violations of rules that check for coding style and possible error prone code constructs.

UCDetector (Unnecessary Code Detector) is a Open Source Eclipse Plugin Tool. UCDetector finds unnecessary (dead) public Java code. It suggests to make code final, protected or private.

Provide metrics calculation and dependency analyzer plugin for the Eclipse platform. Measure metrics with avg and std deviation and detect cycles in package and type dependencies. Continuation of work from http://sourceforge.net/projects/metrics.

Another Open Source Code Analysis Tool

Kammerjäger is a debugging and testing tool that enables you to prove the correctness of your code. In our C like programming language named "SimPL" you can easily and simply annotate your code with preconditions and assertions (also with forall and exists expressions). We then use Microsofts Z3 theorem prover to prove if the behaviour of your program matches what you expected. The easy to use GUI with an integrated Interpreter and Debugger (with a Stackview and HotCodeReplacement) makes it even easier to write your code and find errors. This project has been developed during a University project called PSE ("Praxis der Softwareentwicklung" / "practical experience in software developement") at the Karlsruhe Institute of Technology (KIT) by Andreas Eberle, Nicolas Loza, Olga Plisovskaya, Andreas Waidler and Michael Zangl. Other Projects and pages of the team's members: www.settlers-android-clone.com (by Andreas Eberle and Michael Zangl) www.andreas-eberle.com

Scertify™ Refactoring Assessment is an open source component dedicated to development & QA teams that provides exclusive benchmark data on Software Quality. It automatically detects the portions of an application that can be refactored, gives valuable information on refactoring strategies, and costs. Though IT departments have matured these last 10 years and have now no doubt on the benefits of a continuous control of code quality, three major concerns were still remaining, without any tools able to effectively addressing these needs: * How to understand quality indicators, and how to compare them with the state of the art? * How to measure and manage the gap between the absolute quality level of a software, and a reasonable (reachable) target of quality? * What are the shortest and safe ways to achieve your quality goals?

Code Coverage Tool For Oracle PL/SQL