Scope and rules for a software analysis configuration

In a software analysis configuration, the rules define the coding practices to be enforced and the scope defines the files to which the rules apply.

Scope

The scope identifies the source code files to which the software analysis is to be applied. When you run the software analysis configuration, you can override the configured scope with a different scope. For more information about setting the scope at run time, see Running a code review in the IDE.Table 1 shows the values that can be selected:
Table 1. Scope values
Scope selection: Resulting scope:
Analyze entire workspace All the source code files in the workspace.
Analyze a resource working set All the source code files in the selected resource working set.
Analyze selected projects All the source code files in the selected projects.
Note: The projects in this list are filtered according to the settings in the Project Explorer view. To change these settings click Window > Preferences > Modeling > Views > Project Explorer.

Rules

Rules define the specific coding practices that are to be analyzed in a source code file. The meaning of each rule is described the following:

Severity levels

You can assign one of the following severity levels to the rules you select. The severity levels provide guidance for deciding which problems might be fixed and which problems must be fixed.
Icon Severity level Description
Recommendation The lowest severity level. The result indicates a problem that is not serious but one that you might still fix.
Warning This severity level indicates that a resource likely has a problem that you must resolve.
Severe This highest severity level. The result indicates that you must resolve the problem.

Feedback