Documentation - IT Quality Management - page 101

8.2 Completeness and Relevance

Some indications regarding possible sources of documents have already been given
in Chap. 5 .

8.2.1 Completeness

There are documents which have to be ready before the start of acceptance testing
and others which can be supplied afterwards. The first type includes:

• Released functional specifications,
• Released technical specifications,
• Test scripts,
• Protocol of provisioning.

The latter comprise:

• Training documents,
• Process descriptions etc.

Of cause it is desirable that all these documents are provided before the start of
acceptance testing. Sometimes this is not possible because of time constraints. Of
course, those documents being created during the acceptance testing itself (problem
repository, acceptance protocol etc.) cannot be delivered beforehand. The complete
software documentation itself will in any case only be delivered after the provi-
sioning of the software itself.

8.2.2 Relevance

One has to distinguish between technical and legally relevant documents. One
legally relevant document which at the same time serves as a basis for the billing
process is the acceptance declaration with all appendices (acceptance protocol,
amendment schedule). All other documents comprise technical details permitting
acceptance testing in the first place and later operation. Its importance, however,
lies in the fact that the total system documentation is subject to its own proper
acceptance process. More details further down.

8.3 Responsibilities

According to document type specific responsibilities will be allocated

(see Table 8.2 ).