Deliverable D1.4. Project Quality Plan & Procedural Handbook

Abstract

This deliverable represents the first output of task T1.4 “Quality Management and Risk Assessment” of WP1, the project quality plan and procedural handbook. It outlines the strategy how quality management approaches are integrated into work packages and project management. The concept of QM-Measures, supported by practical proven QM-Tools, is introduced and it is described how QM-Measures have to be integrated at the three identified areas for QM:

• SW Engineering tasks

• the project management level

• meetings  

Like all engineering, software engineering is not just about producing products but involves producing products in a cost-effective way. Given unlimited resources, the majority of software problems can probably be solved but the challenge for software engineers is to produce high-quality software within a finite amount of resources and to a predictable schedule. A general assessment of system quality requires the identification of common attributes which we would expect to find in well-engineered software. Assuming the software provides the required functionality, there are four key attributes which a well-engineered software system should possess:

1. Maintainability: As long-time software is subject to regular change, it should be written and documented so that changes can be made without undue costs
2. Reliability: Reliability means that it should perform as expected by users and should not fail more often than specified in the requirements
3. Efficiency: The system should not make wasteful use of system resources such as memory and processor (note: the more you optimize a software the more the software is difficult to change)
4. Appropriate User Interface: Much software is not used to its full potential because its interface makes it difficult to use. The user interface design must be tailored to the capabilities and background of the system users

The list of software products which is error-prone is endlessly, as well as software projects which failed. Here is the point where quality management comes into play. The purpose of quality management in software-engineering is to offer a comprehensive approach whose adherence finally leads to better software according to measured quality attributes and projects which are in time and budget.

The purpose of this document is to describe procedures and rules so that:

The software components produced in SPIKE meet the requirements. The approach is based on the “classical” (and most widely spread and flexible) waterfall model which has a long history in software-engineering. The recommended procedures are also borrowed from the widespread literature.

The project itself is well documented and traceable.

The basic precondition is that all SPIKE partners keep to these procedures which come into effect after the release of this document.

You can download a short version of this document here:

D1.4. Project Quality Plan and Procedural Handbook 

In order to obtain the full content of this document, please use the contact form below: