Verification ML2

[pahmann]

Epic Description

Get the Verification Process from ML1 to ML2
This includes actions mentioned in #489, #566, #530

• The gaps in the process according to the definition in https://eclipse-score.github.io/process_description/main/ are being collected in below list

• From previous epics and Audits following items are to be resolved:

  • Fix Verification Audit Findings #566
    • 6-9.4.5
    • 8-9.4.2.2
    • 8-9.4.3.3
    • Action_51: It needs to be clarified where the reference system is located physically (affecting e.g. access rights).
    • Action_82: Reference integration is triggered manually today. It shall be required that the reference integration is triggered if a component is changed (process verification requirement implemented as tool requirement CI).

• Towards ML3 as prep for an ML3 epic

  • deployment of process in one S-CORE module/platform repo, all documents are valid
  • process requirements prio 1&2 "automation" are implemented in tooling
  • respective tool evaluation done
  • Safety Audit passed (no open deviations/actions)
    • ??? (waiting for last audit report)

Acceptance Criteria (DoD)

all identified gaps have been resolved