dashboard in polyspace desktop user interface
this topic focuses on the polyspace® desktop user interface. to learn about the equivalent pane in the polyspace access web interface, see dashboard in polyspace access web interface.
the dashboard pane provides statistics on the analysis results in a graphical format.
when you open a results file in polyspace, this pane is displayed by default. you can view the following graphs:
code covered by analysis
from this graph you can obtain the following information:
files: ratio of analyzed files to total number of files. if a file contains a compilation error, polyspace bug finder™ does not analyze the file.
if some of your files were only partially analyzed because of compilation errors, this pane contains a link stating that some files failed to compile. to see the compilation errors, click the link and navigate to the output summary pane.
functions: ratio of analyzed functions to total number of functions in the analyzed files. if the analysis of a function takes longer than a certain threshold value, polyspace bug finder does not analyze the function.
defect distribution by impact
from this pie chart, you can obtain a graphical visualization of the defect distribution by impact. you can find at a glance whether the defects that polyspace bug finder found in your code are low-impact defects. for more information on impact, see .
defect distribution by category or file
from this graph you can obtain the following information.
category | file | |
---|---|---|
top 10 | the ten defect types with the highest number of individual defects.
use this view to organize your check review starting at defect types with more individual defects. | the ten source files with the highest number of defects.
use this view to organize your check review starting at files with more defects. |
bottom 10 | the ten defect types with the lowest number of individual defects. each column on the graph is divided the same way as the top 10 defect types. use this view to organize your check review starting at defect types with fewer individual defects. | the ten source files with the lowest number of defects. each column on the graph is divided the same way as the top 10 files. use this view to organize your check review starting at files with fewer defects. |
coding rule violations by rule or file
for every type of coding rule that you check (misra™, jsf®, or custom), the dashboard contains a graph of the rule violations.
from this graph you can obtain the following information.
category | file | |
---|---|---|
top 10 | the ten rules with the highest number of violations.
use this view to organize your review starting at rules with more violations. | the ten source files containing the highest number of violations.
use this view to organize your review starting at files with more rule violations. |
bottom 10 | the ten rules with the lowest number of violations. each column on the graph is divided in the same way as the top 10 rules. use this view to organize your review starting at rules with fewer violations. | the ten source files containing the lowest number of rule violations. each column on the graph is divided in the same way as the top 10 files. use this view to organize your review starting at files with fewer rule violations. |
other dashboard features
you can also perform the following actions on this pane:
select elements on the graphs to filter results from the results list pane. see .
view the configuration used to obtain the result. select the link configuration.
view the modeling of the multitasking configuration of your code. select the link .