IEC Certification Kit

Polyspace Bug FinderTM

ISO 26262 Tool Qualification Package
R2015b

How to Contact MathWorks

Latest news:

www.mathworks.com

Sales and services:

www.mathworks.com/sales_and_services

User community:

www.mathworks.com/matlabcentral

Technical support:

www.mathworks.com/support/contact_us

Phone:

508-647-7000

The MathWorks, Inc.

3 Apple Hill Drive
Natick, MA 01760-2098
IEC Certification Kit: Polyspace Bug Finder ISO 26262 Tool Qualification Package

COPYRIGHT 20132015 by The MathWorks, Inc.

The software described in this document is furnished under a license agreement. The software may be used or copied only under
the terms of the license agreement. No part of this manual may be photocopied or reproduced in any form without prior written
consent from The MathWorks, Inc.
FEDERAL ACQUISITION: This provision applies to all acquisitions of the Program and Documentation by, for, or through the
federal government of the United States. By accepting delivery of the Program or Documentation, the government hereby agrees
that this software or documentation qualifies as commercial computer software or commercial computer software documentation
as such terms are used or defined in FAR 12.212, DFARS Part 227.72, and DFARS 252.227-7014. Accordingly, the terms and
conditions of this Agreement and only those rights specified in this Agreement, shall pertain to and govern the use, modification,
reproduction, release, performance, display, and disclosure of the Program and Documentation by the federal government (or
other entity acquiring for or through the federal government)and shall supersede any conflicting contractual terms or conditions.
If this License fails to meet the governments needs or is inconsistent in any respect with federal procurement law, the
government agrees to return the Program and Documentation, unused, to The MathWorks, Inc.
Trademarks
MATLAB and Simulink are registered trademarks of The MathWorks, Inc. See www.mathworks.com/trademarks for a
list of additional trademarks. Other product or brand names may be trademarks or registered trademarks of their respective
holders.
Patents
MathWorks products are protected by one or more U.S. patents. Please see www.mathworks.com/patents for more
information.

Revision History
September 2013
March 2014
October 2014
March 2015
September 2015

New for Version 3.2 (Applies to Release 2013b)

Revised for Version 3.3 (Applies to Release 2014a)
Revised for Version 3.4 (Applies to Release 2014b)
Revised for Version 3.5 (Applies to Release 2015a)
Revised for IEC Certification Kit Version 3.6 (Applies to Release 2015b)

