Code Analysis Features of EclipsePro Audit

EclipsePro Audit includes dynamic, extensible tools that detect, report and repair deviations or non-compliance with predefined coding standards and style conventions. These tools form a key portion of Continuous Collaborative Code Analysis (C3A).

Catch 800+ Audit Violations (see categories at lower right) Manual & Dynamic Code Auditing Batch/Ant/Headless Code Auditing Generate Management Reports Multiple Report Formats (HTML, XML, CSV) QuickFix 350+ Violations Audit Explorer View Audit Series Editor Customize Audit Rules Keyword Audit Rule Search Define Multiple Audit Rule Sets Create New Audit Rules Audit Rule Creation Wizard Locally Disable Audit Rules Assign Project-Level Defaults Inclusion & Exclusion Filters Analyze & Repair Javadoc Integrated Collaboration Server Rational Code Review Integration For full documentation of code analysis features, see that section of the product documentation »	Audit Rule Categories
	Coding Style Comments Dead Code Eclipse Plugins Exceptions Formatting Import Usage Inheritance Internationalization J2EE (EJB, JSP, Portlets & Servlets) Javadoc Conventions JDBC Usage JUnit Usage Logging (JCL, log4j)	Modifier Usage Naming Conventions Performance Portability Possible Errors Potential Refactorings Program Complexity Property Files Security Semantic Errors Spell Checking Threading UI Specific XML Files

About Continuous Collaborative Code Analysis (C3A)

Continuous Collaborative Code Analysis (C3A) aids developers in finding and fixing problems in their code earlier in the development process. EclipsePro Audit is like an automated, personal, real-time code review. It happens either continuously (as code is written) or on-demand (when the developer chooses to activate it).

It begins with a powerful set of audit rules — code standards and quality metrics, based on industry standards, company standards, and/or accepted best practices. EclipsePro Audit includes 800+ Audit Rules; it also lets you create new rules and customize existing rules.A lead developer can automatically distribute and enforce chosen rule sets across a team.

EclipsePro Audit's powerful "quick fix" capability automatically offers a corrective fix. Many problems are corrected totally automatically, long before the code is turned over to your QA group.

A less obvious, but very important, benefit of EclipsePro Audit is that it teaches developers to write better code. Whether in Bangor or Bangalore, developers universally are very smart people who quickly internalize advice that leads to increased quality.

Read more About Continuous Collaborative Code Analysis (C3A)