Verification ML2

[pahmann]

Epic Description

Get the Verification Process from ML1 to ML2

• 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
      • The requirement was explained during the audit and it got marked as "n/a" for the audit as we hand over responsibility of unit testing in hardware near environment as an AoU for the integrator. In the discussions we agreed that the AoU is feasible for distributors.
    • 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).
      • Marked as resolved in Audit report "Revision10, May 2026" on page 215

• 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)
    • Remaining findings are addressed by above action items. Remaining is 8-9.4.2.2 and 8-9.4.3.3
  • Resolve actions mentioned in Pending actions for verfication process to reach complete ML2 #489, Fix Verification Audit Findings #566, Verification Process Gaps #530

Acceptance Criteria (DoD)

all identified gaps have been resolved