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 guidelines Feature Request Template (gd_temp__change_feature_request) and Component Request Template (gd_temp__change_component_request), Change Request Guideline (gd_guidl__change_change_request) and a Concept Description (doc_concept__change_process) are available.
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 Create Change Request (wf__change_create_cr)
Analyze change request report according to Analyze Change Request (wf__change_analyze_cr)
Implement change request and monitor it until closure according to Implement and Monitor Chang... (wf__change_implement_monitor_cr)
Close the change request according to Close Change Request (wf__change_close_cr)
In addition create a change management plan as part of the platform management plan according to Create/Maintain Platform Ma... (wf__platform_cr_mt_platform_mgmt_plan)