Static analysis IBM Rational Software Analyzer, Part 3. Enhancing rules for Java code review

Creating severity indicators, templates, user Help, generic variables, and configurable parameters

From the developerWorks archives

Steve Gutz

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

This is the third article in a four-part series about IBM Rational Software Analyzer and its related capabilities in Rational Application Developer and Rational Software Architect. It walks you through the process of creating your own custom rules and Rule Sets and using other advanced capabilities that extend Java code review.

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 that enables software developers to easily use automated code review and structural analysis in their daily 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.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Rational, DevOps
ArticleID=302460
ArticleTitle=Static analysis IBM Rational Software Analyzer: Part 3. Enhancing rules for Java code review
publish-date=04292008