Strategies for creating analysis configurations

When you create analysis configurations, use some simple strategies to improve analysis effectiveness and efficiency.
As you start to create and run analysis configurations, you might find that:
The following strategies can help to return a smaller result set.
  1. Select rules from the same rule category and analysis type.

    Different analysis types have different purposes. For example, running Java Architectural Discovery helps you understand code structure and Java Data Flow Analysis helps find resource leaks.

    Results from multiple analysis types can take longer to evaluate and resolve.

    Different rule categories, even from the same analysis type, can also have different analysis objectives. For example, Security and Globalization are both categories in Java Code Review.

  2. Select a small, logically-related set of source files.

    You can run analysis on all the projects in your workbench or on a single project or even a single source file. The larger the set of files that you include in your analysis scope, the larger your result set.

    Although running an analysis on all the projects in your workspace is possible, it can return a massive number of results many of which might not be related to your current project.

    As an alternative, choose a set of files that are logically related, such as the source files in a project.

  3. Run analysis at regular intervals.

    Software Analyzer is integrated in your Eclipse workbench and is easy to access and run against source files and projects at any time.

    Running analysis frequently when you are writing code allows you to find and fix problems at the earliest possible development phase.


Feedback