Documente Academic
Documente Profesional
Documente Cultură
SCR #: ____________________ REQUIREMENT #:_______________________ CHANGE REQUEST INITIATION: Originator: _________________________________________ Phone#:
(___)_____________________ Date Submitted: ____/____/____ System Name: ______________________________________________ Version Number: _________________
Software: ______
Documentation: ______ Requirement Change: ______ Design Change: ______ Defect: ______ Other: ______
Emergency: ______
CHANGE DESCRIPTION:
Received By: _______________________ Date Received: ___/___/___ Assigned To: _______________________ Date Assigned: ___/___/___ Type of Software Affected: ____________________________________________________________________________________________________ Modules/Screens/Tables/Files Affected: _________________________________________________________________________________________
Documentation Affected:
Requirements Specification System Design Specification System Test Plan Training Plan User System Reference Manual System Maintenance Manual Other (Specify)
Section #
Page #
Date Completed
Initial
_______ _______ _______ _______ _______
___________ ________ ______/______/______ ___________ ________ ______/______/______ _______ ___________ ________ ______/______/______ ___________ ________ ______/______/______ ___________ ________ ______/______/______ ___________ ________ ______/______/______ _______ ___________ ________ ______/______/______
Est. Time
__________
Act. Time
__________
Date Comp.
____/____/____
Remarks
_________________________ ____________
Coding/Testing
__________
__________
Acceptance
__________
__________
___________________________ ___ Total Hours: ________ ________ ____________________ __________ Impact Analysis Needed: APPROVALS: Yes / No
(If yes, include impact on technical performance, resources, schedule, etc.) Change Not Approved: ______ Hold (Future Enhancement): ______
1. Signature ________________________________________________
2. Signature ________________________________________________
DEFINITION
A sequential number beginning with the organizational code (e.g., HR0000194). For requests initiated by the Contractor, a sequential number beginning with the alpha character C (e.g., C0000194). The numbers will be assigned and controlled by configuration management personnel or designees, and tracked by project. Initiators will be notified as to the specific SCR numbers assigned. Number of the requirement to be changed (if known). Note: If the requested change is a new requirement, a specific requirement number may not be assigned or available at the time of the request. Information about the initiator of the change request, and the software/documentation impacts. Originator: Phone #: Date Submitted: System Name: Version Number: Name of person initiating the SCR. Phone number of originator. Date form submitted to DOE or Contractor. Name of system. List full name of system and acronym. Version number of software/documentation to be changed (e.g., V1.0, V2.0, V2.1).
REQUIREMENT #:
CONFIGURATION ITEM:
Configuration item affected. Place a "X" in the appropriate area. Software: Documentation: System component (e.g., operating systems/communications/applications software). System component (e.g., requirements specification/training plan).
CHANGE TYPE:
Type of change being requested. Place a "X" in the appropriate area. Specify other. New Requirement: Requirement Change: Design Change: Other: Requirement was not identified in original specifications. Requirement needs to be altered. Original design needs to be changed. Indicates other than above change types. Specify in the CHANGE DESCRIPTION area.
REASON:
Place a "X" in the appropriate area. Prepare a brief justification identifying the basis for initiating the SCR and the expected benefits. Use the CHANGE DESCRIPTION area of the form if sufficient space is available; otherwise, use an attachment. Assist the appropriate personnel in ranking priorities. Legal: Business: Performance Tuning: Defect: Mandate by changes in Federal and/or State regulations and laws. Mandated change related to DOE business and policy changes. Change(s) required to improve application usability (e.g., improved screen layout, conversions), or platform/operating software performance. A problem with a system/application that requires a change (e.g., program abend, program error).
PRIORITY:
Ranking to identify action or response to an SCR. Place a "X" in the appropriate area. Emergency: Urgent: Routine: Date Required: A change in operational characteristics that, if not accomplished without delay, will impact system operability. A change that, if not accomplished promptly (e.g., prior to the next production cycle), will impact system effectiveness. A change that can be planned, scheduled, and prioritized. The date the change is needed.
CHANGE DESCRIPTION: Detailed functional and/or technical information about the change. Use an attachment, if necessary, to provide adequate detail or supporting documentation (e.g., statement of new requirement). Attachments: If attachments are included, circle "Yes," if not, circle "No." TECHNICAL EVALUATION: To be completed by Contractor. Provides tracking data of technical approach. Received By: Name of person (Contractor) who initially received or originated the SCR. Date Received: Date SCR received by Contractor. Assigned To: Person who is being assigned the responsibility for the technical evaluation. Date Assigned: Date assigned to assignee. Type of Software Identify type(s) of software affected by the change (e.g., operating system software, application software). Also identify all dependent or Affected: subordinate interfacing applications that may be affected by the change. Include name(s) and version number(s) if applicable. If necessary, use the CHANGE DESCRIPTION area or an attachment for additional information. Modules/Screens/ Identify modules/screens/tables/files affected by the change. Include name(s) and version number(s) if applicable. If necessary, use the Tables/Files Affected: CHANGE DESCRIPTION area or an attachment for additional information. Documentation Identify documentation affected by the change. Include section and page number(s). Enter the date completed and the initials Affected: of the author. If necessary, use the CHANGE DESCRIPTION area or an attachment for additional information. TIME ESTIMATES: To be completed by Contractor. Identify the lifecycle stage(s) affected by the change. Post the estimated and actual time required, and date(s) completed. Total the estimated times and provide any remarks. Impact Analysis Needed: If a impact analysis is needed, circle "Yes" and attach to the SCR form; otherwise, circle "No." An impact analysis of the change request should have details on impacts to the Project Plan (i.e., available technical staff, schedule, costs, etc.). APPROVALS: Acquire the approval signatures for authorizing the SCR (e.g., Client - Project Management Officer (PMO), Point of Contact (POC), Contractor - Project Manager (PM)). Select one option by placing a "X" in the appropriate action area: Change Approved, Change Not Approved, or Hold (Future Enhancement). Note: Individuals authorized to approve change requests are identified in the project Configuration Management Plan.