Persistency CFT [2025-05-22, 2:30 - 4:00 pm]

[guysagnes]

Agenda

Change of Cross Functional Team (CFT) to Functional Team (FT)

Participants:

• @guysagnes
• @sbachmann-qorix
• @bogdan Badicu
• @uwe Maucher
• @joshualicht
• @JannikSzwajczyk

Meeting reports

Cross CFT

• Clear responsibilities for infrastructure in both C++ & Rust pilots to enable gap analysis in community
  Epic: Process Pilot #760

Architecture

• JSON Lib dependency and agreement
• Pls review feature definition under Feature Request: JSON Parser #822

Workpackages

Open Pull request
KVS Feature / Requirements
Feature: Persistency KVS - Feature Architecture -> ready for review
Feature: Persistency KVS - Component Requirements -> draft

Merged content
Feature: Persistency KVS - Feature Requirements

Progress report

• Feature Request for Persistency #95 -> done
  • The file system related requirement will be reported to the gap analysis with reference to baselib/filesystem
• [WS AI] Concurrent access in persistency (low prio) -> closed

Architecture / Design

• Improvement: Adaptation of the open / build for KVS to allow process separation #1071

Open actions

• Requirement related safety qualification level (QM / ASIL_B) started @sbachmann-qorix (Pilot)

Meeting Minutes

Related Persistency CFT Board:
Persistency FT

Feature Request for Persistency · Issue #95 · eclipse-score/score

Focus:

• Walkthrough Architecture: https://eclipse-score.github.io/score/pr-1068/features/persistency/kvs/architecture/feature_architecture.html
  • Finding of the review will be provided to the pull request directly
• Walkthrough Component: https://eclipse-score.github.io/score/pr-1069/features/persistency/kvs/requirements/index.html

Reference:

• requirements_inspection_checklist
• requirements_templates

Requirement definition

The requirement reported are not defined following the template
Requirement Formulation Template

Requirements shall be specified according to the following schema:
<The SW Platform|Feature|Component> shall

<temporal/logical conjunction>
<Note: (optional, not to be verified)>
Important for understanding the separation between requirement and note.
The note can contain additional information e.g., verification criteria.
A verification criteria may contain:
(Verification Objectives), Verification Method, (Verification Environment), (Verification Conditions and Constraints), Verification Success Criteria

[sbachmann-qorix]

Please review the coverage unit tests: eclipse-score/inc_mw_per#13

[joshualicht]

Add some questions/topics to the board:

• How should the separation between Rust and C++ be handled?

  • Proposition to be reported to integration / process - Handling of one component with 2 implementations (Rust / C++)
    • make dedicated realization separation inside the component. (Rust API currently not build on bazel)

• C++ Version to be used

  • identified version C++ 2017 due to the SCC tool verification
    • limitation identified with this version related to map handling. (at least 2020 will support expectation)

• Recursive conversion of KvsValue

  • Expectation that the recursive approach may be part of the MISRA rules to be respected
    -> check similarity with realization inside communication
    -> identification of a grant approach

• Handling of dynamic types (e.g., String, Vector, Map, ...)

  • MISRA rules reported type - Rule 21.6.1 / 21.6.2