Change Management ML3

[masc2023]

Epic Description

Get the Change Management from ML2 to ML3

• First the gaps in the process according to the definition in https://eclipse-score.github.io/process_description/main/ have to be documented in below list
  • deployment of process in one S-CORE module/platform repo, all documents are valid
    • score, generic issue templates rolled-out, example Feature Requests / Modification (view), existing examples not using issue templates yet, but linked PRs, Only new Feature request, no modification
    • baselibs, generic issue templates implemented, no examples yet
    • baselibs_rust, not yet implemented, delete local templates PR not merged yet
    • communication, not yet implemented, not yet implemented, delete local templates PR not merged yet
    • config_management, not yet implemented, not yet implemented, delete local templates PR not merged yet
    • feo, generic issue templates implemented, no examples yet
    • kyron, not yet implemented, not yet implemented, delete local templates PR not merged yet
    • lifecycle, generic issue templates implemented, no examples yet
    • logging, generic issue templates implemented, no examples yet
    • orchestrator, not yet implemented, not yet implemented, delete local templates PR not done yet
    • persistency, generic issue templates implemented, no examples yet
    • scrample, not yet implemented, not yet implemented, delete local templates PR not done yet
    • process_description, generic issue templates implemented
    • Which other repos are from interest, e.g.
    • nlohmann_json, not yet implemented, not yet implemented, delete local templates PR not done yet
    • score_crates, generic issue templates implemented, no examples yet
  • process requirements prio 1&2 "automation" are implemented in tooling
    • gd_req__change_attr_title, Prio1, Part of Issue Type
    • gd_req__change_attr_impact_description, Prio1, Part of Issue Type
    • gd_req__change_attr_impact_safety, Prio 1, Part of Issue Type, only partly relevant for doc-as-code
    • gd_req__change_attr_impact_security, Prio 2, Part of Issue Type, only partly relevant for doc-as-code
    • gd_req__change_attr_types, Prio 1, Issue Type itself, and part, not relevant for doc-as-code
    • gd_req__change_attr_affected_wp, Part of Issue Type, Details?
    • gd_req__change_attr_milestone, Part of Issue
    • gd_req__change_attr_mandatory, Covered per Issue Type, not relevant for doc-as-code
    • gd_req__change_tool_impact_analysis, Prio 3, open
  • respective tool evaluation done
    • Currently not dedicated tool implemented for impact analysis, in general doc-as-code with sphinx-needs feature, Tool Evaluation done
  • Safety Audit passed (no open deviations/actions)
    • Fix Change Mgt Audit findings #567
    • Deviation_17: The Impact Analysis on Element Level is not defined by the process definition. It shall be identified which ISO 26262 work products are affected by the change. Still open, depends on tool or with issue entries ok?

Acceptance Criteria (DoD)

all identified gaps have been resolved