Information Technology Reference
In-Depth Information
Table 8.2
Documents and responsibilities
Functional Specifications
Business Units
Technical Specifications
Development
Documents for Acceptance Tests
Acceptance Management
Test Scripts
Business Units
System Documentation
Supplier
Acceptance management has to make sure that these documents are provided in
time and released accordingly within the usual versioning and clearance process.
8.4 Versioning and Releasing
For documents, which do not have operative relevance (such as the problem
repository or the acceptance declaration), but contain basic information, a
versioning process should be established. The coding systematic could be as
follows:
x, y with
• x: version number and
• y: indication of release status.
The release status can be coded as follows:
• 0: draft
• 1: in consultation
• 2: released.
Additional fine tuning is possible.
During the consultation process comments and amendments from different
participants will be solicited to be integrated into the follow-up versions. This
total history will be kept in a table at the end of a document (Template see
Sect.
8.5
) such that the evolution of a document can be traced back later. It is
quite possible that controversies arise about the most recent valid status when
mistakes have been made during releasing and distribution. The history is a sure
instrument to clarify these problems.
8.5 Templates
The following templates are useful: release history (Table
8.3
), list of work
supporting tables (Table
8.4
):
