Information Technology Reference
In-Depth Information
VERSION DESCRIPTION DOCUMENT
Cover Page
Table of Contents
1.0
INTRODUCTION
1.1
Roles and Responsibilities
1.2
Process
2.0
SCOPE
2.1
Identification
2.2
Applicability
2.3
System Overview
2.4
Documentation Overview
2.5
Points of Contact
3.0
REFERENCE DOCUMENTS
4.0
VERSION DESCRIPTION
4.1
Inventory of Materials Released
4.2
Inventories of Software Contents
4.3
Changes Installed
4.4
Interface Compatibility
4.5
Adaptation Data
4.6
Bibliography of References Documents
4.7
Installation Instructions
4.8
Possible Problems and Known Error
4.9
Glossary
Fig. 9.3
Version description document
between features with terms they are familiar with using. It is inevitable that some
jargon may need to be incorporated. In these instances it is best practice to fully
explain the term and then if prudent or possible, by in house standards allow for
indexing the terminology at the end of the document (Fig.
9.3
).
9.4.4 Post-Implementation Review
The review is conducted at the end of the Implementation Phase. A post-
implementation review shall be conducted to ensure that the system functions as
planned and expected; to verify that the system cost is within the estimated amount;
and to verify that the intended benefits are derived as projected. Normally, this shall
be a one-time review that occurs after a major implementation; it may also occur
after a major enhancement to the system. The results of an unacceptable review are
submitted to the System Proponent for its review and follow-up actions. The System
Proponent may decide to return the deficient system to the responsible system
development Project Manager for correction of deficiencies (IRM
2003
) (Fig.
9.4
).
