Configuration Management Process Requirements#

Unique Id
status: valid

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... (doc_concept__configuration_process)

Permanent Storage
status: valid

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.

Storage of pull requests documentation
status: valid

The content of pull requests (conversation, commits, files changed) shall be stored permanently for every release.

Note: The reason is that the PRs could be altered after the release and therefore for example the inspection documented within the review would be corrupted.

Baseline Differences
status: valid
tags: prio_2_automation, config_mgt

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.