Software Change Management 

Purpose

You use the Software Change Management IT process to manage the consistent and synchronized flow of object changes in a distributed system environment between different software stages, such as Development, Consolidation, and Production. To enable this, SAP NetWeaver Development Infrastructure helps you to set up a distributed landscape for your custom development project.

Prerequisites

You have installed a system with usage type Development Infrastructure (DI).

Process Flow

...

       1.      Your administrator designs your software architecture, for example with Microsoft Visio.

       2.      In System Landscape Directory (SLD – part of usage type AS-Java), your administrator defines your software components.

       3.      In Change Management Service (CMS) of the Development Infrastructure, your administrator creates one or more development tracks.

       4.      In CMS, your administrator defines software layers by connecting development tracks.

       5.      In the authoring environment of the Development Infrastructure, your developers do the following:

¡        Create a project and define development components and usage dependencies

¡        Create new development objects and change them, if necessary

¡        Check out existing development objects and change them, if necessary

¡        Check in changed development objects

¡        Perform a central build (activation) and deployment

¡        Release your changes

       6.      In CMS, your administrator or quality manager transports the changes.

       7.      Your quality manager tests and validates the changes centrally.

       8.      In CMS, your administrator or quality manager assembles the changed software components.

       9.      Your quality manager approves the package.

   10.      In CMS, your administrator or quality manager propagates the changed software components to the next track or to delivery.

Result

Your Development Infrastructure is configured so that it provides the infrastructure for your development, and you have handled the production of one software component release.