add requirement coverage in checklist#585
Conversation
RolandJentschETAS
requested review from
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
|
The created documentation from the pull request is available at: docu-html |
...der_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst
Outdated
Show resolved
Hide resolved
| * - ARC_01_02 | ||
| - Does the software architecture design consider all the requirements allocated to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? | ||
| - manual | ||
| - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g., use cases, functional safety requirements), non-functional requirements (e.g., performance, reliability), safety requirements (e.g., ASIL-related requirements), and security requirements (e.g., confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. |
There was a problem hiding this comment.
How should the decision taken into account? What would be evidence for that?
There was a problem hiding this comment.
The reviewer have to check in the review if all previous design decisions are fulfilled. Therefore he have to check the all the design decision. He provides evidence that he have done it. That's the same way as he states that the requirements are valid allocated or completely matches the requirements. Because there is no automatic way that a design decision is fulfilled in reality that have to be done by review. Which is exactly that review here. Best way would be, that any any design decision which influences the feature, the component, the requirements, ... would be linked to them. In such a case it would be easy for the reviewer to check that within the review.
There was a problem hiding this comment.
Agree for linkage, can you discuss/Propose how we can do that?
There was a problem hiding this comment.
The sphinx type "dec_rec" (decision record) already contains an optional link "affects", which can link to anywhere. But maybe can be discussed in the process meeting.
There was a problem hiding this comment.
This will be discussed and solved within EPIC eclipse-score/score#2625
...der_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst
Outdated
Show resolved
Hide resolved
process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst
Show resolved
Hide resolved
Signed-off-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com>
2 participants
Add requirement coverage in review checklist ...
See #584