Conduct Software and Upgrade Management

Use

To specify how to conduct upgrades and any routine or urgent changes in the software, such as support packages and change requests

Prerequisites

Strategy for software and upgrade management defined

Procedure

Major upgrades:

1.       Define an upgrade path for all the software components involved in the solution landscape.

2.       Check release compatibilities and dependencies between the individual components.

3.       Determine a time window for the upgrade (a time frame is sufficient).

4.       Check that the hardware is sufficient for the upgrade.

5.       Design an upgrade path across your system landscape.

-         First, perform the upgrade on the development system.

-         Then perform it on the quality assurance system.

-         Finally, upgrade the production system.

6.       Test the upgrade procedure on the quality assurance system with real data.

7.       Check that the software parameters are set correctly.

Routine software changes:

1.       Test the software changes in the quality assurance system under live conditions.

-         At least three systems are needed: development, quality assurance and production.

-         Copy production data at regular intervals to the quality assurance system.

2.       Ensure that dependent software changes are made in the correct order.

3.       Ensure that the changes in one component do not have a negative impact on another component (for example, by changing the software at an interface).

4.       Ensure that software changes are properly released (use the double-check principle).

5.       Define a time window during which software changes are allowed (primarily for the production system).

Urgent software changes:

1.       Ensure that the software is properly released.

2.       If necessary, bypass the testing on the quality assurance system.

3.       Ensure the change is applied in all the systems.

Result

Software change procedures specified