Improvement: Document Change Management Process

[PandaeDo]

Important

Make sure to link this issue with the PR for your improvement.

Document in score repository (until the process_description repo is available)

Create documentation according to "template": https://github.com/eclipse-score/process_description/blob/main/requirements_engineering/index.rst

this includes workproducts definition and linking to standard
this includes guidance definition and linking to standard

Prepare presentation in audit session

[masc2023]

• create roles as sphinx-needs according to SCORE metamodel by using already available https://github.com/eclipse-score/score/blob/main/docs/process/roles/index.rst - define complete RASIC in description

• create workproducts as sphinx-needs according to SCORE metamodel by using already available https://github.com/eclipse-score/score/blob/main/docs/process/workproducts/index.rst - only the workproducts output by the process and where the main output responsibility is (e.g. release report is part of release mgt even if the safety manger supports this)

• create workflows as sphinx-needs according to SCORE metamodel by using already available https://github.com/eclipse-score/score/tree/main/docs/process/workflows

• describe concept

• create guidelines

• create templates for work products (if needed, if not: create empty bullet point)

• create checklists for inspection/review

• describe methods (if needed, if not: create empty bullet point)

• derive process requirements (also covering tool support)

• provide "getting started"

• fix audit findings from incubation project in SCORE, if effort is low (less than 4h), otherwise create ticket for this (findings see (eclipse-score/process_description](Fix audit 2 findings process_description#2)

• eventually the metamodel needs update - support this in Improvement: Metamodel corrections #335

Note: Metamodel is here: https://github.com/eclipse-score/score/blob/main/docs/_tooling/extensions/score_metamodel/metamodel.py

[masc2023]

~10 days