Rational Developer for System z

Overview of running a code review

This topic provides an overview of running a code review

Typically a code review is started by selecting a software analysis configuration from a menu of existing configurations. You can do this in several contexts: from the main toolbar, from a popup menu in the project explorer, from the COBOL, PL/I, or System z® LPEX editor, or from the software analysis configuration editor. See Starting a code review; runtime scope.

When the configuration is selected the Code Review component first determines the scope of the software analysis, that is the source code files to which the rules are to be applied. The scope is set in the software analysis configuration to be either the entire workspace, a resource working set, or selected projects. See Selecting the scope and the rules of a configuration. However, you can override the configured scope when you start the software analysis. See Starting a code review; runtime scope.

During the software analysis the Code Review component applies the rules specified in the software analysis configuration to each source code file in the scope, and records the results.

The results are of two types. The first type is an expandable tree displayed in the Software Analysis Results view in which the results are organized by rule category, rule, source file, and source code line number. Clicking a result in the tree opens the source code file in the editor at the location where the problem was found. See Working with histories and results.

The second type is a highlighting in the source code editor of the lines of code where each problem was found. The editors supporting this highlighting are the COBOL editor, the PL/I editor, and the System z LPEX editor. See Fixing a problem reported in a result.


Feedback