Main Content

Prioritize Check Review in Polyspace Access Web Interface

This example shows how to prioritize your check review. Try the following approach. You can also develop your own procedure for organizing your orange check review.

Tip

For easier review, run Polyspace® Bug Finder™ on your source code first. Once you address the defects that Polyspace Bug Finder finds, run Polyspace Code Prover™ on your code.

Before beginning your check review, you can check the following:

  • See the Run Log by going to Window > Run Log in the Review view. Use CTRL-F to search the log for warning and error messages, or the string failed compilation. If there are warnings or errors, or files failed to compile, identify why Polyspace could not analyze all of your source files.

    To check for some common Reasons for Unchecked Code, see the documentation for Polyspace Code Prover.

  • See if you have used the right configuration. The configuration options are listed in the Run Log under the strings Options used with Verifier: and User:.

    Sometimes, especially if you are switching between multiple configurations, you can accidentally use the wrong configuration for the verification.

  1. From the Project Overview dashboard, click the number next to Open on the Run-time Checks card.

    This action opens the Results List pane with only unreviewed red, gray and orange checks. You can also filter for these results from the toolstrip in the Review view by clicking Run-time Checks and To Do.

  2. Select and review the first check.

    For more information, see Interpret Code Prover Results in Polyspace Access Web Interface.

    Continue going through the list until you have reviewed all of the checks.

  3. Before reviewing orange checks, review red and gray checks.

  4. Prioritize your orange check review by:

    • For easier review, begin your orange check review from files with fewer orange checks.

      To sort files by number of orange checks, in the Details section of the Run-time Checks dashboard, click View by File, then click the head of the Orange column to sort it. Click an entry from this column to open the corresponding list of orange checks.

    • Check type: Review orange checks in the following order. Checks are more difficult to review as you go down this order.

      Review OrderChecks
      First
      Second
      ThirdRemaining checks

    • Orange check sources: Review all orange checks caused by a single variable or function. Orange checks often arise from variables whose values cannot be determined from the code or functions that are not defined.

      To review the sources of orange checks, select an orange check from the Results List pane then click in the Results Details pane. You can also open the Orange Sources pane by going to Window > Orange Sources. For more information, see Filter Using Orange Sources.

    • Result details: Review all results that originate from the same cause. Sometimes, the Detail column on the Results List pane shows additional information about a result. For instance, if multiple issues trigger the same coding rule violation, this column shows the issue. Click the column header so that results that originate from the same type of issue are grouped together. Review the results in one go.

  5. To see what percentage of checks you have justified, go to the Dashboard view and see the Summary section of the Run-time Checks dashboard.

Related Topics