<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title>JavaToolbox Category : Code analysis - Standards verifiers</title>
    <link>https://javatoolbox.com/categories/code-analysers-standards-verifiers</link>
    <description>Category of tools referenced on JavaToolbox.com</description>
    <managingEditor>info@NOJavaToolboxSPAM.com</managingEditor>
    <webMaster>info@NOJavaToolboxSPAM.com</webMaster>
    <language>en</language>
    <copyright>Fabrice Marguerie</copyright>
    <pubDate>Tue, 14 Apr 2026 06:39:06 GMT</pubDate>
    <lastBuildDate>Tue, 14 Apr 2026 06:39:06 GMT</lastBuildDate>
    <ttl>60</ttl>
    <image>
      <url>https://z.javatoolbox.com/style/LogoForRss.png</url>
      <title>JavaToolbox Category : Code analysis - Standards verifiers</title>
      <link>https://javatoolbox.com/categories/code-analysers-standards-verifiers</link>
    </image>
    <item>
      <title>JRequire</title>
      <link>https://javatoolbox.com/tools/jrequire</link>
      <guid>https://javatoolbox.com/tools/jrequire</guid>
      <pubDate>Tue, 20 Sep 2005 09:49:20 GMT</pubDate>
      <description>&lt;p&gt;Requirement coverage tool that facilitates focusing on requirements as you develop code.
&lt;br /&gt;&lt;br /&gt;JRequire works on top of the JUnit unit testing framework to identify the requirement coverage in the code. This also makes JRequire useful for projects that use tools that operate on top of JUnit, such as Cactus, StrutsTestcase, etc.
&lt;br /&gt;From a developer's perspective, JRequire facilitates getting a view of: requirements successfully covered by code; broken requirements; requirements that are not covered.
&lt;br /&gt;As a project manager you get a visibility on whether you are meeting the project requirements, and the potential risk areas. In addition, as the code enhances and unit tests fail, you can identify the requirements that are at risk.
&lt;br /&gt;&lt;br /&gt;JRequire is integrated with the Eclipse IDE and Ant.
&lt;br /&gt;JRequire is available as Community Edition (free for non-commercial use only) and Commercial Edition.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jrequire"&gt;more about JRequire&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lint4j</title>
      <link>https://javatoolbox.com/tools/lint4j</link>
      <guid>https://javatoolbox.com/tools/lint4j</guid>
      <pubDate>Tue, 13 Dec 2005 17:10:30 GMT</pubDate>
      <description>&lt;p&gt;Lint4j ("Lint for Java") is a static Java source and byte code analyzer that detects locking and threading issues, performance and scalability problems, and checks complex contracts such as Java serialization by performing type, data flow, and lock graph analysis. It has plugins for Ant, Maven, Eclipse as well as Unix and Windows command line utilities.
&lt;br /&gt;&lt;br /&gt;Lint4j reports suspicious coding patterns and obvious problems, which helps developers speed up code reviews and find issues very early in the software development lifecycle.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/lint4j"&gt;more about Lint4j&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sonar</title>
      <link>https://javatoolbox.com/tools/sonar</link>
      <guid>https://javatoolbox.com/tools/sonar</guid>
      <pubDate>Sat, 26 Jan 2008 14:51:45 GMT</pubDate>
      <description>&lt;p&gt;Quality control tool that enables to collect, analyze and report metrics on source code.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- All projects at a glance: Have a quick insight of your portfolio’s health is possible even with hundreds of projects. 	
&lt;br /&gt;- Coding rules: More than 600 coding rules are provided off the shelf from simple naming convention to complex anti-pattern detection. Need more? Write your own rules.
&lt;br /&gt;- Standard metrics: Retrieve in Sonar all classical metrics related to Lines of Code, Cyclomatic Complexity, Duplicated code, Comments, etc.
&lt;br /&gt;- Drill down to source code: Want to know why a project has for instance so many coding rules violations? Drill down to modules then to packages and finally to source code.
&lt;br /&gt;- Unit Tests and code coverage
&lt;br /&gt;- TimeMachine: Sonar helps you replay the past and show you how quality metrics evolve in time.
&lt;br /&gt;- Maven ready
&lt;br /&gt;- Leverage existing components: Sonar can transparently orchestrate tools like Checkstyle, PMD, Findbugs, Clover, and Cobertura.
&lt;br /&gt;- Plugins: Add new features to Sonar to suit your requirements or cover new languages.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/sonar"&gt;more about Sonar&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JStyle</title>
      <link>https://javatoolbox.com/tools/jstyle</link>
      <guid>https://javatoolbox.com/tools/jstyle</guid>
      <pubDate>Mon, 04 Jul 2005 07:35:34 GMT</pubDate>
      <description>&lt;p&gt;Analyzes Java source to offer comments on the code and to generate metrics.
&lt;br /&gt;&lt;br /&gt;Some categories of comments are: Class naming conventions; Class member naming conventions; Class section ordering; Coding practices that affect reusability; Unsafe exception handling practices; Design deficiencies.
&lt;br /&gt;&lt;br /&gt;Some of the metrics generated are: Depth of Inheritance; Class fan-in/fan-out; RFC; LCOM; Cyclomatic Number; Halstead Measures; Weighted Methods Complexity.
&lt;br /&gt;&lt;br /&gt;Other product highlights:
&lt;br /&gt;- Two scripting languages JMScript and VBScript are built-in to extend the functionality of JStyle.
&lt;br /&gt;- Parsed and analyzed information is available to the script in the form of several COM objects.
&lt;br /&gt;- Supports a syntax-aware text editor. The editor functionality is exposed via COM objects for use within scripts.
&lt;br /&gt;- A code browser that is integrated with editor for easier navigation. Right mouse button brings up a context sensitive menu.
&lt;br /&gt;- Supports compressed jar files.
&lt;br /&gt;- A class browser that supports Javadoc comments is also included.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jstyle"&gt;more about JStyle&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>jMetra</title>
      <link>https://javatoolbox.com/tools/jmetra</link>
      <guid>https://javatoolbox.com/tools/jmetra</guid>
      <pubDate>Fri, 12 May 2006 10:27:50 GMT</pubDate>
      <description>&lt;p&gt;Tool for collecting project metrics and outputting them into XML files.
