Rework of component requirements related to snapshots#337
Conversation
tizava
commented
Jul 10, 2026
- Snapshots are now explicit (Driven by the users)
- Snapshots are created from live data (Not from data flushed to disk)
- New API to acquire status of the snapshot slot (Occupied/Free)
- General rework and cleanup
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
PandaeDo
left a comment
There was a problem hiding this comment.
Please have a look again on the requirements. It seems to me that they are not fully atomic. You can use https://eclipse-score.github.io/process_description//main/process_areas/requirements_engineering/guidance/requirements_templates.html#gd_temp__req_formulation and also the question if the requirement is testable. Understandable they are.
| :belongs_to: comp__persistency_snapshot | ||
|
|
||
| The component shall maintain a configurable maximum number of snapshots. | ||
| The component shall provide APIs to create, restore, and delete snapshots. |
There was a problem hiding this comment.
Please specify amount of APIs. Requirement is not testable without this information.
There was a problem hiding this comment.
Sorry but maybe I don't understand your question. The APIs are three, the ones specified in the description of the requirement: create, restore and delete.
There was a problem hiding this comment.
This is was I meant. How should I know that these are three? I think I would need the information that there are 3 APIs. One for create....