eclipse-score / eclipse-score/persistency

KVS Requirement Inspection Findings (PR #288)

Open
#297 3 comments 0 reactions 1 assignee Claimed by @umaucher View on GitHub
documentation quality
Dominant language
Rust
Stars
2
Forks
28
Avg merge
2d 16h
Merged PRs (30d)
32

Description

Collective tracking issue for all **Passed: NO** findings from the [KVS Requirement Inspection Checklist](https://eclipse-score.github.io/persistency/pr-288/score/kvs/docs/requirements/chklst_req_inspection.html) (PR #288).

## Findings

| ID | Topic | Short Summary |
|----|-------|---------------|
| REQ_02_01 | Comprehensibility | Undefined terms ("snapshot"), unclear wording in multiple requirements |
| REQ_02_02 | Unambiguity | `comp_req__kvs__field_mode`: unverifiable term "as much as possible" |
| REQ_03_01 | Parent linkage | Multiple requirements linked to wrong parent reqs — rework of full set requested |
| REQ_04_01 | Consistency | Value serialization misplaced in KVS; wrong component name prefix in all req IDs |
| REQ_06_01 | External interfaces | Interface operations (e.g. open, flush) not fully specified |
| REQ_08_02 | Verifiability | Three requirements not confirmed testable or verified by design/code review |
| REQ_09_01 | Safety error reaction | Two safety-mechanism requirements missing error reaction definition |

For details see the checklist linked above.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.