Modifications to System Software

Purpose

To define procedures for modifying corporate system software.

Scope

All modifications to system software.

Standard

All system software modifications must adhere to University of Houston-defined policies and procedures regarding their development, testing, and implementation.

Guidelines
  1. System software modification implementation--The system programmer applying changes to system software must have an approved backout plan, in case there are problems encountered during the implementation of the changes.
  2. Separate test environment for system software programs--System software modifications/exits should be made to test versions of the software libraries. The test environment shall have a reasonable set of activities performed within it, in order to validate the integrity of the new environment.
  3. Emergency modifications directly to the production system software--All modifications directly to the production system software libraries shall require the approval of the system programmer's direct line manager. After the emergency is past, documentation shall be developed to reflect the changes made to the affected system software.