Configuration Management Process Requirements

Unique Id		status: valid
tags: done_automation, config_mgt, configuration_management complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8 satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch, wf__mr_saf_analyses_dfa, wf__vy_saf_analyses_dfa, wf__platform_mr_im_platform_mgmt_plan
The Docs-as-Code tool shall check that the Id’s of the configuration items (documented in doc-as-code) are unique. Note: For definition of configuration items see Configuration Management Co...
gd_req__configuration_uid		Process Requirements

Permanent Storage		status: valid
tags: prio_3_automation, config_mgt, configuration_management complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8 satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note
At least every platform release shall be stored permanently as a collection of text documents (docs and code) including the used OSS tooling on project owned servers. Note: This is to ensure to have the development artefacts available during the complete lifetime of the products (cars) the SW platform is used in.
gd_req__config_workproducts_storage		Process Requirements

Storage of pull requests documentation		status: valid
tags: prio_2_automation, config_mgt, configuration_management complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414 satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch
The content of pull requests (conversation, commits, files changed) shall be stored permanently for every release. Note: This requirement exists because PRs may be modified after a release, which could corrupt the documented inspection results recorded during the review.
gd_req__config_pull_request_storage		Process Requirements

Baseline Differences		status: valid
tags: prio_2_automation, config_mgt, configuration_management complies: std_req__iso26262__support_741 satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note
It shall be possible to show the differences between two baselines. Note: This could be done by showing all the commits which happened between these baselines in one release branch.
gd_req__config_baseline_diff		Process Requirements

Document attributes		status: valid
tags: prio_2_automation, configuration_management complies: std_req__aspice_40__SUP-8-BP3, std_req__aspice_40__SUP-8-BP4 satisfies: wf__platform_cr_mt_platform_mgmt_plan
It shall be prohibited to override any mandatory attribute value of an docs-as-code element. Note: This requirement exists because docs-as-code attributes may be globally overridden, which leads to a mismatch of code and the representing generated documentation. Exception only exists for optional tags, which can be used for filtering and reporting purposes.
gd_req__config_consistent_attributes		Process Requirements

Global tags extension		status: valid
tags: prio_3_automation, configuration_management satisfies: wf__platform_cr_mt_platform_mgmt_plan
It shall be possible to define global tags with the docs-as-code tool, which can be used for filtering and reporting. Note: This requirement exists to enable the use of global tags for filtering and reporting purposes, while still prohibiting the overriding of mandatory attributes or elements globally.
gd_req__config_global_tags		Process Requirements