&lt;br /&gt;jMetra can also generate HTML documentation from the produced metrics files.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Collects Lines-of-code-counted (LOCC), Method count, and Class count at the package level. Collects Method counts and LOCC for individual classes. Metrics are provided for both individual packages and the summation of results from all subpackages.
&lt;br /&gt;- Automation of metrics collection across a project.
&lt;br /&gt;- Resulting metrics for a project are represented in a XML document.
&lt;br /&gt;- Allows metrics results taken across time to be aggregated into XML documents than span multiple metrics collections (i.e. builds).
&lt;br /&gt;- Continuity in tracking source code even as it changes class name or package location through the project lifecycle.
&lt;br /&gt;- Generation of jMetraDoc for viewing of results. jMetraDoc mimics the layout and navigation of JavaDoc.
&lt;br /&gt;- Customizable jMetraDoc using a template engine and customized cascading style sheets (css).
&lt;br /&gt;- Automated compilation and metrics calculations for JSPs.
&lt;br /&gt;- Command line interface.
&lt;br /&gt;- Ant integration&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jmetra"&gt;more about jMetra&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Structure101</title>
      <link>https://javatoolbox.com/tools/structure101</link>
      <guid>https://javatoolbox.com/tools/structure101</guid>
      <pubDate>Tue, 13 Jun 2006 12:07:46 GMT</pubDate>
      <description>&lt;p&gt;Helps you understand the structure of your code-base (design, architecture).
&lt;br /&gt;&lt;br /&gt;Structure101 for Java parses your byte code and creates an implementation model of all the dependencies mapped up through the compositional hierarchy. You can browse the model and view dependency diagrams at any level - method, class, package or jar.
&lt;br /&gt;&lt;br /&gt;With Structure101 you can:
&lt;br /&gt;- Control architecture: See how your high-level components depend on each other and why. Find out when your architecture is accidently changed by code-level changes at the coal-face, and how to best reverse out the rogue dependencies.
&lt;br /&gt;- Control structural complexity: Set complexity limits at each level (method, class or package) and Structure101 will measure the degree to which any item exceeds the limits and relate this to the amount of code impacted so that you can prioritize any repair work. Discover the locations of productivity-killing package dependency cycles and analyze how to break them.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/structure101"&gt;more about Structure101&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>DevPartner Java Edition</title>
      <link>https://javatoolbox.com/tools/devpartner-java-edition</link>
      <guid>https://javatoolbox.com/tools/devpartner-java-edition</guid>
      <pubDate>Wed, 23 Sep 2009 22:51:58 GMT</pubDate>
      <description>&lt;p&gt;Helps resolve problems associated with run-time performance, memory utilization and multi-threading.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- automates development productivity tasks such as: distributed application analysis, memory analysis, performance analysis, code coverage analysis, thread analysis, code review, design analysis and refactoring
&lt;br /&gt;- includes OptimalAdvisor: a design and code validation tool that offers advice into the structure and effectiveness of the overall application.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/devpartner-java-edition"&gt;more about DevPartner Java Edition&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JavaNCSS</title>
      <link>https://javatoolbox.com/tools/javancss</link>
      <guid>https://javatoolbox.com/tools/javancss</guid>
      <pubDate>Sat, 26 Jan 2008 14:58:54 GMT</pubDate>
      <description>&lt;p&gt;Source measurement suite for Java.
&lt;br /&gt;JavaNCSS is a command line utility that measures two standard source code metrics for the Java programming language. The metrics are collected globally, for each class and/or for each function.
&lt;br /&gt;JavaNCSS can optionally present its output with a little graphical user interface. To interactively select Java source files for counting, Jacob (a Java class browser and project manager) can be used for this purpose. JavaNCSS can also be used out of an Ant build.xml script as it comes bundled with an Ant task.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Metrics can be applied to global-, class-, or function-level
&lt;br /&gt;- Non Commenting Source Statements (NCSS)
&lt;br /&gt;- Cyclomatic Complexity Number (McCabe metric)
&lt;br /&gt;- Packages, classes, functions and inner classes are counted
&lt;br /&gt;- Number of formal Javadoc comments per class and method
&lt;br /&gt;- Average values are calculated
&lt;br /&gt;- Command line driven
&lt;br /&gt;- A GUI is provided for better output browsing as well as the integration of JavaNCSS in a project manager and class browser named Jacob for easy selection of input source files
&lt;br /&gt;- XML output (optional)
&lt;br /&gt;- XSLT stylesheets provided for further generation of HTML, and SVG reports and as a basis for your own custom reports
&lt;br /&gt;- Ant task
&lt;br /&gt;- Support for Java 1.5 syntax (generics, enums, etc.)&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/javancss"&gt;more about JavaNCSS&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jindent</title>
      <link>https://javatoolbox.com/tools/jindent</link>
      <guid>https://javatoolbox.com/tools/jindent</guid>
      <pubDate>Sun, 27 Feb 2005 19:01:23 GMT</pubDate>
      <description>&lt;p&gt;Source code formatter for Java with custom coding style support.
