Static analysis IBM Rational Software Analyzer, Part 2. Creating rules and rule filters to extend Java code review

From the developerWorks archives

Steve Gutz

Date archived: May 17, 2017 | First published: April 29, 2008

This is the second article in a four-part series about IBM Rational Software Analyzer and its related capabilities in IBM Rational Application Developer and IBM Rational Software Architect. It focuses on using the Java code review capabilities for analyzing your code and walks you through the process of creating rules and filters.

IBM® Rational® Software Analyzer encourages and simplifies the process of automated code quality improvements. It was initially designed as an API and user interface to create and integrate static analysis tools into other Rational products, such as Rational Application Developer and Rational Software Architect. It has evolved into a complete, standalone offering for automated code review and structural analysis in the daily software development process.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some content, steps, or illustrations may have changed.

Zone=Rational, DevOps
ArticleTitle=Static analysis IBM Rational Software Analyzer: Part 2. Creating rules and rule filters to extend Java code review