VDA volume 2 - Annex 6 / Software Test Report

Sender: Date of issue:

Software Test Report

Recipient:

Appendix to the PPA report

Part No.1): Drawing and geometry status (ZGS):

Company Dept. Name Telephone Signature

Produced by:

Approved by2):

Software description3) :

This software replaces the following part nos.:

Reason for the software test report

Main release
Change release
Repeat release (Bugfix)

Changes compared to previous software4):

Configuration details5):
Part No. Hardware version Software version Diagnosis ident. Security class

Order No.

Hardware part no. YY/WW YY/WW_Patchlevel

Software part no. 1 YY/WW_Patchlevel

Software part no. 2 YY/WW_Patchlevel

Software part no. 3 YY/WW_Patchlevel

Software part no.4 YY/WW_Patchlevel

Release:

Date Signature

© VDA QMC all rights reserved

This download is part of the VDA volume 2 and so are terms of the page 3 of the publication also mandatory.

Page 1 of 4
Part No.

ZGS:
Software Test Report
Appendix to PPA report

Sheet 2 : Tests completed

General hardware and software details
Microcontroller 1. 2. 3.

Microcontroller frequency 1. 2. 3.

Quartz frequency 1. 2. 3.

Operating system

Memory capacity utilization

Component Used Available Used [%] Specified Status

ROM
RAM
EEPROM
Hard disk

Compatibility6)
On which hardware (part no.) if is possible to flash the HW Version HW Version HW Version HW Version HW Version HW Version
software (part no.)?

Function tests7)
Tested according to test specification

All test sequences successful? Yes No

Which test sequence was not successful? 1)

2)

3)

4)

5)

6)

Which measure have been defined?

When is the next bugfixing release?

Signature

Page 2 of 4
Part No.

ZGS:
Software Test Report
Appendix to PPA report

Sheet 3 : Confirmation of software tests

Herewith we confirm the performance of the following tests and the correctness of their results:

Software integration test

Performed yes no
Version xxxxxxxx
Result successful not successful
Number of points outstanding xxxxxxxx

Module test
Performed yes no
Version xxxxxxxx
Result successful not successful
Number of points outstanding xxxxxxxx

System integration test

Performed yes no
Version xxxxxxxx
Result successful not successful
Number of points outstanding xxxxxxxx

Software in the loop (SIL)

Performed yes no
Version xxxxxxxx
Result successful not successful
Number of points outstanding xxxxxxxx

Acceptance test
Completed yes no
Version xxxxxxxx
Result successful not successful
Number of points outstanding xxxxxxxx

Approval:

Date Signature

Page 3 of 4
 Software Test Report
Sheet 4: Notes

This test report must be appended as related document with the PPAP for components containing software. In the case that only software is
presented this software test report replaces the sample card for the relevant part number. In this case the term Software includes Flashware
(programs and data) and associated diagnostic data (Diogenes data).
1)
In the case that only the software is presented, the part number must be documented in this field. If hardware is presented with software
the order number must be documented.
2)
The "2 pairs of eyes principle" is used during approval to ensure an unbiased examination of the software. This means that the signatory
must not have been involved in the development of the tested part number, however he may be a department or team colleague as long as
he works on other projects.
3)
All open and not realized features from the specification under designation the specification version have to be stated.The sponsor of the
changes has to be named.
4)
In this field all modifications and their effects on external interfaces must be designated.
5)
If several software part numbers (software modules) are entered in the configuration matrix it is important to state the individual SW part
numbers in the sequence in which they must be considered in the flash sequence.
6)
All hardware variants able to be flashed have to be stated including hardware part number and hardware version. It is vital that only these
hardware part numbers are listed that have been tested under these Software conditions.
7)
The valid test specification must be mentioned which was used to verify the functional requirements. Test sequences which did not pass
must be mentioned with measures. In addition the date of the next bugfix release is to be noted.

Page 4 of 4