Add process requirements for AoU linking #599
+35
−2
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -158,8 +158,8 @@ Attributes of Architectural Elements | |
| * valid | ||
| * invalid | ||
|
|
||
| Traceability to Requirements and AoU | ||
| ------------------------------------ | ||
|
|
||
| .. gd_req:: Architecture attribute: fulfils | ||
| :id: gd_req__arch_attr_fulfils | ||
|
|
@@ -170,6 +170,15 @@ Traceability to Requirements | |
|
|
||
| Each architectural element shall be linked to a requirement. | ||
|
|
||
| .. gd_req:: Architecture attribute: fulfils (AoU) | ||
| :id: gd_req__arch_attr_fulfils_aou | ||
| :status: valid | ||
| :tags: manual_prio_1, attribute, mandatory | ||
| :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. | ||
|
|
||
| .. gd_req:: Architecture traceability | ||
| :id: gd_req__arch_traceability | ||
| :status: valid | ||
|
|
@@ -250,6 +259,15 @@ Checks for Architectural Design | |
| * Functional requirements <-> static / dynamic architectural elements (feat_arc_sta, feat_arc_dyn) | ||
| * Interface requirements <-> interface architectural elements (logic_arc_int, logic_arc_int_op) | ||
|
|
||
| .. gd_req:: Check of Architecture linkage to AoU | ||
| :id: gd_req__arch_linkage_aou | ||
| :status: valid | ||
| :tags: prio_2_automation, attribute, check | ||
| :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch | ||
|
|
||
| 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) | ||
|
Comment on lines
+268
to
+269
Contributor
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.
Contributor
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. |
||
|
|
||
| .. gd_req:: Check of Architecture consistency Components in modules | ||
| :id: gd_req__arch_consistency_model | ||
| :status: valid | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -192,6 +192,21 @@ Process Requirement Linkage | |
| * workflow or stakeholder requirements <- process requirements | ||
| * process requirements or stakeholder requirements <- tool requirements | ||
|
|
||
| .. gd_req:: Requirement Linkage to AoU | ||
| :id: gd_req__req_linkage_aou | ||
| :status: valid | ||
| :tags: manual_prio_1, attribute | ||
| :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5 | ||
| :satisfies: wf__req_feat_req, wf__req_comp_req | ||
|
|
||
| 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). | ||
|
Comment on lines
+202
to
+208
Contributor
There was a problem hiding this comment. This isn't depicted in the picture here
Contributor
There was a problem hiding this comment. Is the "mitigated_by" link is meaned ? Instead of "satisfies" ? |
||
|
|
||
| .. gd_req:: Requirement Traceability | ||
| :id: gd_req__req_traceability | ||
| :status: valid | ||
|
|
||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
and
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Additionally a link from Feature to component or Feature AoU would lead to cyclic dependency of repositories, which is not implementable.