Checklist for Preliminary QA Plan (qE1)



 

 

 

 

 

 

 

 

 

 

 

1 Introduction

1.1 Purpose of the document
The preliminary QA plan summarizes all the known Q requirements and QA requirements of the client, defines the process model which is to be used for the project which is to be initiated, and uses this information to derive all necessary QA measures (documents to be drawn up, type and scope of reviews, tests, etc.) which need to be planned in greater detail. This will provide a basis for a preliminary estimation of the effort involved.

Formulation proposal:
The purpose of this preliminary QA plan is to summarize the Q and QA requirements specified for project <xyz> and to define the process model which is to be applied to the project. The QA measures which the plan shows to be necessary are outlined below.

1.2 Validity of the document
The document is essentially limited in scope to the initiation phase, with the QA information known up until that point, and is used in conjunction with the proposed solution and preliminary project plan as a basis for the project decision report.

1.3 Definitions of terms and abbreviations
Where necessary, this section must be used to define all important terms and abbreviations occurring in this document. These include, first and foremost, terms which have different meanings at the PSE to those used by the client.

Example:

Q Quality
QA Quality Assurance

1.4 Relationship with other documents
How is this document related to other internal and external documents?

Examples of interesting references to internal documents:

  • Project organization (preliminary project plan)
  • Additional QA requirements (e.g. for a superordinate project or the business unit; QA process manual, QA manual)

Examples of references to important external documents:

  • Documents relating to calls for tender
  • Standards to be complied with
  • Other QA requirements of the client (e.g. any QA process manual or QA manual which is available).
2 Process model

This section must be used to enter the process model which is to be used for the project. If the client does not request a specific process model, an existing instance of SEM must be selected in every case. No specification is required in case of provision of personnel.

3 Quality requirements of the client

Quality requirements are requirements made on the product (the result of the project). This section must specify all quality requirements so far known of the envisaged client.

Typical quality requirements include the availability of a program, reliability, time behavior, consumption behavior, maintainability, portability and all aspects relating to user friendliness or usability.

4 Quality assurance requirements of the client

QA requirements are requirements made on the project (the course of the project). This section must specify all of the client’s known requirements which are relevant for handling the project (e.g. from the documentation relating to the call for tender). These must also be examined to determine whether they are critical and risk-related or whether they will have any effect on the effort.

Typical quality assurance requirements include:

  • Attaining a specific test coverage
  • Conducting official safety certification for safety-relevant software (with all the certification obligations this brings with it)
  • Requirements relating to code reviews in the form of intensive inspections for specific program sections
  • Test records for performing stand-alone tests
  • Inclusion of the client into the procedure for reviewing specific documents.
5 Quality assurance measures required

This section is intended to summarize the consequences of the process model, the Q requirements and QA requirements: Which QA measures need to be planned and implemented in this project?

At this moment, it is not yet necessary to plan all project QA measures in detail, but rather to produce a list of the necessary measures in order that this can be used as a basis for a preliminary estimation of the effort which these measures will require.


Siemens AG Österreich, Program and Systems Engineering PSE
Contact: stdSEM Webmaster
Last modified: 08/27/98 15:41
Copyright © Siemens AG Österreich 1997. All rights reserved.