Contents
1 Introduction ...................................................................................................................................... 1-1
1.1 Item / Element Identification .................................................................................................. 1-2
1.2 Tool Overview and Identification ........................................................................................... 1-3
1.3 Tool Interfaces ........................................................................................................................ 1-3
1.3.1
Tool Inputs ................................................................................................................ 1-3
1.3.2
Tool Outputs ............................................................................................................. 1-4
1.4 Tool Qualification Artifacts Summary .................................................................................... 1-5
2 Software Tool Criteria Evaluation Report ....................................................................................... 2-1
2.1 Tool Environment ................................................................................................................... 2-2
2.2 Tool Configuration.................................................................................................................. 2-3
2.3 Tool Use Cases and Reference Workflow .............................................................................. 2-4
[PBF_UC1] Static analysis of C/C++ code to assess compliance with coding standards ....... 2-4
[PBF_UC2] Static analysis of C/C++ code to determine code size and complexity metrics .. 2-4
[PBF_UC3] Determination of software quality metrics .......................................................... 2-4
[PBF_UC4] Static analysis of C/C++ code to assess interface between components ............. 2-5
[PBF_UC5] Static analysis of C/C++ code to detect systematic and potential software defects
................................................................................................................................................ 2-5
2.4 Generic Tool Classification .................................................................................................... 2-6
2.4.1
Potential Malfunctions or Erroneous Output ............................................................ 2-7
[PBF_E1] Standards compliance analysis false negative ..................................................... 2-7
[PBF_E2] Standards compliance analysis false positive ..................................................... 2-7
[PBF_E3] Complexity metrics analysis incorrect metrics value .......................................... 2-7
[PBF_E4] Quality metrics reporting incorrect metrics value ............................................... 2-7
[PBF_E5] Non interference .................................................................................................... 2-7
[PBF_E6] Usage of incorrect input data ................................................................................. 2-7
[PBF_E7] Misinterpretation of results .................................................................................... 2-7
[PBF_E8] Incorrect tool usage ................................................................................................ 2-7
[PBF_E9] Incorrect or modified tool installation.................................................................... 2-8
[PBF_E10] Incorrect operational environment ....................................................................... 2-8
2.4.2
Error Prevention and Detection Measures ................................................................ 2-8
[M1] Preceding or Subsequent Dynamic Verification (Testing) of the Software ................... 2-8
[M2] Specified Procedure for Corrective Action on Failure of Source Code Analysis .......... 2-8
[M_MISC1] Revision Control and Configuration Management to Identify the Artifacts to be
Analyzed; Use of Checksums ................................................................................................. 2-8
[M_MISC2] Competency of the Project Team ....................................................................... 2-9
[M_MISC3] Adherence to Installation Instructions; Integrity of Tool Installation ................ 2-9
[M_MISC4] Analysis of Available Bug Report Information .................................................. 2-9
Tool Classification Summary................................................................................................ 2-10
3 Software Tool Qualification Report ................................................................................................. 3-1
3.1 Requirement for Tool Qualification ........................................................................................ 3-2

3.2 Tool Qualification Documentation ......................................................................................... 3-3

4 Confirmation Review of Tool Classification and Qualification ....................................................... 4-1
4.1 Requirement for Confirmation Review ................................................................................... 4-2
4.2 Validity of Generic Tool Classification .................................................................................. 4-3
4.3 Validity of Generic Tool Qualification ................................................................................... 4-4
4.4 Conformance with Reference Workflow ................................................................................ 4-5

vi

1 Introduction
This document constitutes the ISO 26262 Tool Qualification Package for the Polyspace Bug
Finder product. This document is intended for use in the ISO 26262 tool classification and
qualification process for software tools. It contains templates for the ISO 26262 tool
qualification work products (see ISO 26262-8, Clause 11).
The applicant shall review this template for applicability to the application under consideration,
and tailor and complete the information.
See also:

IEC Certification Kit: Users Guide, R2015b

ISO 26262-8, Clause 11

ISO 26262-8, Clause 11 provides provisions for software tools that are used to tailor activities or
tasks required by ISO 26262. The standard outlines a two-step approach to establish the required
confidence in such tools:
Tool classification determines the required level of confidence in the software tool.
Depending on the result of the tool classification, you might need to carry out a formal
tool qualification.
The following work products need to be created when applying this approach to a software tool
(see ISO 26262-8, 11.5):

A software tool criteria evaluation report documenting the tool classification.

A software tool qualification report documenting the tool qualification, if required.

Note The applicant needs to review this template for applicability to the project under
consideration and insert missing information.

1.1 Item / Element Identification

Applicant:

<Company name>

Item/element under development:

<Item or element to be analyzed using Polyspace Bug Finder>

1-2

1.2 Tool Overview and Identification

Polyspace Bug Finder supports the detection of MISRA C:2004, MISRA C:2012, MISRA
C++:2008, and JSF++ coding standard violations in embedded software written in the C and
C++ programming languages.
The product also generates code size and complexity metrics and produces reports that you can
use to monitor and help improve code reliability and quality.
Polyspace Bug Finder can be used on handwritten code, generated code, or a combination of
the two.
Software Tool
Polyspace Bug Finder

Version (Release)
Version 2.0 (R2015b)

IEC Certification Kit

Version 3.6 (R2015b)

