Quick code review

The Quick code review includes three categories of rules: J2EE Best Practices, J2SE Best Practices, and Performance.

Purpose

The Quick code review applies a set of rules that have the problem severity level. This code review checks code for the most serious problems that should be addressed first. The name refers to the fact that this analysis offers a quick way to discover the most problematic parts of the code; it does not have as a goal quick execution time.

Rule categories

The following table lists all of the categories and subcategories in the Quick code review, along with a description of the rules in each one. In the left column, categories are in bold text and subcategories are in plain text.

Category or subcategory Description
J2EE Best Practices Contains rules based on the best J2EE development practices and supports Web projects targeted to WebSphere® servers
Garbage Collection Contains rules to detect method invocations that can delay garbage collection
Maintainability Contains rules to detect code that may be hard to maintain in J2EE applications
Performance and Scalability Contains rules to detect method invocations that hinder the performance or limit the scalability of a J2EE application
J2SE Best Practices Contains rules that validate code for compliance with J2SE best practices for Java™ development
AWT Contains rules that detect issues related to using the Abstract Window Toolkit library
Cloneable Contains rules that detect issues related to object cloning
Comparison Contains rules that detect issues related to comparing objects and testing object equality
Null Contains rules that detect issues related to using null
Portability Contains rules that detect issues related to portability
Serialization Contains rules that detect issues related to serialization
Threads Contains rules that detect issues related to using threads
Performance Contains rules that enforce suggestions for improving performance and reducing the memory footprint in Java applications
Memory Contains rules that detect performance issues related to memory usage

Sample rule

The following rule is a sample one that is applied in the Quick code review. It is in the Naming Conventions category, in the Conflicts subcategory:
Avoid multiple overloaded methods with the same number of parameters
Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.