7 Part 7: V-Modell Reference Mapping to Standards

7.2 Mapping to other Standards

7.2.1 Mapping to AQAP-150

7.2.1.2 Project-related Software Quality Management Activities

AQAP-150 requires from the supplier the planning and execution of effective software quality management activities. Those include both management-related and technical processes for the development of quality software. Starting with the contractual requirements, these processes have to ensure that the requirements can be traced down to software units and the elements of the configuration management system. They also have to guarantee that software quality is both verified and validated and that risk management is carried out. In this process the activities of the software quality system have to be based on standards and procedures in the organization-wide software quality system.

In addition to these general requirements, there are further requirements concerning the following points:

Software Project Quality Plan (SPQP)

AQAP-150 includes the following requirement: "The supplier shall document the software quality management activities as related to the project in a SPQP. The SPQP may be a discrete document or part of another plan that is prepared under the »Contract. The SPQP shall carry the signature of approval of those organizational elements having responsibilities identified in the SPQP, and be placed under configuration control. If stipulated in the contract, the SPQP shall be offered to the purchaser for agreement. Once agreed by the purchaser, the SPQP shall form part of the contract."

Identification and Review of Software Requirements

According to the AQAP, the supplier shall identify and review the software requirements and development constraints, have them approved by the responsible authorities and manage them in the configuration management system. If they are developed by the supplier as part of a system contract, they shall be offered to the purchaser, who may disapprove them, subject to the conditions of the contract.

In the V-Modell the acquirer is responsible for preparing the »Requirements Specification for the system to be developed. These requirements are part of the contract (»Contract (Acquirer)). From this the supplier derives the »Overall System Specification and subsequently refines the requirements step by step. If the system includes software units, a »Software Specification is prepared for them within the framework of the step-by-step refinement. The acquirer may determine in the contract that he is offered the software requirements and that he may disapprove them.

The quality of all requirements is assured by the regulations in the V-Modell.

Management

This part of the AQAP-150 deals with the management of the software project. It combines requirements related to the following topics:

Software development process
Organization
Non-conforming Software
Corrective Action
Subcontractor Management
Software Configuration Management (SCM)
Off-the-Shelf Software
Non-deliverable Software
Quality Records
Documentation Retention
Handling and Storage of Software Media
Replication and Delivery

Software Engineering

For software development and maintenance activities AQAP-150 requires the use of recognized methods, procedures and validated tools

Evaluation, Verification and Validation (EVV)

The supplier has to plan, define and implement a process for the evaluation of software methods, techniques, tools, procedures and activities, a process for the evaluation of software items and products and a process for the provision of follow-up action to ensure that necessary changes are made and for subsequent reverification. This EVV process has to be an integral part of the development process and define the roles, objects, implementation criteria, methods and tools and the documentation to be produced.

Maintenance

If required, the supplier has to plan and implement an approach for planning and carrying out maintenance.

These requirements are met by the V-Modell. When preparing the »Project Manual, however, care must be taken that all objects that have to be subjected to configuration management under AQAP-150 actually are subject to configuration management. Examples of this are the »Project Manual, the »Project Plan and specifications and elements of the »Enabling System. In addition, the »Metrics required in AQAP-150, such as fault statistics and testing efficiency, have to be defined in the »Project Manual. The contractually defined requirements of AQAP-150 have to be met also by the »Sub-Suppliers. This has to be specified therefore accordingly in the topics »Directives for the Project Manual of the Supplier and »Directives for the QA Manual of the Supplier. The V-Modell contains recommendations for methods and tool classes. The selection and evaluation of particular methods/tools, however, has to be made with regard to the specific project or the organization. For the topic »Evaluation of Off-the-Shelf Products the requirements of AQAP-150 have to be taken into account for example with regard to documentation and the rights concerning data protection.