Scope and rules for a software analysis configuration

In a software analysis configuration, the rules define the coding standards to be applied and the scope defines the source code files to be checked.

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, see Running a code review. Table 1 shows the values that can be selected on the Scope tab in the software analysis configuration window.
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

The rules define the coding requirements for the software analysis. The rules are described in the following topics:

Severity levels

You can assign a severity level to each rule. The severity levels can provide guidance to developers as to how to handle violations.
Icon Severity level
Recommendation
Warning
Severe

Feedback