Application Maintenance

ajaym259General, Resources1 Comment

Application Maintenance consists of the activities to keep an application and its documentation in conformance to existing business and operational requirements. The Application Maintenance does not change (add, modify, or delete) the business functionality provided by the application to the user.

Adaptive Maintenance

Adaptive Maintenance is that portion of Application Maintenance to modify an application and its documentation as necessitated by changes (patches, updates, etc) to the technical environment in which the application operates. Modifications are not made for the purpose of changing user functionality. Each Adaptive Maintenance Request for Change will be estimated as a whole and will not be divided into requests of lesser size.

Technical Environment Change

Technical Environment Change is defined as the work to implement a new patch or release of a COTS package. If the environment is driving the change, it is considered Adaptive Maintenance. Service provider will have to coordinate with the COTS service providers.

The following are examples of Technical Environment Changes:
  1. Change code due to an upgrade to the operating system software
  2. Recompile source code for a newly installed compiler
  3. Reformat data or perform one-time data loads
  4. Move files from one device to another
  5. An upgrade to the Database Management Services
  6. Change code due to an upgrade to existing software used by application

Regulatory Changes

A Regulatory Change is defined as an application modification necessitated by changes in government legislation as affecting Organisation, identified by Organisation and submitted to Service Provider in a Request for Change (RFC).

One Comment on “Application Maintenance”

  1. Pingback: koquest | koquest

Leave a Reply

Your email address will not be published. Required fields are marked *