8.3.1 QA Plan (QPl)

  QS-Plan

Contents		Introduction Document Index Document Structure Links to the V-Model Mailinglist

Introduction

Document Index

Document Structure

1. General Information

2. Desired Quality and Risks in the Project

2. 1. Quality Goals for Products and Processes

2. 2. Quality Risks

2. 3. Measures Based on Quality Goals and Risks

3. QA Measures according to Criticality and IT Security

3. 1. Applied Rules or Standards

• Definition of criticality and its levels
  The definition contained in the V-Model that might be adapted with regard to the actual project must be used as basis. In accordance with the customer, it is possible to select a definition of appropriate existing standards (e. g. /RTCA-178B/); in this connection, any specifications possibly set down in the Project Manual already have to be taken into consideration.
  The criticality of the System, the defined fields, and the structure elements they are based on are specified in the User Requirements. The criticality classification of the function units Segment and SW Unit or HW Unit is realized in the Technical Requirements. The classifications of the criticality level for the functional units SW Component and SW Module are defined in the Software Architecture.
• Definition of IT security-relevant levels as well as setting up evaluation levels and the required strength of IT security mechanisms
  In this connection, reference is normally made to a published criteria catalogue, and the project-specific interpretation of the corresponding regulations is realized.

3. 2. QA Measures based on Classifications

With regard to criticality, this is defined with the help of a criticality/methods matrix consisting of two submatrices: one matrix for constructive (specifications with respect to generation) QA methods and one matrix for analytical (specifications with respect to assessment) QA methods. Examples for both of these matrices can be found in Part 3 Collection of Manuals of the V-Model (Safety and Criticality manual).

For every criticality level, the constructive QA methods agreed will be set up in the matrix for constructive QA methods. According to the definition in this matrix, the activities of the submodel SD (in special cases also the other submodels) have to be carried out.

For every criticality level, the analytical QA methods agreed will be set up in the matrix for analytical QA methods. According to the definition in this matrix, the products generated by the submodels system development, quality assurance, configuration management, and project management will have to be assessed.

Depending on the IT security-relevant levels, requirements must be covered by QA; they can be found in the corresponding criteria catalogue and have already been listed in the Project Manual. These requirements and the resulting QA measures are specified with regard to the actual project.

4. Quality Assurance during Development

4. 1. Products to be Assessed

4. 2. Activities to be Assessed

5. Special Control Measures

5. 1. Entry Control of Off-the-Shelf Products

1. purchased software, e. g. library programs, test monitor, operating systems, compilers, tools,
2. usable software that has been developed in the same company, but not within the current project.

• off-the-shelf products integrated into the functionality of the System, and
• off-the-shelf products used for the development process.

• to guarantee the identification of manufacturer and product,
• to check if the documentation is available according to the project guidelines,
• to check if sufficient quality assurance measures have been carried out and if (and in which cases) this has yet to be done.

5. 2. Controlling Subcontractors

• the size of the documentation and
• the development standards

The control measures for the subcontractors must also be defined:

• accompanying assessment of the development
• acceptance control for developed products
• specifications for the internal subcontractor assessments

5. 3. Software Item Exit Control

5. 4. Change Control

5. 5. Controlling Working Responsibilities

5. 6. Controlling the Configuration Management

Note: The CM Plan describes the respective procedures, e. g. backup of results and archivation; the QA Plan, however, describes the corresponding control measures, e. g. for the proper backup of results.

Links to the V-Model Mailinglist

This page online  •  GDPA Online  •  Last Updated 06.Mar.2003 by C. Freericks