Repository navigation
update component requirements. - #443
Conversation
Ahmed-Elsaka-JC
commented
Sep 25, 2026
- update component requirements
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
7384c86 to
12962f4
Compare
| .. comp_req:: Callback Support | ||
| :id: comp_req__kvs__callback_support | ||
| .. comp_req:: Default Value Config tool validation | ||
| :id: comp_req__kvs__default_value_cfg_tool_validation |
There was a problem hiding this comment.
| :id: comp_req__kvs__default_value_cfg_tool_validation | |
| :id: comp_req__kvs__default_value_cfg_tool_vali |
Id is too long
There was a problem hiding this comment.
i would change it to : comp_req__kvs__storage_tool
| :id: comp_req__kvs__multi_instance | ||
| :reqtype: Functional | ||
| :security: NO | ||
| :safety: ASIL_B |
There was a problem hiding this comment.
It's derived from an QM requirement. So you might check if this is also an QM requirement.
There was a problem hiding this comment.
thanks for catch , i will fix it
| :satisfied_by: comp__persistency_kvs[version==1] | ||
| :tags: inspected | ||
|
|
||
| When the storage cannot be loaded, the component shall behave according to the ``Need_Kvs`` configuration parameter (represented by the ``OpenNeedKvs`` flag): |
There was a problem hiding this comment.
General remark for all requirements:
Please use
feat_req__persistency__multiple_app (ASIL_B) requires the Persistency to prevent access to a KVS instance from multiple OS processes, so this is a component requirement and not an AoU on the user. ID and wording are aligned with eclipse-score#443. Open point: the requirement is not implemented yet (Rust and C++ only use in-process mutexes, no inter-process lock). Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
d12f5f3 to
54adb90
Compare
| :satisfied_by: comp__persistency_kvs[version==1] | ||
| :tags: inspected | ||
|
|
||
| The component shall access operating system services exclusively through an abstraction layer and shall not depend on any specific operating system. |
There was a problem hiding this comment.
isn't this sentence enough :"The component shall access operating system services exclusively through an os abstraction layer" . the second part implies the same right.
| :satisfied_by: comp__persistency_kvs[version==1] | ||
| :tags: inspected | ||
|
|
||
| The component shall not allocate dynamic memory during runtime operations. All memory required for runtime operation shall be allocated during initialization of a KVS instance. |
There was a problem hiding this comment.
Should we write it like this :"The component shall not allocate heap memory after a KVS instance has been successfully created/opened. All memory required for the instance's operation shall be allocated during its opening, with the constraints defined by :need:comp_req__kvs__constraints."
| :satisfied_by: comp__persistency_kvs[version==1] | ||
| :tags: inspected | ||
|
|
||
| The component shall manage all runtime variables within an instance to |
There was a problem hiding this comment.
Should we frame it like this :"The component shall support the concurrent existence of multiple KVS instances , such that operations on one instance do not affect the data or state of any other instance."
7800159 to
7b0782a
Compare
|
Documentation preview for this pull request is available at: |
There was a problem hiding this comment.
| :status: invalid |
There was a problem hiding this comment.
resolved with latest commit
| - NO | ||
| - :need:`comp_req__kvs__field_mode` uses hard to verify term "as much as possible" | ||
| - https://github.com/eclipse-score/persistency/issues/297 | ||
| - YES |
There was a problem hiding this comment.
When we change the inspection we must mark it as invalid. It's an screenshot we made with the named participants. I would recommend to keep as it is and create a new version of the inspection. There are a lot more changes that has to be considered.
There was a problem hiding this comment.
resolved with latest commit
- remove tags element for all new requirements , updated requiremetns. - set status of inspection checklist to invalid
PandaeDo
left a comment
There was a problem hiding this comment.
Still some open topics like tag inspected for new, uninspected requirements. Fine for the moment. Safety Analysis will require update of requirements and afterwards we'll perform the inspection.
d83b0e4