Example of Preliminary QA Plan (qE1)


1 Introduction

1.1 Purpose of the document
This preliminary QA plan summarizes all the Q and QA requirements specified for the BIS project and defines the process model which is to be used. The necessary QA measures resulting from this plan are described in section 5.

1.2 Validity of the document
The preliminary QA plan is valid for the planned revision BIS V1.0. It contains the product requirements made known to Mr. Meister by May 2, 199x.

1.3 Definitions of terms and abbreviations
BIS: Bank Branch Information System
EN ISO 9001: Model for representing the quality assurance system in the Design / Development, Production, Assembly and Customer Service departments
RDBMS: Relational database management system

1.4 Relationship with other documents
The responsibilities are defined in the preliminary project plan.
The legal provisions for payment transactions (e.g. with abroad) apply for all requirements which are not listed explicitly.


2 Process model

The stdSEM process model of PSE will be used for the project.

3 Quality requirements of the client

The primary criteria are the run times for the various functions and the correctness of payment transactions and automatic operation.

The average processing times for manual activities (payment transactions, provision of information, account management) should be reduced considerably from their current levels. The automatic functions are executed outside the bank staff's normal working hours. This period thereby represents a natural run time barrier. The following procedure can be adopted to obtain an adequate criterion for the run time of the automatic functions as a function of the quantity of data to be processed:

Periods involving particularly high work volumes (e.g. monthly, quarterly or annual changes) must be taken as the basis for the anticipated level of data. The anticipated maximum level must be determined for each automatic function. The actual volume of data which needs to be considered is derived from the sum of the maximum levels multiplied by a safety factor of 2.

All data should be managed in a relational database management system (RDBMS) wherever possible. This solution is mandatory for customer and account data.

4 Quality assurance requirements of the client

The client insists on certification to EN ISO 9001, together with the associated documentation requirements and QA documentation.

He explicitly requests:

  • Monthly quality reports which correspond to his normal classification scheme (this is not a problem for us, since the quality reports in our department are similar).
  • Inspection of test records for stand-alone, integration and system tests.
5 Quality assurance measures required

In addition to all measures resulting from the application of the development method, particular attention must be paid to the test documentation and related efforts (so far we have not drawn up records for stand-alone tests). This gives rise to the following provisional QA-related activities and measures:

  • Drawing up of a QA plan, revision of this plan during subsequent project phases
  • Monthly quality reports (clarify with QM whether report to client can fully replace our own internal report)
  • Reviews of development documents (software requirements specification, project plan, QA plan, system specification, detailed design specification, test plan)
  • Estimation of data volume and run time (we require data from the client, a mass test is urgently recommended at the earliest possible date, preferably on a prototype)
  • Code review only for a small number of critical program parts (approx. 20%, selection of parts yet to be clarified!)
  • Conducting of stand-alone, integration and system tests (type of documentation yet to be clarified!)
  • Drawing up of a test report on tests conducted
  • Drawing up of an acceptance report
  • Project review and drawing up of a project experience report

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.