feat: Satisfy gd_req__arch_linkage_safety#557
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //src:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
48ae479 to
5b8e488
Compare
|
Consumer test "score" fails with three warnings: Checked one and the warning is correct. Created eclipse-score/score#2933 to fix that. |
| :satisfies: gd_req__arch_linkage_safety | ||
| :parent_covered: YES | ||
|
|
||
| Enforce that valid ASIL architecture views fulfil only ASIL requirements. |
There was a problem hiding this comment.
can we mention the exact attribute here? And what exactly is an architecture view. There was so much confusion int he past about what a "view" is, that I would love to simply have the exact need types here.
There was a problem hiding this comment.
Yes, should be static and dynamic ...
There was a problem hiding this comment.
Good question. The classics are feat_arc_sta, comp_arc_sta, logic_arc_int, real_arc_int. I'll add them.
What about logic_arc_int, real_arc_int, und mod_view_sta? At least in tool_req__docs_arch_views they are listed as architecture views.
There was a problem hiding this comment.
@RolandJentschETAS Maybe it's better to extend tool_req__docs_req_arch_link_safety_to_arch to cover all architecture elements AND views? Otherwise it feels like we spread the same requirement to multiple requirements.
MaximilianSoerenPollak
left a comment
There was a problem hiding this comment.
Some comments.
| .. tool_req:: Check safety architecture view fulfils only safety requirements | ||
| :id: tool_req__docs_arch_link_safety_fulfils | ||
| :tags: Architecture | ||
| :implemented: YES | ||
| :version: 1 | ||
| :satisfies: gd_req__arch_linkage_safety | ||
| :parent_covered: YES | ||
|
|
||
| Enforce that valid ASIL architecture views | ||
| (``feat_arc_sta``, ``feat_arc_dyn``, ``comp_arc_sta``, ``comp_arc_dyn``) | ||
| "fulfil" only ASIL requirements. |
There was a problem hiding this comment.
Do we not already have a requirement that does this?
This one here
Also this should be filtered against VALID only no?
There was a problem hiding this comment.
Tricky question. We don't have check that in other cases. Any mandatory link may go an invalid item.
There was a problem hiding this comment.
We do have this check here:
i have to ask where the process requirement for this is again.
There was a problem hiding this comment.
I believe need._links.values() in graph_checks already covers all attributes including fulfil? That would imply we don't have to check it here again.
There was a problem hiding this comment.
Maybe it's better to extend tool_req__docs_req_arch_link_safety_to_arch to cover all architecture elements AND views? Otherwise it feels like we spread the same requirement to multiple requirements.
| - safety != QM | ||
| - status == valid | ||
| check: | ||
| fulfils: safety != QM |
There was a problem hiding this comment.
This has to be status == valid too.
Otherwise we would be checking also when we link against invalid requirements ?
There was a problem hiding this comment.
Same as the other comment: We don't require that for other links.
📌 Description
🚨 Impact Analysis
✅ Checklist