Conversation
aschemmel-tech
requested review from
MaximilianSoerenPollak and
RolandJentschETAS
|
The created documentation from the pull request is available at: docu-html |
aschemmel-tech
requested review from
PandaeDo,
masc2023 and
pahmann
as code owners
|
Requested infrastructure team review if the requirements are understood and can be implemented |
| It shall be checked that architecture elements are not linked to its own AoU | ||
| ("own" means the AoU linked as "mitigated_by" to the Safety/Security Analysis linked via "violates" to the element) |
There was a problem hiding this comment.
Can you make an example here I don't quiet get what is allowed and what isn't.
There was a problem hiding this comment.
I think that's currently not possible from the meta model. See https://eclipse-score.github.io/process_description/pr-599/general_concepts/score_building_blocks_concept.html
There is no link from component to AoU. Therefore this check can't be done, because the AuO does not known, to which component or feature it belongs to.
| Requirements shall be linked to AoU via the attribute satisfies, if they already satisfy these. | ||
|
|
||
| * AoU <- feature requirements | ||
| * AoU <- component requirements | ||
|
|
||
| Note: "Already" illustrates the understanding that AoU come from used (external) components | ||
| which appear later in the development (after deciding an architecture). |
There was a problem hiding this comment.
This isn't depicted in the picture here
Is this something new?
There was a problem hiding this comment.
Is the "mitigated_by" link is meaned ? Instead of "satisfies" ?
| :complies: std_req__iso26262__support_6425, std_req__aspice_40__SWE-2-BP4 | ||
| :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch | ||
|
|
||
| Each architectural element shall be linked to AoUs if it fulfills these. |
There was a problem hiding this comment.
That contradicts the meta model and the other requirements.
See https://eclipse-score.github.io/process_description/pr-599/process_areas/architecture_design/guidance/architecture_process_reqs.html#gd_req__arch_build_blocks
The meta model shows only links from component architecture or feature architecture, but not from component, module, features, interface and interface op. See picture and list of architecture elements.
There was a problem hiding this comment.
Additionally a link from Feature to component or Feature AoU would lead to cyclic dependency of repositories, which is not implementable.
| It shall be checked that architecture elements are not linked to its own AoU | ||
| ("own" means the AoU linked as "mitigated_by" to the Safety/Security Analysis linked via "violates" to the element) |
There was a problem hiding this comment.
I think that's currently not possible from the meta model. See https://eclipse-score.github.io/process_description/pr-599/general_concepts/score_building_blocks_concept.html
There is no link from component to AoU. Therefore this check can't be done, because the AuO does not known, to which component or feature it belongs to.
3 participants
Resolves: #597