January 16, 2012

Performance verification plan - E-6

Describe verification activities by the end requirements elaboration

A. Scope

The Performance Verification Plan (PVP) presents an overview of the verification process implemented by the Supplier to meet Customer requirements.

It assumes that the status of readiness is high and is therefore produced at the end of the pending product specification phase.

It reassures the Customer that each requirement has been analysed by the Supplier in terms of verification activities: who performs it ? When ? How ? etc.

It therefore proposes a global verification strategy incorporating the Customer's programme and technical objectives.

B. Fundamentals

The Performance Verification Plan is drawn up by the Supplier at the end of phase B, prior to the switch to phases C/D.

Its content is discussed with the Customer to ensure:

  • that the Supplier correctly takes into account Customer requirements ("just what is required"),
  • the Customer is kept in the loop regarding verifications performed by the Supplier ("just what is necessary").


The provisions specified in the PVP guarantee adherence to the following objectives.

1. Presenting the verification process to the Customer

The Supplier proposes its vision of verification activities in this document, focusing on technical content and organisation.

This is essentially established on the basis of Customer specifications, on its Development Plan (Model policy, planning, etc.) (see M-4), and any specific drawbacks recorded in Statement Of Work, a MOU, etc. (e.g. organisation of subcontracting, partnership).

In this way, the Customer will ensure the maturity of the Supplier with regards to management of the preparation of verification activities that will ultimately lead to product qualification.

2. Preparing verification activities at Supplier sites

With regards to verification activities that have been approved by both parties, their definition in the PVP will allow the Supplier to assess the optimum scope of activities to be performed: the overall volume, the skills and facilities to be implemented and, more generally, to schedule phase C and D activities.

Remark: for small-scale projects, the PVP and the AIT Plan (see E-10) may be combined in a single "AIV Plan".

C. Typical content

1. Subject

This chapter describes the objectives, content and implementation of the PVP.

It briefly describes the purpose of the verification process and, in particular, hypotheses and constraints regarding verification activities.

2. Applicable and reference documents

This chapter identifies the applicable and reference documents related to project verification activities.

It lists, in particular, the applicable verification documents and their content.

3. Definitions and abbreviations

This chapter lists the applicable dictionaries or glossaries and gives the definition of specific terms and abbreviations used in the PVP.

4. Project verification strategy

This chapter describes the verification concepts retained for the project and provides the definition of the principles retained to perform the relevant activities (methods, levels and phases).

4.1 Models policy

The PVP presents the templates selected for the project in its Models policy and the associated product matrix.

4.2 Verification strategy

The PVP describes the selected combination of different verification methods (analysis, simulation, inspection, tests, etc.) for each type or set of requirements (including software).

4.3 Presenting the verification programme

The PVP documents verification activities and the associated schedule throughout phases C and D.

The analysis, design review, inspection and test programmes are detailed on specific activity sheets or referenced in the AIT plan.

4.4 Provisional verification matrix

A requirement is verified by several verification activities. It is therefore necessary to indicate the traceability between verification tasks and requirements applicable to the project.

The provisional verification matrix presents the nature of each scheduled verification task, the relevant project phase(s), the template(s) applied, the entity responsible for the activity, the facilities required and the expected results, for each requirement applicable to the project.


RisksNon-obtainment of functional performance
Non-resistance to the environment
 RecommandationsDEFINE THE PRODUCT
Definition File
Status reports
Verification Matrix
Justification File
Assembly, Integration and Test drawing
Integration Procedure
Test Procedure and Report


Activities / documentation

Published in: