|ENGINEERING CHANGE ORDER
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 engineering change order (ECO) is completed when a change request has been approved for a baselined SCI. The ECO is a mini-requirements specification for the change.
1.0 SCI Identification
This section identifies the SCI(s) for which a change will be made.
- 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.
2.0 Description of the change to be made
This section presents a brief description of the change.
- 2.1 Description of SCI(s) affected
This section discusses 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 user 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 Analysis and design modifications
A description of the analysis and design modifications that will be required.
- 3.1 Description of analysis model modifications
Changes required to the analysis model are described. Data, function and behavior models are all considered.
3.2 Description of design model modifications
Changes required to the design model are described. Data, architectural, interface and component-level models are all considered.
4.0 Validation requirements
A description of the SQA activities and testing approach required to ensure that the change has been made without side effects.
Return to APM Documents