Software Change Management
Purpose
You use the Software Change Management IT process to manage the consistent and synchronized flow of object changes between different software stages, such as development, consolidation, and production in a distributed system environment. To enable this, SAP NetWeaver Development Infrastructure helps you to set up a distributed landscape for your custom development project.
Use of the Process
This process is part of the following IT scenarios:
IT Scenario |
Scenario Variant |
Prerequisites
You have installed a system with usage type Development Infrastructure (DI).
Process Flow
...
1. Your system administrator designs your software architecture, for example with Microsoft Visio.
2. In the System Landscape Directory of SAP NetWeaver (part of usage type AS Java), your system administrator defines your software components.
3. In Change Management Service (CMS) of DI, your system administrator creates one or more development tracks.
4. In CMS, your system administrator defines software layers by connecting development tracks.
5. In the authoring environment of DI, your developers perform the following actions:
○ They create a project and define development components and usage dependencies.
○ They create new development objects and change them, if necessary.
○ They check out existing development objects and change them, if necessary.
○ They check in any changed development objects.
○ They perform a central build (activation) and deployment.
○ They release the changes.
6. In CMS, your system administrator or quality manager transports the changes.
7. Your quality manager tests and validates the changes centrally.
8. In CMS, your system administrator or quality manager assembles the changed software components.
9. Your quality manager approves the package.
10. In CMS, your system 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 work, and you have handled the production of one software component release.