Workflow Change Management

Create/Analyze Change Request		status: valid
status: valid tags: change_management contains: gd_guidl__change__change_request, gd_temp__change__feature_request, gd_temp__change__component_request, gd_temp__change__impact_analysis, gd_temp__component_classification, gd_req__change__attr_uid, gd_req__change__attr_status, gd_req__change__attr_title, gd_req__change__attr_impact_description, gd_req__change__attr_impact_safety, gd_req__change__attr_impact_security, gd_req__change__types, gd_req__change__attr_affected_wp, gd_req__change__attr_milestone, gd_req__change_tool_impact_analysis has: doc_concept__change__process, doc_getstrt__change__process needs input: wp__policies, wp__issue_track_system, wp__feat_request, wp__cmpt_request outputs: wp__issue_track_system, wp__feat_request, wp__cmpt_request responsible: rl__contributor approved by: rl__committer supported by: rl__technical_lead, rl__module_lead is satisfied by: gd_req__change__attr_uid, gd_req__change__attr_status, gd_req__change__attr_title, gd_req__change__attr_impact_description, gd_req__change__attr_impact_safety, gd_req__change__attr_impact_security, gd_req__change__types, gd_req__change__attr_affected_wp, gd_req__change__attr_milestone, gd_req__change_attr_mandatory, gd_req__change_tool_impact_analysis
The Change Request is created and analyzed. The Change Request must be filled out based on existing templates, including affected work products, impact on functional safety and security, schedule, risk resources and verification measures. All affected work products are traced. Until the template is not filled out properly, the Change Request may be kept in “draft” from the [Committer (rl__committer)]. The possible outcome is either a Change Request with status “draft” or “in review”.
wf__change__cr_an_change_request		Workflow

Review/Approve Change Request		status: valid
status: valid tags: change_management contains: gd_guidl__change__change_request, gd_temp__change__feature_request, gd_temp__change__component_request, gd_temp__change__impact_analysis, gd_temp__component_classification, gd_req__change__attr_uid, gd_req__change__attr_status, gd_req__change__attr_title, gd_req__change__attr_impact_description, gd_req__change__attr_impact_safety, gd_req__change__attr_impact_security, gd_req__change__types, gd_req__change__attr_affected_wp, gd_req__change__attr_milestone, gd_req__change_tool_impact_analysis has: doc_concept__change__process, doc_getstrt__change__process needs input: wp__issue_track_system, wp__feat_request, wp__cmpt_request outputs: wp__issue_track_system, wp__feat_request, wp__cmpt_request responsible: rl__committer approved by: rl__technical_lead, rl__module_lead supported by: rl__safety_manager, rl__security_manager, rl__quality_manager is satisfied by: gd_req__change__attr_uid, gd_req__change__attr_status, gd_req__change__attr_title, gd_req__change__attr_impact_description, gd_req__change__attr_impact_safety, gd_req__change__attr_impact_security, gd_req__change__types, gd_req__change__attr_affected_wp, gd_req__change__attr_milestone, gd_req__change_attr_mandatory, gd_req__change_tool_impact_analysis
The Change Request is evaluated based on the analysis result either approved, rejected or delayed. The Change Request is implemented and verified. The defined verification measures must be available and pass. The final approval is done by the [Technical Lead (rl__technical_lead)] or the [Module Project Lead (rl__module_lead)] dependent on the scope. The possible outcome is either a Change Request with status “accepted” or “rejected” or kept “in review”.
wf__change__rv_ap_change_request		Workflow