evaluate polyspace code prover results against software quality objectives -凯发k8网页登录

evaluate polyspace code prover results against software quality objectives

instead of evaluating all results of a code prover analysis, you can first define a set of criteria that the analyzed project must meet and compare the code prover results against those criteria. the software quality objectives or sqos are a set of thresholds against which you can compare your verification results. you can develop a review process based on the software quality objectives. in your review process, you consider only those results that cause your project to fail a certain sqo level.

you can use a predefined sqo levels or define your own. to customize sqo levels, see .

specifications of sqo levels

following are the quality thresholds specified by each predefined sqo.

metric	threshold value
comment density of a file	20
number of paths through a function	80
number of `goto` statements	0
cyclomatic complexity	10
number of calling functions	5
number of calls	7
number of parameters per function	5
number of instructions per function	50
number of call levels in a function	4
number of `return` statements in a function	1
language scope, an indicator of the cost of maintaining or changing functions. calculated as follows: (n1 n2) / (n1 n2) `n1` — number of different operators `n1` — total number of operators `n2` — number of different operands `n2` — total number of operands	4
number of recursions	0
number of direct recursions	0
number of unjustified violations of the following misra c™:2004 rules: 5.2 8.11, 8.12 11.2, 11.3 12.12 13.3, 13.4, 13.5 14.4, 14.7 16.1, 16.2, 16.7 17.3, 17.4, 17.5, 17.6 18.4 20.4	0
number of unjustified violations of the following misra c:2012 rules: 8.8, 8.11, and 8.13 11.1, 11.2, 11.4, 11.5, 11.6, and 11.7 14.1 and 14.2 15.1, 15.2, 15.3, and 15.5 17.1 and 17.2 18.3, 18.4, 18.5, and 18.6 19.2 21.3	0
number of unjustified violations of the following misra™ c rules: 2-10-2 3-1-3, 3-3-2, 3-9-3 5-0-15, 5-0-18, 5-0-19, 5-2-8, 5-2-9 6-2-2, 6-5-1, 6-5-2, 6-5-3, 6-5-4, 6-6-1, 6-6-2, 6-6-4, 6-6-5 7-5-1, 7-5-2, 7-5-4 8-4-1 9-5-1 10-1-2, 10-1-3, 10-3-1, 10-3-2, 10-3-3 15-0-3, 15-1-3, 15-3-3, 15-3-5, 15-3-6, 15-3-7, 15-4-1, 15-5-1, 15-5-2 18-4-1	0

metric	threshold value
number of unjustified red checks	0
number of unjustified and checks	0

metric	threshold value
number of unjustified gray `unreachable code` checks	0

metric	threshold value
percentage of justified orange checks, calculated as the number of green and justified orange checks divided by the total number of green and orange checks.	: 50
: 60
: 80
: 50
: 80
: 60
: 80
: 80
: 60
: 60
: 50
: 50
: 80
: 60
: 80
: 60

metric	threshold value
number of unjustified violations of the following misra c:2004 rules: 6.3 8.7 9.2, 9.3 10.3, 10.5 11.1, 11.5 12.1, 12.2, 12.5, 12.6, 12.9, 12.10 13.1, 13.2, 13.6 14.8, 14.10 15.3 16.3, 16.8, 16.9 19.4, 19.9, 19.10, 19.11, 19.12 20.3	0
number of unjustified violations of the following misra c:2012 rules: 11.8 12.1 and 12.3 13.2 and 13.4 14.4 15.6 and 15.7 16.4 and 16.5 17.4 20.4, 20.6, 20.7, 20.9, and 20.11	0
number of unjustified violations of the following misra c rules: 3-4-1, 3-9-2 4-5-1 5-0-1, 5-0-2, 5-0-7, 5-0-8, 5-0-9, 5-0-10, 5-0-13, 5-2-1, 5-2-2, 5-2-7, 5-2-11, 5-3-3, 5-2-5, 5-2-6, 5-3-2, 5-18-1 6-2-1, 6-3-1, 6-4-2, 6-4-6, 6-5-3 8-4-3, 8-4-4, 8-5-2, 8-5-3 11-0-1 12-1-1, 12-8-2 16-0-5, 16-0-6, 16-0-7, 16-2-2, 16-3-1	0
percentage of justified orange checks, calculated as the number of green and justified orange checks divided by the total number of green and orange checks.	: 70
: 80
: 90
: 70
: 90
: 70
: 90
: 90
: 70
: 70
: 70
: 70
: 90
: 80
: 90
: 80

metric	threshold value
percentage of justified orange checks, calculated as the number of green and justified orange checks divided by the total number of green and orange checks.	: 90
: 100
: 100
: 90
: 100
: 80
: 100
: 100
: 80
: 80
: 90
: 90
: 100
: 100
: 100
: 100

metric	threshold value
number of unjustified misra c and misra c coding rule violations	0
number of unjustified red checks	0
number of unjustified and checks	0
number of unjustified gray `unreachable code` checks	0
percentage of justified orange checks, calculated as the number of green and justified orange checks divided by the total number of green and orange checks.	100

for information on the rationales behind these levels, see .

compare verification results against software quality objectives

you can compare your verification results against sqos either in the polyspace^® access web interface or the polyspace desktop user interface.

in the polyspace access web interface, you can first determine whether your project fails to attain a certain quality objective threshold by looking at the quality objectives card on the project overview dashboard.
the card shows the percentage of results that you have already fixed or justified in order to attain the threshold. click the number of remaining findings to open those findings in the results list. for a more detailed view of the quality of your code against all quality objectives thresholds, open the quality objectives dashboard. for more information, see the .
you can also generated reports that show the pass or fail status using the templates softwarequalityobjectives_summary and softwarequalityobjectives. see bug finder and code prover report (-report-template).
in the polyspace user interface, you can use the menu in the results list toolbar to display only those results that you must fix or justify to attain a certain software quality objective.

to activate the sqo options in this menu, select tools > preferences. on the review scope tab, select include quality objectives scope.

note

you cannot use the menu in the user interface to suppress red or gray checks. therefore, you cannot directly compare your project against predefined sqo levels 1, 2 and 3 in the polyspace user interface. however, in the polyspace access web interface, you can compare your project against all predefined sqo levels.

customize sqo levels

to customize sqos:

in the polyspace access web interface, see .
in the polyspace desktop user interface, review scopes are used to implement sqos. see how to create your own review scopes in one of these topics:

evaluate polyspace code prover results against software quality objectives -凯发k8网页登录