&lt;br /&gt;A program like Jindent is also referred to as a Java formatter, pretty printer, code beautifier or Java indent tool.
&lt;br /&gt;&lt;br /&gt;Jindent empowers you to transform any foreign Java source code to meet your preferred coding style or any common Java code convention.
&lt;br /&gt;Furthermore Jindent can format, generate and complete Javadoc comments on demand.
&lt;br /&gt;Features include:
&lt;br /&gt;- Intelligent Line Wrapping, Indentation, Tabular Code Alignment and Justification
&lt;br /&gt;- Brace Style Transformation
&lt;br /&gt;- Uniform White Space Conventions
&lt;br /&gt;- Template-driven Javadoc Generation
&lt;br /&gt;- Javadoc Formatting and Elimination
&lt;br /&gt;- Header and Footer Templates
&lt;br /&gt;- Comment Formatting and Elimination
&lt;br /&gt;- Code Separation
&lt;br /&gt;- Conversion between Unicode and a number of other character encodings
&lt;br /&gt;- Open API
&lt;br /&gt;- Integrations for Java IDEs: JBuilder, Eclipse, JDeveloper, Visual Cafe, Forte/Netbeans, IntelliJ IDEA, JCreator
&lt;br /&gt;- Integrations for Java build tools: Ant
&lt;br /&gt;- Integrations for text editors: Emacs, Vi/Vim, UltraEdit, Textpad
&lt;br /&gt;- Integrations for version control systems: CVS, WinCVS&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jindent"&gt;more about Jindent&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>PMD</title>
      <link>https://javatoolbox.com/tools/pmd</link>
      <guid>https://javatoolbox.com/tools/pmd</guid>
      <pubDate>Mon, 21 Feb 2005 19:02:54 GMT</pubDate>
      <description>&lt;p&gt;PMD scans Java source code and looks for potential problems like:
&lt;br /&gt;- Possible bugs: empty try/catch/finally/switch statements
&lt;br /&gt;- Dead code: unused local variables, parameters and private methods
&lt;br /&gt;- Suboptimal code: wasteful String/StringBuffer usage
&lt;br /&gt;- Overcomplicated expressions: unnecessary if statements, for loops that could be while loops
&lt;br /&gt;- Duplicate code: copied/pasted code means copied/pasted bugs
&lt;br /&gt;&lt;br /&gt;PMD is integrated with JDeveloper, Eclipse, JEdit, JBuilder, BlueJ, CodeGuide, NetBeans/Sun Java Studio Enterprise/Creator, IntelliJ IDEA, TextPad, Maven, Ant, Gel, JCreator, and Emacs.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/pmd"&gt;more about PMD&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jlint</title>
      <link>https://javatoolbox.com/tools/jlint</link>
      <guid>https://javatoolbox.com/tools/jlint</guid>
      <pubDate>Sun, 06 Feb 2005 17:43:32 GMT</pubDate>
      <description>&lt;p&gt;Checks Java code and find bugs, inconsistencies and synchronization problems by doing data flow analysis and building lock graph.
&lt;br /&gt;&lt;br /&gt;Jlint consists of two separate programs performing syntax and semantic verification. 
&lt;br /&gt;- AntiC fixes problems with C, C++, Objective C and Java grammars, which can cause dangerous programmer's bugs, undetected by compiler. It uses hand-written scanner and simple top-down parser, to detect such bugs as suspicious use of operators priorities, absence of break in switch code, wrong assumption about constructions bodies...
&lt;br /&gt;- The Semantic verifier Jlint extracts information from Java class files. By using debugging information Jlint can associate reported messages with Java sources. Jlint performs local and global data flow analyses, calculating possible values of local variables and catching redundant and suspicious calculations. Jlint is able to detect invocation of method with possible "null" value of formal parameter and using of this parameter in method without check for "null". Jlint also builds lock dependency graph for classes dependencies and uses this graph to detect situations, which can cause deadlock during multithreaded program execution. Jlint is also able to detect possible race condition problem, when different threads can concurrently access the same variables. 
&lt;br /&gt;&lt;br /&gt;All messages reported by Jlint are grouped in categories, and it is possible to enable or disable reporting messages of specific category as well as concrete messages.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jlint"&gt;more about Jlint&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Klocwork Developer for Java</title>
      <link>https://javatoolbox.com/tools/klocwork-developer-for-java</link>
      <guid>https://javatoolbox.com/tools/klocwork-developer-for-java</guid>
      <pubDate>Thu, 18 Sep 2008 17:08:32 GMT</pubDate>
      <description>&lt;p&gt;Source code analysis Eclipse plug-in.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Automated Detection of over 200 security vulnerabilities and quality defects - no test cases need to be generated or run.
&lt;br /&gt;- Persistent analysis results so you can keep track of issues over time.
&lt;br /&gt;- Integration with Eclipse including issue traceback in the source code.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/klocwork-developer-for-java"&gt;more about Klocwork Developer for Java&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JiveLint</title>
      <link>https://javatoolbox.com/tools/jivelint</link>
      <guid>https://javatoolbox.com/tools/jivelint</guid>
      <pubDate>Wed, 28 Sep 2005 06:36:39 GMT</pubDate>
      <description>&lt;p&gt;Command line tool employing static analysis on your Java source code.
&lt;br /&gt;Potential bugs and weak points are reported and the manual describes how the source code can be improved. JiveLint also checks that the source code follows a set of coding convention rules.
&lt;br /&gt;For example, JiveLint will find unused code and variables, switch blocks without a default case, if a class overrides "Object.equals()" but not "Object.hashCode()", if code use == to compare Strings instead of equals().&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jivelint"&gt;more about JiveLint&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Resource Standard Metrics</title>
      <link>https://javatoolbox.com/tools/resource-standard-metrics</link>
      <guid>https://javatoolbox.com/tools/resource-standard-metrics</guid>
      <pubDate>Wed, 04 May 2005 21:43:48 GMT</pubDate>
      <description>&lt;p&gt;Resource Standard Metrics (RSM) performs source code metrics and quality analysis for C, C++, C# and Java in any operating system.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Analyze lines of code and derive function points
