Merge pull request #599 from eclipse-score/aschemmel-tech-fulfil-aou

Add process requirements for AoU linking

Author: masc2023

process/general_concepts/_assets/score_building_blocks_meta_model.drawio.svg

@@ -158,8 +158,8 @@ Attributes of Architectural Elements
    * valid
    * invalid
 
-Traceability to Requirements
-----------------------------
+Traceability to Requirements and AoU
+------------------------------------
 
 .. gd_req:: Architecture attribute: fulfils
    :id: gd_req__arch_attr_fulfils
@@ -168,7 +168,16 @@ Traceability to Requirements
    :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 a requirement.
+   Each architectural view (feature/comp_arc_sta, feature/comp_arc_dyn) and interface (logic/real_arc_int) 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 static view (feature/comp_arc_sta) shall be linked to AoUs if the element (feature/comp) fulfills these.
 
 .. gd_req:: Architecture traceability
    :id: gd_req__arch_traceability
@@ -250,6 +259,16 @@ 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 architectural static view (feature/comp_arc_sta) 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,
+   another equivalent distinguishing is that the "own" AoU are in the same repository whereas the "other" are in another repository).
+
 .. gd_req:: Check of Architecture consistency Components in modules
    :id: gd_req__arch_consistency_model
    :status: valid

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -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 covers, if they already cover 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).
+
 .. gd_req:: Requirement Traceability
    :id: gd_req__req_traceability
    :status: valid