|SOFTWARE CHANGE REPORT
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 software change report (SCR) is completed as a consequence of a formal request for change of a baselined SCI. The SCR is completed after the change request has been evaluated by software engineering staff.
1.0 SCI identification
This section identifies the SCI(s) 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 .
The name of the person who has evaluated the change request.
1.4 Contact information
How to contact the requester and the evaluator.
1.5 Date, Location, and time
When and where the change report was generated.
2.0 Evaluation of the change request
This section presents a brief evaluation of the requested change.
2.1 Description of SCI(s)affected
This section discussed the SCIís to be affected by the requested change.
2.2 Change categorization
This section places the change into one or more generic change categories.
2.3 Scope of the change
The evaluator's assessment of the scope of the change including a listing of all SCIís that will be affected and all users who must be informed.
2.3.1 Technical work required
A description of the work required to accomplish the change
2.3.2 Tools/special resources
Required tools or other special resources are noted here.
2.4 Interoperability effects
The impact of the change on other systems.
2.5 Technical risks
The risks associated with making the change are described.
3.0 Cost Assessment
This section presents a cost assessment of the requested change including an estimate of effort and time required.
This section presents the evaluator's recommendation regarding the change, its internal priority, and the ultimate disposition of the request, based on further evaluation by the CCB/CCA.
Should the change be made?
4.2 Internal priority
How important is this change in light of on-going work and other business/product considerations?
Will the change be made, and if so, when?
Return to APM Documents