Objectives - IT Quality Management - page 2

Each chapter with the exception of this introduction and the appendices are
structured in a similar way:
• Introduction
• Problem area
• Organisational solution
• Instruments
• Templates
• Summary of approach.
1.2 Scope
The scope of this topic and some of its guidelines are characterised by two
limitations:
• System relevance and
• Time relevance.
System relevance refers to the complexity and the level of change with regard to
software. Obviously the proposed methods can be applied to any kind of software.
For economical reasons, however, they are less relevant for small and standard
applications.
The time scope normally refers to states of document versions such as an
acceptance directive or some of the documents discussed in Chap. 8 . Each docu-
ment is identified by a version ID referring to the main document. Its validity is
based on the current version, only exceptionally on sections of predecessor ver-
sions. In any case the latest update of a document normally is the valid one. All
changes to any document have to be recorded as a version history until final
clearance.
1.3 Methodologies
The implementation of complex systems will normally be achieved by setting up a
proper project of its own or by using the structure of an already existing project.
There are now a number of methodologies, which can be employed to facilitate the
acceptance procedures. To those belong for example CMMI (Capability Maturity
Model Integration), SPICE (Software Process and Capability Determination) and
ITIL. CMMI helps to judge and improve the quality for product development
processes. This means it precedes proper quality control itself from the perspective
of customers, but also covers initial sections of the overall process chain such as
request management for example. SPICE is a true norm (ISO/IEC 15504), which
initially validates enterprise processes in general, but emphasizes software