Change Procedures

The typical change procedures that the product manages involve the following activities:

Retrieving elements from production to a development library
Making changes to elements
Adding or updating elements into the test stage
Moving elements to QA
Moving elements back into production

The following illustration shows the typical change procedures in a software life cycle.

Flow diagram of a typical software life cycle.

In this life cycle, new or existing code is developed in the Development library. After the code has been unit tested by the application developer, the code is added to the Test stage for unit testing. When the code is ready for system testing, it is moved to the Quality Assurance stage. Finally, when the code is ready to be used by customers, the code is moved to the Production stage. Any fixes are applied to production code in the Emergency stage.

If your company requires approvals to move your software code changes through the life cycle, you must use packages to perform the moves.

Note: For more information about packages, see the Packages Guide.