Tool Vendor
The MathWorks, Inc.
3 Apple Hill Drive
Natick, MA, 01760-2098
USA

1.3 Tool Interfaces

Polyspace Bug Finder uses the tool inputs and creates the tool outputs listed in the following
sections.

1.3.1 Tool Inputs

C source code (e.g. .c and .h files) or C++ source code (e.g. .cpp and .hpp files) to be
analyzed
Polyspace configuration and project information (.psprj and .ppm files)1
Analysis results provided by Polyspace Bug Finder

Note

Depending on the actual use case(s), some of the tool inputs may not be applicable.

Configuration and project information is being shared between Polyspace Bug Finder and Polyspace
Code Prover.

1-3

1.3.2 Tool Outputs

Code analysis results with coding standard violations (MISRA-C-summaryreport.xml, MISRA-CPP-summary-report.xml, or JSF-summaryreport.xml)
Code metrics results (Code_Metrics.xml)
Software quality metrics results displayed in Web Dashboard or exported via Polyspace
GUI (.html, .pdf, .rtf, .docx, or .xml file)

Note

Depending on the actual use case(s), some of the tool inputs may not be applicable.

1-4

1.4 Tool Qualification Artifacts Summary

The following table lists:

Prerequisites (see ISO 26262-8, 11.3.1)

Supporting information (see ISO 26262-8, 11.3.2)
Tool qualification work products (see ISO 26262-8, 11.5)

for Polyspace Bug Finder. The table also maps these tool qualification artifacts to sections in
this document and artifacts found elsewhere.
Tool Certification Artifact
Safety plan

Corresponding Documents / Artifacts

<Document title, version, and filename / link>

Applicable prerequisites of the <Applicable software lifecycle phase(s)>

lifecycle phases where software <Phase-specific prerequisite(s)>
tool is used
Predetermined maximum ASIL < ASIL>
Software tool documentation

Polyspace Bug Finder Getting Started Guide

R2015b
bugfinder_gs.pdf
Polyspace Bug Finder Users Guide
R2015b
bugfinder_ug.pdf
Polyspace Bug Finder Reference
R2015b
bugfinder_ref.pdf

Environment and constraints of

the software tool

Polyspace Bug Finder Release Notes

R2015b
rn.pdf
MathWorks bug report system at
www.mathworks.com/support/bugreports/
< Additional information if applicable >

1-5

Tool Certification Artifact

Corresponding Documents / Artifacts
Software tool criteria evaluation Customized and completed section Software Tool Criteria Evaluation
report
Report of Polyspace Bug Finder ISO 26262 Tool Qualification
Package (this document)
certkitiec_bugfinder_tqp.docx
Polyspace Bug Finder Reference Workflow
R2015b
certkitiec_bugfinder_workflow.docx
Certificate Z10 13 06 67052 012
June 2013
certkitiec_bugfinder_certificate.pdf
Report to the Certificate Z10 13 06 67052 012
May 2015
certkitiec_bugfinder_certreport.pdf
Software tool qualification
report

Customized and completed section Software Tool Qualification

Report in the Polyspace Bug Finder ISO 26262 Tool Qualification
Package (this document)
certkitiec_bugfinder_tqp.docx
Customized and completed Polyspace Bug Finder Conformance
Demonstration Template
certkitiec_bugfinder_cdt.docx
Certificate Z10 13 06 67052 012
June 2013
certkitiec_bugfinder_certificate.pdf
Report to the Certificate Z10 13 06 67052 012
May 2015
certkitiec_bugfinder_certreport.pdf

Confirmation review of
qualification of a software tool

Customized and completed section Confirmation Review of Tool

Classification and Qualification of Polyspace Bug Finder ISO 26262
Tool Qualification Package (this document)
certkitiec_bugfinder_tqp.docx

1-6

2 Software Tool Criteria Evaluation

Report

2.1 Tool Environment