&lt;br /&gt;- Logic complexity
&lt;br /&gt;- Object metrics and inheritance
&lt;br /&gt;- Functional and file metrics
&lt;br /&gt;- Quality check against more than 50 known style and logic problems compilers miss - Create metrics/analysis reports in XHTML, CSV, or Text format.
&lt;br /&gt;- Perform code peer reviews and enforce coding standards.
&lt;br /&gt;- Perform metrics differentials between two code baselines to determine the degree of code change over time.
&lt;br /&gt;- Command line to script and integrate into configuration managers and IDEs including ClearCase, Eclipse, JBuilder, and Visual Studio.
&lt;br /&gt;- Windows GUI Wizard.
&lt;br /&gt;- C# metrics and analysis and user defined quality analysis using regular expressions.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/resource-standard-metrics"&gt;more about Resource Standard Metrics&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Creole</title>
      <link>https://javatoolbox.com/tools/creole</link>
      <guid>https://javatoolbox.com/tools/creole</guid>
      <pubDate>Sun, 27 Feb 2005 19:03:28 GMT</pubDate>
      <description>&lt;p&gt;Eclipse plug-in that allows you to explore your Java code visually. You can see your code's structure and the links (references, accesses, etc) between its different pieces.
&lt;br /&gt;Creole uses SHriMP. SHriMP is both an application and a technique, designed for visualizing and exploring software architecture and any other information space. SHriMP (Simple Hierarchical Multi-Perspective) is a domain-independent visualization technique designed to enhance how people browse and explore complex information spaces.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/creole"&gt;more about Creole&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>QJ-Pro</title>
      <link>https://javatoolbox.com/tools/qj-pro</link>
      <guid>https://javatoolbox.com/tools/qj-pro</guid>
      <pubDate>Sat, 12 Mar 2005 00:56:56 GMT</pubDate>
      <description>&lt;p&gt;Toolset for static analysis of Java source code: a combination of automatic code review and automatic coding standards enforcement.
