Add process requirements for AoU linking#599
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.
There was a problem hiding this comment.
I was referring to this part of the metamodel:
so I thought the information should be available. But maybe we could differentiate by the deployment in module's repositories?
There was a problem hiding this comment.
The point is that you say "It shall be checked that architecture elements are not linked to its own AoU". But the arrow is only from the Feature Architecture. So the picture is completely fine for me, but the text is to wide. The feature architecture is only one of the "Architectural elements". See https://eclipse-score.github.io/process_description/pr-599/process_areas/architecture_design/guidance/architecture_process_reqs.html#gd_req__arch_build_blocks. Depending what is your goal, you have to either adopt the the text or the picture or both. But currently the picture and the text does not fit together. Or other way round the test is not described in the right way.
| 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" ?
There was a problem hiding this comment.
Yes, this would be something new. I had no good idea to show this in the picture. We could also have a new link name because it is not showing the derivation of a requirement.
There was a problem hiding this comment.
Can you not simply also change the meta model picture ?
| :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.
There was a problem hiding this comment.
I will update the new process requirement https://eclipse-score.github.io/process_description/pr-599/process_areas/architecture_design/guidance/architecture_process_reqs.html#gd_req__arch_attr_fulfils_aou to make clear the fulfils shall be part of the component/feature architecture (view) - but also will correct accordingly the https://eclipse-score.github.io/process_description/pr-599/process_areas/architecture_design/guidance/architecture_process_reqs.html#gd_req__arch_attr_fulfils where I copied from.
There was a problem hiding this comment.
There should not be a cyclic dependency, because the module only needs to fulfill the AoUs of another module it needs so the link direction as shown in https://eclipse-score.github.io/process_description/main/_images/score_traceability_model_wp_overview.drawio.svg (to "(external) Component assumtion of use" should be possible.
| 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.
aschemmel-tech
force-pushed
the
aschemmel-tech-fulfil-aou
branch
from
f15383a to
5b008ca
Compare
RolandJentschETAS
left a comment
RolandJentschETAS
left a comment
There was a problem hiding this comment.
Lats point was not changed
aschemmel-tech
force-pushed
the
aschemmel-tech-fulfil-aou
branch
from
5b008ca to
3c90811
Compare
4 participants
Resolves: #597