Getting Started#
Getting Started on Change Management
|
status: valid
|
||||
This document describes the steps to create a change request, and further to analyze, implement, and to control the change until closure. Where a change is defined as an introduction of a new feature/component or modification of an existing feature/component.
Examples for change requests:
New feature e.g. communication, debugging, health management, cryptography introduced (feature request).
Existing feature, e.g. communication supports new protocol (feature modification).
New component for parsing a protocol introduced (component request).
API change for an existing component (component modification).
Therefore a template { title } is available. This template is complemented by the { title }, { title }, { title } and { title }.
General Workflow#
The workflows are defined in the Change Management Workflows section.
For every change identified, the following workflows are executed:
Create your change request according to { title }
Analyze change request report according to { title }
Implement change request and monitor it until closure according to { title }
Close the change request according to { title }
In addition create a change management plan as part of the platform management plan according to { title }