It is assumed that Polyspace Bug Finder will be used in the following environment when
analyzing C/C++ code for the item / element under consideration (see ISO 26262-8, 11.4.4.1d):
<Insert operating system and other pertinent environment information>

2-2

2.2 Tool Configuration

It is assumed that Polyspace Bug Finder will be used with the following configuration settings
when analyzing C/C++ code for the item / element under consideration (see ISO 26262-8,
11.4.4.1b):
Analysis Option
Language

Setting
<Insert C or C++>

Target & Compiler pane

<Insert configuration parameter names>

<Insert application-specific settings>

Multitasking pane
<Insert configuration parameter names>

<Insert application-specific settings>

Coding Rules pane

<Insert configuration parameter names>

<Insert application-specific setting>

Bug Finder Analysis pane

<Insert configuration parameter names>

<Insert application-specific setting>

Post Verification pane

<Insert configuration parameter names>

<Insert application-specific setting>

Reporting pane
<Insert configuration parameter names>

<Insert application-specific setting>

Distributed Computing pane

<Insert configuration parameter names>

<Insert application-specific setting>

2-3

2.3 Tool Use Cases and Reference Workflow

It is assumed that Polyspace Bug Finder will be used as described by one or more of the
following use cases (see ISO 26262-8, 11.4.4.1c). Details about these use cases are documented
in Polyspace Bug Finder Reference Workflow.
Additional information about the assumed usage of Polyspace Bug Finder can be found in the
reference workflow document Polyspace Bug Finder Reference Workflow.

[PBF_UC1] Static analysis of C/C++ code to assess

compliance with coding standards
The Polyspace Bug Finder tool is used to statically analyze C or C++ source code to assess
compliance with coding standards such as:

MISRA-C, MISRA AC AGC

MISRA C++
JSF ++

Coding standard compliance analysis can be applied to handwritten as well as generated source
code.

[PBF_UC2] Static analysis of C/C++ code to determine

code size and complexity metrics
The Polyspace Bug Finder tool is used to determine size and complexity metrics for C or C++
source code, including:

Comment density of a source file

Cyclomatic complexity
Number of lines, parameters, call levels, etc. in a function

Size and complexity metrics can be determined for handwritten as well as generated source
code. For more information about determining size and complexity metrics, see the Polyspace
Bug Finder Users Guide, R2015b.

[PBF_UC3] Determination of software quality metrics

The Polyspace Bug Finder tool is used to define, determine, and report quality metrics for C or
C++ source code, including thresholds for coding rules, code metrics and reports. The reports

2-4

are based on analysis and verification results provided by Polyspace Code Prover and Polyspace
Bug Finder.
Software quality metrics can be applied to handwritten as well as generated source code.

[PBF_UC4] Static analysis of C/C++ code to assess

interface between components
The Polyspace Bug Finder tool is used to detect interface errors between components.
Polyspace Bug Finder provides the following information:

Function-call with an incorrect number of arguments.

Function-call with an incorrect type of argument.

This analysis can be applied to handwritten and generated source code.

[PBF_UC5] Static analysis of C/C++ code to detect

systematic and potential software defects
The Polyspace Bug Finder tool is used to provide static code analysis to detect overflow, divideby-zero, out-of-bounds array access, and other defects in the source code.
This verification uses formal-methods based on abstract interpretation techniques. It can be
applied to handwritten as well as generated source code.

2-5

2.4 Generic Tool Classification

The tool classification for Polyspace Bug Finder was performed in a generic manner,
independently from the development of a particular safety-related item or element.
For the generic tool classification, the reference use cases listed in the section Tool Use Cases
and Reference Workflow have been taken into account. The tool classification is based on the
potential malfunctions or erroneous outputs and error prevention and detection measures listed
in the corresponding sections below.
Additional information about the assumed error prevention and detection measures can be found
in the reference workflow document Polyspace Bug Finder Reference Workflow.

2-6

