Software Change Requests                                            

Effective November 1, 2008, all agency Software Change Requests (SCRs) must be submitted with the forms below or the request will be returned. The forms will only be accepted from an authorized agency official. Request should be sent to the Project Control Office.

• Software Change Request Form
• SCR Strategic Value Assessment

Additional Information for Completing an SCR

An SCR should include in as much detail as necessary to understand the desired result.

• The reason the change is needed (Law, regulation, functionality problem, technology change)
• A description of the desired result of the change
• Sufficient technical details
  • entry or reporting system/application that will reflect results of the change
  • data involved
  • calculations
  • validation rules
  • regulation, Executive Order, Legislation, OPM Letter
  • NOAC/Authorities, if relevant
  • special security requirements
  • test data to verify correctness of implementation

The following list suggests the type of information to be included for common types of requests. Not all SCRs of each type of request will require all of the suggested information, and some will require information that is not listed.

• Change to an exiting Screen, report, data file - application and screen name or report name, names of elements to be added, changed, or removed; description of or list of values to be added, changed or deleted; sample data; attachment of marked up screen print or report; calculation; validation rules
• Play plan/personnel processing - citation of applicable law or regulation; calculations and validation rules; table(s) of values; classification of positions covered; grade structures covered; number of employees involved; timing of change
• New Functionality - complete description of desired functionality; description of data; value lists/tables; data flows, reports; calculations; validation rules; file formats for transmitted files
• Special Processing - pay periods involved; number of individuals affected, list/description of data elements to be changed; identity of transmitted files to be changed; precise description of change or desired result; special timing of required