&lt;br /&gt;QJ-Pro's main functionality is to ensure that no errors enter the source code when it is written or modified, resulting in more reliable, maintainable, testable and portable Java programs.
&lt;br /&gt;&lt;br /&gt;The tool is based on quality attributes such as reliability, maintainability, testability and portability, that are usually defined in a so-called coding standard. QJ-Pro comes with a set of good programming practices that can be enforced automatically.
&lt;br /&gt;QJ-Pro analyzes your Java source code and outputs information about the quality. The amount and type of output depends on the settings of the tool and the quality of the source code. The tool is most effectively used in the coding phase of a project to prevent an expensive maintenance and testing effort later on in the development process.
&lt;br /&gt;&lt;br /&gt;QJ-Pro comes as a standalone application for Windows and Linux, and as plug-ins for Eclipse, JBuilder and JDeveloper.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/qj-pro"&gt;more about QJ-Pro&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jalopy</title>
      <link>https://javatoolbox.com/tools/jalopy</link>
      <guid>https://javatoolbox.com/tools/jalopy</guid>
      <pubDate>Wed, 26 Jan 2005 11:40:28 GMT</pubDate>
      <description>&lt;p&gt;Jalopy is a java source code formatter depending on some widely configurable rules (By default the SUN's standards).
&lt;br /&gt;It makes it possible to homogenize the java files whithout putting a formatting burden on individual programers.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Brace style transformation  
&lt;br /&gt;- Fine-grained white space settings  
&lt;br /&gt;- Indentation  
&lt;br /&gt;- Intelligent line wrapping  
&lt;br /&gt;- Code separation  
&lt;br /&gt;- Javadoc auto-generation  
&lt;br /&gt;- Header/Footer templates  
&lt;br /&gt;- Command-line interface  
&lt;br /&gt;- Client API  
&lt;br /&gt;- Several Plug-ins (Ant, Eclipse, JBuilder, ...)&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jalopy"&gt;more about Jalopy&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>McCabe IQ</title>
      <link>https://javatoolbox.com/tools/mccabe-iq</link>
      <guid>https://javatoolbox.com/tools/mccabe-iq</guid>
      <pubDate>Mon, 15 Sep 2008 13:24:07 GMT</pubDate>
      <description>&lt;p&gt;Interactive, visual environment for managing software quality through static analysis and test/code coverage.
&lt;br /&gt;McCabeIQ comes in three editions: Developers, Test Team, Enterprise.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Software metrics: McCabe Cyclomatic Complexity; McCabe Essential Complexity; Module Design Complexity; Integration Complexity; Lines of Code; Halstead.
&lt;br /&gt;- Color-coded structure Battlemaps, scatter plot diagrams, and flow graphs
&lt;br /&gt;- Metric Trend Reports: track a system's metric values over time to document the progress made in improving the overall stability and quality of the project
&lt;br /&gt;- Customized reporting
&lt;br /&gt;- Plan software testing resources in advance, identifying test paths and the number of tests required
&lt;br /&gt;- Code coverage
&lt;br /&gt;- McCabe Compare: helps you locate redundant code so you can either delete or reengineer it
&lt;br /&gt;- McCabe Data: track data use within your programs and anticipate complexity
&lt;br /&gt;- McCabe Change: identify the modules in your program that have changed since the first time you parsed your code
&lt;br /&gt;- McCabe Slice: uncover your program’s internal architecture
&lt;br /&gt;- Supports Ada, ASM86/95, C, C#, C++.NET, C++, Cobol, Fortran, Java, JSP, Perl, PL1, VB, VB.NET
&lt;br /&gt;- Enterprise Edition provides all the functionality of the Developers and Test Team Editions. In addition, it provides enterprise reporting, reengineering capabilities, change analysis, and secure web-enabled test data collection.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/mccabe-iq"&gt;more about McCabe IQ&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Simian</title>
      <link>https://javatoolbox.com/tools/simian</link>
      <guid>https://javatoolbox.com/tools/simian</guid>
      <pubDate>Wed, 28 Jan 2004 02:33:51 GMT</pubDate>
      <description>&lt;p&gt;Simian (Similarity Analyser) identifies duplication in Java, C#, C, C++, COBOL, Ruby, JSP, HTML, XML and Visual Basic source code. Simian can also be used on any human readable files such as plain text files.
&lt;br /&gt;Especially on large enterprise projects, it can be difficult for any one developer to keep track of all the features (classes, methods, etc.) of the system. Simian can be used as part of the build process during development or as a guide when re-factoring. Think of Simian as an independent pair of eyes that will assist in raising the quality of your software.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/simian"&gt;more about Simian&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Klocwork Insight</title>
      <link>https://javatoolbox.com/tools/klocwork-insight</link>
      <guid>https://javatoolbox.com/tools/klocwork-insight</guid>
      <pubDate>Thu, 18 Sep 2008 17:17:57 GMT</pubDate>
      <description>&lt;p&gt;Source code analysis tool.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Connected desktop analysis
&lt;br /&gt;- Architecture visualization and optimization
&lt;br /&gt;- Analysis that identifies hundreds of security vulnerabilities and quality defects in your code
&lt;br /&gt;- Code analysis from within the developer IDE (Eclipse, IntelliJ IDEA, Rational Application Developer, text editors and command line interfaces...)
&lt;br /&gt;- Code visualization tool
&lt;br /&gt;- Extensibility framework: Developers can write their own style or path analysis checkers to meet specific coding or organizational requirements
&lt;br /&gt;- Reporting&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/klocwork-insight"&gt;more about Klocwork Insight&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JarJarDiff</title>
      <link>https://javatoolbox.com/tools/jarjardiff</link>
      <guid>https://javatoolbox.com/tools/jarjardiff</guid>
      <pubDate>Sun, 02 Jan 2005 05:17:42 GMT</pubDate>
      <description>&lt;p&gt;Compares two versions of the same codebase and reports the differences in the API. JarJarDiff lists new, changed, and removed elements such as packages, classes, interfaces, methods, constructors and fields. You can tailor the reports to focus on your public, published API versus the private, internal one.
&lt;br /&gt;Comes packaged with Dependency Finder.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jarjardiff"&gt;more about JarJarDiff&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>eoSense</title>
      <link>https://javatoolbox.com/tools/eosense</link>
      <guid>https://javatoolbox.com/tools/eosense</guid>
      <pubDate>Mon, 29 Oct 2007 17:10:33 GMT</pubDate>
      <description>&lt;p&gt;Java EE testing and analysis tool for discovering and understanding performance and reliability-related problems.
&lt;br /&gt;eoSense uses built-in knowledge of the Java EE framework to test and visualize runtime application architecture and operation. A range of construction problems and anti-patterns are automatically detected. Complex application architecture and operation are explained visually.
&lt;br /&gt;&lt;br /&gt;Use of the following Java EE services are verified and visualized automatically: EJB, WebServices/SOAP, Servlets, Struts, JTA, JMS, JDBC, JNDI.
&lt;br /&gt;eoSense supports WebLogic (6.1, 8.1, 9.1, 9.2) and WebSphere (6.1).&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/eosense"&gt;more about eoSense&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>FindBugs</title>
      <link>https://javatoolbox.com/tools/findbugs</link>
      <guid>https://javatoolbox.com/tools/findbugs</guid>
      <pubDate>Thu, 17 Mar 2005 18:01:47 GMT</pubDate>
      <description>&lt;p&gt;Open-source bug finding tool for Java.
&lt;br /&gt;FindBugs operates on Java bytecode and uses static analysis techniques to find a variety of potential bugs.
&lt;br /&gt;&lt;br /&gt;FindBugs is based on the concept of bug patterns. A bug pattern is a code idiom that is often an error.
&lt;br /&gt;Bug patterns arise for a variety of reasons:
&lt;br /&gt;- Difficult language features
&lt;br /&gt;- Misunderstood API methods
&lt;br /&gt;- Misunderstood invariants when code is modified during maintenance
&lt;br /&gt;- Garden variety mistakes: typos, use of the wrong boolean operator
&lt;br /&gt;&lt;br /&gt;FindBugs doesn't focus on style or formatting; it specifically tries to find real bugs or potential performance problems.
&lt;br /&gt;Comes with an Eclipse plug-in.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/findbugs"&gt;more about FindBugs&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Lattix LDM for Java</title>
      <link>https://javatoolbox.com/tools/lattix-ldm-for-java</link>
      <guid>https://javatoolbox.com/tools/lattix-ldm-for-java</guid>
      <pubDate>Mon, 02 Oct 2006 20:10:31 GMT</pubDate>
      <description>&lt;p&gt;Enables you to analyze the architecture of your Java application in terms of the elements and their relationships (jars, packages, classes, methods, etc.).
&lt;br /&gt;&lt;br /&gt;Lattix LDM allows you to analyze your architecture, edit the structure to create what-if and should-be architectures, and then create design rules to formalize and communicate that architecture to your development organization. Lattix LDM uses a dependency-matrix approach to obtain information about an application. It displays the matrix and lets users conceptually reorganize the layers and packaging structure. Continual monitoring of an application for structural deterioration is also enabled; thereby allowing remedial action to be taken before the problem escalates to a major maintenance problem.
&lt;br /&gt;Lattix LDM offers a GUI as well as a command line options to facilitate integration with build tools or IDEs.  Plugins for NetBeans and Eclipse are available. It also includes support for Hibernate and Spring Framework.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/lattix-ldm-for-java"&gt;more about Lattix LDM for Java&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>TeamCity</title>
      <link>https://javatoolbox.com/tools/teamcity</link>
      <guid>https://javatoolbox.com/tools/teamcity</guid>
      <pubDate>Fri, 21 Jul 2006 01:20:52 GMT</pubDate>
      <description>&lt;p&gt;IDE-independent integrated team environment.
&lt;br /&gt;TeamCity automates and coordinates key collaborative processes to eliminate manual systems and delays, providing integration with multiple build and test tools, real-time unit test frequency, server-side inspections and code coverage analysis.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- continuous integration and testing
&lt;br /&gt;- server-side code analysis
&lt;br /&gt;- build management
&lt;br /&gt;- automated team communication
&lt;br /&gt;- code coverage analysis and reporting
&lt;br /&gt;- web-based interface and project dashboard
&lt;br /&gt;- extensibility
&lt;br /&gt;- IntelliJ IDEA, Eclipse and Visual Studio integration
&lt;br /&gt;- pre-tested (delayed) commit
&lt;br /&gt;- remote run for personal builds
&lt;br /&gt;&lt;br /&gt;Supported environments:
&lt;br /&gt;- Ant, Maven, NAnt, MSBuild
&lt;br /&gt;- Having an IntelliJ IDEA project or a Visual Studio solution, you can build your application with TeamCity, even without providing a build script
&lt;br /&gt;- Supports JUnit and NUnit
&lt;br /&gt;- Integrates with Perforce, CVS, Subversion, Visual SourceSafe, StarTeam&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/teamcity"&gt;more about TeamCity&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Convergence</title>
      <link>https://javatoolbox.com/tools/convergence</link>
      <guid>https://javatoolbox.com/tools/convergence</guid>
      <pubDate>Tue, 15 Mar 2005 03:09:34 GMT</pubDate>
      <description>&lt;p&gt;Quality management dashboard that enables tracking of application quality early in the software development life-cycle.
&lt;br /&gt;&lt;br /&gt;With Convergence, teams can:
&lt;br /&gt;- Determine if new code is being unit tested
&lt;br /&gt;- Track and understand code growth with respect to test coverage
&lt;br /&gt;- Identify areas to focus on to detect defects
&lt;br /&gt;- Identify the cause of test failures
&lt;br /&gt;- Uncover practices that impair maintainability and increase risk
&lt;br /&gt;&lt;br /&gt;Unlike static build reports, which convey limited information, Convergence tracks and relates multiple data points, enabling teams to understand and report on application quality through a unified focus on:
&lt;br /&gt;- NUnit/JUnit test statuses, code coverage and outputs
&lt;br /&gt;- Source code and code changes in CM systems like CVS and Subversion
&lt;br /&gt;- Assembly/package and class dependencies
&lt;br /&gt;- Code size, code audits, complexity and coupling
&lt;br /&gt;- NUnit/JUnit test &amp;amp; defect report relationships in defect tracking systems like JIRA and Bugzilla&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/convergence"&gt;more about Convergence&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Hammurapi</title>
      <link>https://javatoolbox.com/tools/hammurapi</link>
      <guid>https://javatoolbox.com/tools/hammurapi</guid>
      <pubDate>Fri, 15 Apr 2005 07:26:18 GMT</pubDate>
      <description>&lt;p&gt;Componentry for automated code reviews.
&lt;br /&gt;Hammurapi allows you to establish code governance processes in your organization by injecting automated code review "hooks" into development and build processes.
&lt;br /&gt;&lt;br /&gt;Features  include:
&lt;br /&gt;- Cascading inspector sets 
&lt;br /&gt;- Loading inspector sets from URL 
&lt;br /&gt;- Multiple levels of analyzis: Source code (Token stream including whitespace and comments; Parse tree), Package, Repository 
&lt;br /&gt;- Three levels of reporting: Compilation unit, Package, Summary 
&lt;br /&gt;- Source documentation 
&lt;br /&gt;- Metrics 
&lt;br /&gt;- Severity level highlighting 
&lt;br /&gt;- Fails builds on low Sigma, high DPMO (Defects per million opportunities) or on severity level 
&lt;br /&gt;- Embedded inspectors 
&lt;br /&gt;- Extensibility&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/hammurapi"&gt;more about Hammurapi&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Universal Report</title>
      <link>https://javatoolbox.com/tools/universal-report</link>
      <guid>https://javatoolbox.com/tools/universal-report</guid>
      <pubDate>Tue, 21 Dec 2004 08:33:23 GMT</pubDate>
      <description>&lt;p&gt;Generic reverse engineering software for analysis and automatic documentation of source codes (program/header/form files).
&lt;br /&gt;Universal Report's goal is to analyse and generate a structured and formatted overview of a given set of program codes. A session can be achieved either in a step-by-step way or in a completely automatic way.
&lt;br /&gt;Universal Report is not focused on a specific programming language (will run with codes in Basic, C, C++, Fortran, Java, Matlab, Pascal, Visual Basic, Borland C++ Builder, Delphi, Kylix, Visual C++, Visual Basic .Net, Visual C#, Visual J++, etc....), and you can get reports in several common formats (text, latex, html) and languages (English, French, German, Spanish, Portuguese, and Italian). The universality is due to heuristics that use programming languages intersection as well as possible, and examine further specific points. The tool is parameterizable both in the behavior point of view and the quality of the outputs. Moreover, some additional features are available, including spell checking, general pattern research, automatic information extraction, automatic code formating, glossary generator, graphics generator, routines reviewing system, protection with password, and more.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/universal-report"&gt;more about Universal Report&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Checkstyle</title>
      <link>https://javatoolbox.com/tools/checkstyle</link>
      <guid>https://javatoolbox.com/tools/checkstyle</guid>
      <pubDate>Mon, 21 Feb 2005 19:00:34 GMT</pubDate>
      <description>&lt;p&gt;Designed to help programmers write Java code that adheres to a coding standard.
&lt;br /&gt;By default Checkstyle supports the Sun Code Conventions, but is configurable and can be made to support other coding standards. Sample configuration files are supplied for other well known conventions.
&lt;br /&gt;Checkstyle can check many aspects of your source code. Historically it's main functionality has been to check code layout issues, but since the internal architecture was changed in version 3, more and more checks for other purposes have been added. Now Checkstyle provides checks that find class design problems, duplicate code, or bug patterns like double checked locking.
&lt;br /&gt;Checkstyle is most useful if you integrate it in your build process or your development environment. The distribution includes: an Ant task and a command line tool.
&lt;br /&gt;Existing plug-ins for IDE and build tools include Eclipse, IntelliJ IDEA, NetBeans, JBuilder, Maven...&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/checkstyle"&gt;more about Checkstyle&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Java PathFinder</title>
      <link>https://javatoolbox.com/tools/java-pathfinder</link>
      <guid>https://javatoolbox.com/tools/java-pathfinder</guid>
      <pubDate>Wed, 04 May 2005 16:46:35 GMT</pubDate>
      <description>&lt;p&gt;System to verify executable Java bytecode programs.
&lt;br /&gt;&lt;br /&gt;In its basic form, Java PathFinder (JPF) is a Java Virtual Machine (JVM) that is used as an explicit state software model checker, systematically exploring all potential execution paths of a program to find violations of properties like deadlocks or unhandled exceptions. Other than traditional debuggers, JPF reports the whole execution path that leads to a defect. JPF is especially suitable to find hard-to-test concurrency defects in multithreaded programs.
&lt;br /&gt;&lt;br /&gt;JPF is a pure Java application that can be run either as a standalone command line tool, or embedded into systems like development environments. It was mostly developed - and is still used - at the NASA Ames Research Center. Started in 1999 as a feasibility study for software model checking, JPF since then has found its way into academia and industry, and even helped to detect defects in real spacecraft. &lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/java-pathfinder"&gt;more about Java PathFinder&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JDepend</title>
      <link>https://javatoolbox.com/tools/jdepend</link>
      <guid>https://javatoolbox.com/tools/jdepend</guid>
      <pubDate>Mon, 03 Jan 2005 23:25:56 GMT</pubDate>
      <description>&lt;p&gt;Traverses Java class file directories and generates design quality metrics for each Java package.
&lt;br /&gt;JDepend allows you to automatically measure the quality of a design in terms of its extensibility, reusability, and maintainability to manage package dependencies effectively.
&lt;br /&gt;Metrics include:
&lt;br /&gt;- Number of Classes and Interfaces
&lt;br /&gt;- Afferent Couplings
&lt;br /&gt;- Efferent Couplings
&lt;br /&gt;- Abstractness
&lt;br /&gt;- Instability
&lt;br /&gt;- Distance from the Main Sequence
&lt;br /&gt;- Package Dependency Cycles&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jdepend"&gt;more about JDepend&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Enerjy</title>
      <link>https://javatoolbox.com/tools/enerjy</link>
      <guid>https://javatoolbox.com/tools/enerjy</guid>
      <pubDate>Thu, 18 Dec 2008 16:07:34 GMT</pubDate>
      <description>&lt;p&gt;Eclipse plug-in that analyzes Java source code files to spot bugs before they happen.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/enerjy"&gt;more about Enerjy&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Eclipse Checkstyle Plug-in</title>
      <link>https://javatoolbox.com/tools/eclipse-checkstyle-plug-in</link>
      <guid>https://javatoolbox.com/tools/eclipse-checkstyle-plug-in</guid>
      <pubDate>Mon, 11 Jul 2005 08:59:40 GMT</pubDate>
      <description>&lt;p&gt;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.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/eclipse-checkstyle-plug-in"&gt;more about Eclipse Checkstyle Plug-in&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>XDepend</title>
      <link>https://javatoolbox.com/tools/xdepend</link>
      <guid>https://javatoolbox.com/tools/xdepend</guid>
      <pubDate>Thu, 05 Feb 2009 14:03:41 GMT</pubDate>
      <description>&lt;p&gt;Code base analyzer.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Analyze code structure
&lt;br /&gt;- Assess components given different metrics (Number of Lines of Code, Cyclomatic Complexity)
&lt;br /&gt;- Apprehend dependencies and navigate through artifacts
&lt;br /&gt;- Specify design rules
&lt;br /&gt;- Plan massive refactoring
&lt;br /&gt;- Code reviews
&lt;br /&gt;- Compare versions of code
&lt;br /&gt;- Query your code with a SQL-Like Code Query Language (CQL) with autocompletion support
&lt;br /&gt;- Anti-patterns detection
&lt;br /&gt;- Graphical dynamic displays
&lt;br /&gt;- Quality control rules extracted from best practices and customizable
&lt;br /&gt;- Maven plugin
&lt;br /&gt;&lt;br /&gt;Java version of the NDepend product.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/xdepend"&gt;more about XDepend&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>SourceGlider for Eclipse</title>
      <link>https://javatoolbox.com/tools/sourceglider-for-eclipse</link>
      <guid>https://javatoolbox.com/tools/sourceglider-for-eclipse</guid>
      <pubDate>Tue, 27 Feb 2007 21:26:40 GMT</pubDate>
      <description>&lt;p&gt;Code analyzer that helps you to understand the code, display its impact and dependencies, monitor code quality and stability, measure code properties, indicate the major coding problems, search the common design patterns, etc.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Show what variables actually refer to
&lt;br /&gt;- Show what values are stored in arrays and collections
&lt;br /&gt;- Methods of code browsing: 145 predefined queries
&lt;br /&gt;- Performance and quality metrics: 95 predefined metrics
&lt;br /&gt;- Tracking of code changes
&lt;br /&gt;- Java 1.5 coverage
&lt;br /&gt;- Available analysis: types, objects, callees, dependencies, exceptions, arrays, points-to (Equals), threads, impact, actual type, actual callees
&lt;br /&gt;- Requires Eclipse 3.1 or higher&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/sourceglider-for-eclipse"&gt;more about SourceGlider for Eclipse&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>JDiff </title>
      <link>https://javatoolbox.com/tools/jdiff-</link>
      <guid>https://javatoolbox.com/tools/jdiff-</guid>
      <pubDate>Mon, 03 Jan 2005 23:19:54 GMT</pubDate>
      <description>&lt;p&gt;An HTML report of API differences.
&lt;br /&gt;JDiff is a Javadoc doclet that generates an HTML report of all the packages, classes, constructors, methods, and fields which have been removed, added or changed in any way, including their documentation, when two APIs are compared.
&lt;br /&gt;This is useful for describing what has changed between two releases of a product. Only the API of each version is compared. It does not compare what the source code does when executed.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jdiff-"&gt;more about JDiff &lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Sotograph</title>
      <link>https://javatoolbox.com/tools/sotograph</link>
      <guid>https://javatoolbox.com/tools/sotograph</guid>
      <pubDate>Tue, 23 Jan 2007 09:50:11 GMT</pubDate>
      <description>&lt;p&gt;Software analysis workbench.
&lt;br /&gt;Sotograph supports continuous architecture management, monitoring of internal software quality, comprehension of complex software systems and re-engineering.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- stores the structural information about a software system into a central repository. This information is then used for visualization and analysis such as structure, dependency, cycle, quality, what-if and impact analysis on different abstraction levels.
&lt;br /&gt;- determines for the entire software system where the source code does not correspond to the designed architecture
&lt;br /&gt;- can localize and visualize illegal relationships from the architecture level down to the source code
&lt;br /&gt;- can manage information about several versions of a software system
&lt;br /&gt;- able to analyze Java, C# and C/C++ software&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/sotograph"&gt;more about Sotograph&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Crap4j</title>
      <link>https://javatoolbox.com/tools/crap4j</link>
      <guid>https://javatoolbox.com/tools/crap4j</guid>
      <pubDate>Sat, 13 Dec 2008 11:10:00 GMT</pubDate>
      <description>&lt;p&gt;Java implementation of the CRAP (Change Risk Analysis and Predictions) software metric.
&lt;br /&gt;CRAP: a mildly offensive metric name to help protect you from truly offensive code.
&lt;br /&gt;The CRAP metric combines cyclomatic complexity and code coverage from automated tests (e.g. JUnit tests) to help you identify code that might be particularly difficult to understand, test, or maintain – the kind of code that makes developers say: "This is crap!" or, if they are stuck maintaining it, "Oh, crap!".
&lt;br /&gt;Crap4j comes in two forms: Eclipse update and Ant task.
&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/crap4j"&gt;more about Crap4j&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>CodeAssure</title>
      <link>https://javatoolbox.com/tools/codeassure</link>
      <guid>https://javatoolbox.com/tools/codeassure</guid>
      <pubDate>Thu, 21 Sep 2006 14:15:55 GMT</pubDate>
      <description>&lt;p&gt;Static source-code analyzer that provides a solution for identifying, assessing, and remediating software vulnerabilities.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Eclipse and Visual Studio support
&lt;br /&gt;- Java, C, C++ analysis
&lt;br /&gt;- Vulnerability knowledgebase
&lt;br /&gt;- Security Advisor: provides explanations of vulnerabilities
&lt;br /&gt;- Shared vulnerability comments and review status
&lt;br /&gt;- Automated build integration
&lt;br /&gt;- Management reporting / trend analysis
&lt;br /&gt;- Policy enforcement
&lt;br /&gt;- Customer rules
&lt;br /&gt;- Access control / Centralized administration
&lt;br /&gt;- Compliance management and definition&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/codeassure"&gt;more about CodeAssure&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Jacobe</title>
      <link>https://javatoolbox.com/tools/jacobe</link>
      <guid>https://javatoolbox.com/tools/jacobe</guid>
      <pubDate>Wed, 31 May 2006 08:44:22 GMT</pubDate>
      <description>&lt;p&gt;Configurable code beautifier.
&lt;br /&gt;It is possible to let Jacobe print your Java code according to the layout rules of Sun Microsystems or customize it to your own standards.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Javadoc template generation and completion rules
&lt;br /&gt;- a graphical configuration utility
&lt;br /&gt;- Ant task
&lt;br /&gt;- plug-in for Eclipse 3.1.0
&lt;br /&gt;- Supports Windows, Linux, Solaris&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/jacobe"&gt;more about Jacobe&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>SonarJ</title>
      <link>https://javatoolbox.com/tools/sonarj</link>
      <guid>https://javatoolbox.com/tools/sonarj</guid>
      <pubDate>Mon, 03 Mar 2008 18:51:58 GMT</pubDate>
      <description>&lt;p&gt;Software architecture management solution.
&lt;br /&gt;Basically there are two main use cases for SonarJ:
&lt;br /&gt;- You want to make sure that a given software architecture is reflected by the source code
&lt;br /&gt;- You want to check the technical quality of a software delivery.
&lt;br /&gt;&lt;br /&gt;Features include:
&lt;br /&gt;- Ability to check a given set of Java source and class files to its conformance to a given logical architecture
&lt;br /&gt;- Logical architecture definition
&lt;br /&gt;- Checking for architecture violations and cyclic dependencies
&lt;br /&gt;- Calculates metrics: ACD (average component dependency - about internal coupling), LOC (lines of code), Cyclomatic complexity, Assertion usage, Relational cohesion, Metrics of Robert C. Martin (abstractness, instability, etc.), and more.
&lt;br /&gt;- Ant task and Maven plugin
&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/sonarj"&gt;more about SonarJ&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Clone Doctor</title>
      <link>https://javatoolbox.com/tools/clone-doctor</link>
      <guid>https://javatoolbox.com/tools/clone-doctor</guid>
      <pubDate>Thu, 22 Oct 2009 11:03:32 GMT</pubDate>
      <description>&lt;p&gt;Clone detection and removal tool.
&lt;br /&gt;Clone Doctor is a tool that detects and removes duplicate code ("clones"). It identifies not only exact, but near-miss duplicates in software systems and can be used on a variety of languages.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/clone-doctor"&gt;more about Clone Doctor&lt;/a&gt;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Dependency Finder</title>
      <link>https://javatoolbox.com/tools/dependency-finder</link>
      <guid>https://javatoolbox.com/tools/dependency-finder</guid>
      <pubDate>Sun, 02 Jan 2005 05:17:56 GMT</pubDate>
      <description>&lt;p&gt;Suite of tools for analyzing compiled Java code.
&lt;br /&gt;At the core of Dependency Finder is a dependency analysis application that extracts dependency graphs and mines them for useful information. This application comes in many forms, including command-line tools, a Swing-based application, a web application ready to be deployed in an application server, and a set of Ant tasks.
&lt;br /&gt;Dependency Finder has a powerful querying mechanism based on Perl regular expressions.&lt;/p&gt;&lt;p&gt;&lt;a href="https://javatoolbox.com/tools/dependency-finder"&gt;more about Dependency Finder&lt;/a&gt;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>