2.4.1 Potential Malfunctions or Erroneous Output

The following potential malfunctions or erroneous outputs were taken into account as part of the
tool classification process:

[PBF_E1] Standards compliance analysis false negative

Standards compliance analysis incorrectly marks software as compliant

[PBF_E2] Standards compliance analysis false positive

Standards compliance analysis incorrectly marks software as non-compliant

[PBF_E3] Complexity metrics analysis incorrect metrics value

Polyspace Bug Finder computes an incorrect value for a given size or complexity metrics

[PBF_E4] Quality metrics reporting incorrect metrics value

Polyspace Bug Finder computes an incorrect value for a software quality metrics or fails to
report the violation of a defined software quality goal.

[PBF_E5] Non interference

Polyspace Bug Finder analysis contains an error, but software to be analyzed does not invoke
the erroneous portion of the tool

[PBF_E6] Usage of incorrect input data

Analysis of incorrect or inconsistent tool inputs 2

[PBF_E7] Misinterpretation of results

User interprets Polyspace Bug Finder analysis results incorrectly

[PBF_E8] Incorrect tool usage

User does not follow recommended procedures when using Polyspace Bug Finder analysis

For example, analysis of the wrong source code files

2-7

[PBF_E9] Incorrect or modified tool installation

Polyspace Bug Finder has not been installed correctly, has been modified after installation or
available bug reports for the tool havent been analyzed.

[PBF_E10] Incorrect operational environment

Polyspace Bug Finder is not been used in the intended operational environment, or available bug
reports for the tool havent been analyzed.

2.4.2 Error Prevention and Detection Measures

The following measures to detect potential malfunctions or erroneous outputs were taken into
account as part of the tool classification process. Additional considerations are discussed in the
Additional Considerations section of the reference workflow document Polyspace Bug Finder
Reference Workflow.

[M1] Preceding or Subsequent Dynamic Verification (Testing) of the

Software
Before or after verifying or analyzing the source code with Polyspace Bug Finder:

Dynamically verify (test) the executable code corresponding to the C or C++ source
code.

[M2] Specified Procedure for Corrective Action on Failure of Source

Code Analysis
After verifying or analyzing the source code with Polyspace Bug Finder:

Analyze the identified issues using a defined procedure for corrective action.

The procedure for corrective action includes manual analysis and review of the issues
uncovered.

[M_MISC1] Revision Control and Configuration Management to Identify

the Artifacts to be Analyzed; Use of Checksums
Apply configuration management to the artifacts to be verified or analyzed using Polyspace Bug
Finder.

2-8

[M_MISC2] Competency of the Project Team

Those carrying out verification or analysis activities using Polyspace Bug Finder shall be
competent for the activities undertaken.

[M_MISC3] Adherence to Installation Instructions; Integrity of Tool

Installation
Adhere to the installation instructions for Polyspace Bug Finder (including dependent tools) and
verify the version and integrity of the tool.
Validate modifications or additions made to the shipping product(s), if applicable.

[M_MISC4] Analysis of Available Bug Report Information

Assess and analyze bug report information for Polyspace Bug Finder provided by MathWorks
and comply with the recommendations and workarounds, if applicable.

2-9

Tool Classification Summary

Potential
Use cases TI
malfunction or
erroneous output
[PBF_E1]
[PBF_UC1] TI2
Standards compliance [PBF_UC4]
analysis false
negative

Justification Prevention /
for TI
detection
measures
Incorrect
[M1]
verification
Preceding or
result could
subsequent
prevent coding dynamic
standard
verification
violations
(testing) of the
from being
software
detected

[PBF_E2]
[PBF_UC1] TI1
Standards compliance [PBF_UC4]
analysis false
positive

Software does
not violate
coding
standard rules

[PBF_E3]
Complexity metrics
analysis incorrect
metrics value

[PBF_UC2] TI2

TD

Justification for TD

TD2

