Information Technology Reference
In-Depth Information
3.3 Responsibilities of Quality Management
Roughly speaking the main responsibility of quality management focuses on
scheduling and managing acceptance tests prior to final delivery of software or
interfaces to be put into operation. All other responsibilities result from input from
other sub-processes or standard practise. The latter are caused by the interplay with
activities either prior to acceptance tests or follow them up as consequences of test
results (as lined out above and to be detailed further down). The overall task of
quality management is facilitated by drafting generally agreed upon acceptance
specifications as part of an implementation project.
As already indicated, quality management initially takes on the role of goods
entry by applying the rules:
1. Ordered goods: technical specifications
2. Delivered goods: software.
Deviations are recorded as errors, before a final decision concerning possible
rejection of the delivery or parts thereof is made.
The responsibilities of ordinary goods entry are exceeded in the sense that
quality management also is responsible to follow up on possible subsequent deli-
veries in the form of amendments and corrections until the original delivery of all
ordered software runs without faults.
The responsibilities in detail comprise the following:
Identification of test requirements
Define personal responsibilities within the framework of acceptance tests
Overall scheduling of acceptance tests together with the supplier
Managing acceptance tests
Final validation and recommendation.
3.3.1
Identification of Test Requirements
According to acceptance of one of the objects
Release
Special functions/individual change requests
Error amendments
Data migration,
the requirements for acceptance tests may vary. To begin with, the following
essential resources have to be considered:
Hardware and system environment, and there again
1. Server environment with the performance required for the tasks at hand,
2. Configuration, including subsystems and utilities necessary for the software
to be tested and to run without faulty configuration parameters,
