|SOFTWARE CHANGE REQUEST
Change request, change report and engineering change order are generated as part of the configuration control activity within the SCM process. These documents are often represented as printed or electronic forms. The outline that follows is intended to provide an indication of the content of each. The actual structure of this SCM information may vary depending on its implementation.
The change document is completed whenever a formal request for change of a base lined SCI is requested.
1.0 SCI Identification
This section identifies the SCI for which a change has been requested.
1.1 Name, identification and description of SCI(s)
The name, version/control numbers of the SCI is specified, including page numbers if a document is involved. A brief description is provided.
The name of the person requesting the change
1.3 Contact information
How to contact the requester.
1.4 Date, location, and time
When and where the change was requested
2.0 Description of the change
This section presents a brief description of the requested change
This section presents a detailed description of the circumstances that precipitated the change reqest and the request desired.
2.2.1 Underlying circumstances
Background information regarding the request.
Supporting information, e.g., printouts containing an error in a report or an incorrect screen image
2.2.3 The change
A detailed discussion of the change requested.
2.2 Reasons and justification
This section discusses why the change has been requested and the justification for the request.
2.3 Perceived affects
The requester's perception of the affects of the change.
The requester's perception of any alternatives to the change.
2.5 Requester priority
The priority assigned by the requester to the work generally chosen from a five-value scale.
Return to APM Documents