MISRA-C and other coding

TCL2
standards checker typically detect
only a subset of the existing
MISRA-C violations in the
software. Therefore, other process
steps cannot assume completeness
of MISRA-C analysis results.
MISRA-C or other coding
standard violations do not
necessarily imply incorrect
software. Not every rule applies to
automatically generated code.
Functional or structural testing
help detect real software errors.
The likelihood of detecting these
errors by testing is considered to
be medium.
Procedure for corrective action
TCL1
includes manual analysis and
review of the issues uncovered.
This process will detect false
positives.

[M2]
TD1
Specified
procedure for
corrective action on
failure of source
code analysis
Complexity
[M1]
TD1
metrics could Preceding or
prevent the
subsequent
detection and dynamic
mitigation of verification
overly
(testing) of the
complex code. software
Code with
high
complexity is
more difficult
to test and has
a higher
likelihood of
error.

TCL

Static and dynamic verification

based on requirements detect
software errors.

2-10

TCL1

Potential
malfunction or
erroneous output
[PBF_E4]
Quality metrics
reporting incorrect
metrics value

Use cases TI

[PBF_E5]
Non interference

[PBF_UC1, TI1
PBF_UC2,
PBF_UC3,
PBF_UC4,
PBF_UC5]
[PBF_UC1, TI2
PBF_UC2,
PBF_UC3,
PBF_UC4,
PBF_UC5]

[PBF_E6]
Usage of incorrect
input data

[PBF_UC3] TI2

[PBF_E7]
Misinterpretation of
results

[PBF_UC1, TI2
PBF_UC2,
PBF_UC3,
PBF_UC4,
PBF_UC5]

[PBF_E8]
Incorrect tool usage

[PBF_UC1, TI2
PBF_UC2,
PBF_UC3,
PBF_UC4,
PBF_UC5]

Justification Prevention /
for TI
detection
measures
Incorrect
[M3]
value for
Check of the
quality metrics underlying analysis
could prevent results for critical
a software
issues
problem from [M2] Specified
being detected procedure for
and analyzed corrective action on
failure of source
code analysis
Error in the
tool does not
impact
analysis
results
Incorrect or
[M_MISC1]
incomplete
Revision control
analysis
and configuration
results could management to
prevent errors identify the
from being
artifacts to be
detected
analyzed; Use of
checksums
Misinterpre- [M_MISC2]
tation of
Competency of the
analysis
project team
results could
prevent errors
from being
detected
Incorrect
[M_MISC2]
usage could
Competency of the
prevent errors project team
from being
detected

TD

Justification for TD

TD1

Quality metrics reports aggregate TCL1

analysis results provided by
Polyspace Bug Finder. Reviewing
the aggregated results does not
replace an analysis of the
underlying analysis results.
Checking the underlying results
for critical issues will reveal
software problems that are
incorrectly aggregated.
TCL1

TD1

TCL

TD1

Revision control and configuration TCL1

management maintains the
integrity of the artifacts to be
verified. Using checksums allows
the unique identification the
artifacts being analyzed.

TD1

Training of users can prevent

these issues.

TCL1

TD1

Training of users can prevent

these issues.

TCL1

2-11

Potential
malfunction or
erroneous output
[PBF_E9]
Incorrect or modified
tool installation

Use cases TI

[PBF_E10]
Incorrect operational
environment

[PBF_UC1, TI2
PBF_UC2,
PBF_UC3,
PBF_UC4,
PBF_UC5]

[PBF_UC1, TI2
PBF_UC2,
PBF_UC3,
PBF_UC4,
PBF_UC5]

Justification Prevention /
TD
for TI
detection
measures
Incorrect or
[M_MISC3]
TD1
modified
Adherence to
installation
Installation
could prevent Instructions;
errors from
Integrity of Tool
being detected Installation
[M_MISC4]
Analysis of
available bug report
information
Incorrect
[M_MISC3]
TD1
operation
Adherence to
could prevent Installation
errors from
Instructions;
being detected Integrity of Tool
Installation
[M_MISC4]
Analysis of
available bug report
information

