Welcome » IT Booklets » Development and Acquisition » Maintenance » Emergency Modifications
Emergency modifications are periodically needed to correct
software problems or restore processing operations quickly.
Although the changes must be completed quickly, they should also be
implemented in a well-controlled manner.
Emergency change standards should include procedures similar to
those for routine change controls. However, the standards should
include abbreviated change request, evaluation, and approval
procedures to ensure changes are made quickly. The standards should
be designed to ensure management completes detailed evaluations and
documentation of emergency changes as soon as possible after
Whenever possible, emergency changes should be tested prior to
implementation. If management is unable to thoroughly test
emergency modifications before installation, it is critical that
they appropriately backup files and programs and have established
back-out procedures in place.
Appropriate backups, established back-out procedures, and
detailed documentation enhance management's ability to reverse
changes if they cause system disruptions. Detailed documentation
also enhances management's ability to analyze the impact of any
changes during post-change evaluations. At a minimum, emergency
change procedures should require: