Change Proposal Template

A Change Proposal is used by the project team and client organization to initiate enhancements and modifications to system requirements, design specifications, and software that are part of an existing Configuration Management baseline. Directions for completing this form appear following Page 2 of the form.

CHANGE PROPOSAL (CP)Page 1 ORIGINATOR NAME & PHONE #:

DATE: ____/____/____CP IDENTIFICATION #:_____________ FUNCTIONAL AREA(S):

[ ] [ ]

[ ] [ ]

[ ] [ ]

[ ] [ ]

[ ] [ ]

[ ] [ ]CLASS 1

CLASS 2

(Requires Approval)DOCUMENTATION[ ]

SOFTWARE[ ]CONFIGURATION ITEM(S)

AFFECTED:DESCRIPTION OF CHANGE:

IN OPERATIONAL BASELINE:

[ ] YES [ ] NOANALYSISDATE REVIEWED:____/____/____EFFECT ON CONFIGURATION ITEM SPECIFICATIONS:

IMPACT ON OTHER ITEM(S):

ALTERNATIVE SOLUTION(S):

(cont.)

CHANGE PROPOSAL (CP)Page 2 DEVELOPMENT REQUIREMENTS:

PROCESS MANAGEMENTRECOMMENDATION:SIGNATURE: CLASS 2 [ ] APPROVEDATE:____/____/____ [ ] APPROVE WITH MODIFICATION (EXPLANATION BELOW) [ ] DISAPPROVE (EXPLANATION BELOW) [ ] FURTHER ANALYSIS REQUIRED (EXPLANATION BELOW)EXPLANATION:DATE ASSIGNED TO IMPLEMENT CHANGE:____/____/____DATE VERIFICATION OF CHANGES COMPLETED ____/____/____

SIGNATURE: FINAL APPROVALREVIEW OF MODIFIED DOCUMENTATION/SOFTWARE:SIGNATURE: [ ] APPROVEDATE: ____/____/____ [ ] DISAPPROVE (EXPLANATION BELOW)EXPLANATION:IMPLEMENTATIONDATE IMPLEMENTED: ____/____/____ RELEASE NOTICE: SIGNATURE:

INSTRUCTIONS FOR COMPLETING CHANGE PROPOSAL (CP)Originator Name &

Phone NumberCompleted by Originator. Name and telephone number of person submitting request.DateCompleted by Originator. Date Change Proposal was submitted to Configuration Management.CP Identification #Completed by Configuration Management. Unique identification number assigned from Change Proposal Log.Functional

Area(s)Completed by Originator. Indicate functional area(s) (for example, component, subsystem) of product affected by the change.Class 1/Class 2Completed by Configuration Management. Check appropriate box to indicate Class 1 or Class 2 change request. Class 1 changes are enhancement, modifications, or defect corrections that are considered minor in scope and do not require Process Management approval. Class 2 changes require Process Management approval.Documentation/

SoftwareCompleted by Originator. Check appropriate box(es) to indicate if change request is for documentation, software, or both.Configuration Item(s)

AffectedCompleted by Originator. List all configuration items that are impacted by the change (documentation and software).Description of

ChangeCompleted by Originator. Provide a detailed description of the requested enhancements or modifications.In Operational

BaselineCompleted by Originator. Check appropriate box to indicate if change request is for documentation or software that is currently in production.ANALYSISCompleted by Person Performing AnalysisDate ReviewedIndicate date the Change Proposal analysis was completed.Effect on Configuration Item SpecificationsIdentify, by configuration item, all changes that must be made to accommodate the request.(continued on next page)

INSTRUCTIONS FOR COMPLETING CHANGE PROPOSAL (cont.)Impact on Other ItemsIdentify, by configuration item, all changes that must be made to accommodate the request.Alternative Solution(s)Indicate any options or alternative means by which the change request can be implemented.Development RequirementsProvide a detailed description of development requirements (e.g., people, time, resources) required to implement the changes.PROCESS MANAGEMENTCompleted by Process Management ChairmanRecommendationCheck the appropriate box to indicate the Process Management decision to indicate approval, approval with modification, disapproval of the request, or if further analysis is required. Provide an explanation for modification and disapprovals. Process Management chairman or designate signs and dates the form.Date Assigned to Implement ChangeDate that the Change Proposal was submitted to the organization responsible for implementing the change(s)Date Verification of Changes CompletedCompleted by Verification Organization. Date that the modified software was tested and verified as meeting all functional specifications and/or documentation was reviewed for accuracy and completeness.FINAL APPROVALCompleted by Process Management Chairman

Review of Modified Documentation/Software

Check the appropriate box to indicate the Process Management decision either to approve or disapprove the modifications. Provide an explanation for disapprovals. Process Management Chairman or designate signs and dates the form.IMPLEMENTATIONCompleted by Configuration ManagementDate ImplementedDate modifications implemented (new baseline established) and Change Proposal closedRelease NoticeIf Change Proposal affects operational baseline, the number of the Release Notice that transmits change(s) to affected partiesSignatureSignature of Configuration Management Chairman