Justification for TD

TCL

Verification of the installed tool

version will prevent these issues.

TCL1

Adherence to installation guide

instructions will provide a
seamless installation

TCL1

There is a possibility that a safety requirement can be violated if Polyspace Bug Finder is
malfunctioning or producing erroneous output. According to the preceding analysis, the
maximum tool impact (TI) of the use cases taken into account for Polyspace Bug Finder is TI2.
According to the preceding analysis, the maximum required tool confidence level (TCL) for
Polyspace Bug Finder is TCLMAX2.
TV SD reviewed the generic tool classification and confirmed the results in Report to the
Certificate Z10 13 06 67052 012.

2-12

3 Software Tool Qualification Report

3.1 Requirement for Tool Qualification

Given the maximum required tool confidence level TCLMAX2 (see Generic Tool
Classification), Polyspace Bug Finder needs to be qualified up to TCL2. Additional tool
qualification methods appropriate for the predetermined maximum ASIL for the application
under consideration are necessary, according to ISO 26262-8, clause 11.4.6.1. Permissible tool
qualification methods for TCL2 are listed in ISO 26262-8 Table 5.

3-2

3.2 Tool Qualification Documentation

MathWorks carried out an application-independent prequalification of the Polyspace Bug
Finder. The Polyspace Bug Finder was prequalified for all ASILs according to ISO 26262-8 (for
TCL1, TCL2).
The prequalification for the Polyspace Bug Finder was carried out using a combination of the
following methods:

Evaluation of the tool development process (ISO 26262-8, Table 5, Method 1b).
Validation of the software tool (ISO 26262-8, Table 5, Method 1c).

According to ISO 26262-8, Table 5, these two methods are permissible for all ASILs.
For TCL2, method 1b is highly recommended for ASILs A, B, and C. Method 1c is highly
recommended for ASIL D.
TV SD carried out an independent tool qualification assessment. MathWorks submitted the
results of the methods applied to prequalify the Polyspace Bug Finder to TV SD.
TV SD reviewed the generic tool qualification artifacts for Polyspace Bug Finder and
confirmed the results in Report to the Certificate Z10 13 06 67052 012.
Tool qualification for the Polyspace Bug Finder can be claimed for TCL1 and TCL2 by
referencing the certification report and corresponding certificate.

3-3

3-4

4 Confirmation Review of Tool

Classification and Qualification

4.1 Requirement for Confirmation Review

The tool classification (see "Software Tool Criteria Evaluation Report) was carried out
independently from the development of the application under consideration. Therefore, the
resulting, predetermined tool confidence level shall be confirmed by the applicant prior to
Polyspace Bug Finder being used for the development of a particular safety-related item or
element for the application under consideration (see ISO 26262-8, 11.4.2, 11.4.10).
The tool qualification (see "Software Tool Qualification Report) was carried out independently
from the development of the application under consideration. Therefore, the resulting, generic
prequalification shall be confirmed by the applicant prior to Polyspace Bug Finder being used
for the development of a particular safety-related item or element for the application under
consideration (see ISO 26262-8, 11.4.2, 11.4.10).

4-2

4.2 Validity of Generic Tool Classification

Applicable Tool Confidence Level: < Insert TCL>
<Results of confirmation review or reference to confirmation review documentation>

4-3

4.3 Validity of Generic Tool Qualification

Applicable Tool Confidence Level: < Insert TCL>
<Results of confirmation review or reference to confirmation review documentation>

4-4

4.4 Conformance with Reference Workflow

Applicable Tool Confidence Level: < Insert TCL>
<Reference to completed Polyspace Bug Finder Conformance Demonstration Template>
<Statement regarding conformance with reference workflow>

4-5