Show TOC

Background documentationPhases in Quality Gate Management

Features

Quality gate management scenarios have the following four phases:

  1. During the Scope phase, you plan the tasks that are required to complete the scenario. In this phase, you also verify the system landscape and the technical prerequisites of the systems for a scenario.

    In the Scope phase, you carry out the following activities:

    • You document the functional or technical design.

    • You document the requirements of individual departments.

    • You evaluate the technical viability of a scenario.

    The Scope phase begins at the quality gate Start of Scope.

  2. The Build phase refers to the actual development process. In all of the systems used in the scenario, you create the necessary transport requests, which are attached to the software development objects. The transports are imported into the follow-on systems together to ensure that functions remain stable if the transport requests are interdependent.

    The Build phase begins at the quality gate Scope to Build.

  3. In the Test phase, new developments and Customizing settings are imported and activated in the test systems. The quality assurance team completes any test cases that have been created (for example, integration and user acceptance testing). If the test cases identify errors, the necessary corrections must be made in the development systems. The changes are then assigned to new transports, which are imported to the test system.

    The Test phase begins at the quality gate Build to Test.

  4. Only the entire scenario, including all changes and corrections, can be imported during the Deploy phase. This process ensures that all transport requests for a scenario are imported into the production system in full and in the correct sequence. The Deploy phase, also know as “go-live”, is the last phase of the scenario.

    The Deploy phase begins at the quality gate Test to Deploy.

    Note Note

    When you work with a QGM scenario, you can create change cycles. In this case, instead of having the End of Deployment quality gate, you have a quality gate called Deploy to Scope. The End of Deployment quality gate is not applicable until there are no more change cycles. For more information, see Change Cycles.

    End of the note.