Revert gd_req/arch links per review, add satisfied_by for requirements

Author: RSingh1511

process/folder_templates/features/feature_name/architecture/index.rst

@@ -54,14 +54,14 @@ Requirements
    .. needtable:: Overview of Feature Requirements
       :style: table
       :columns: title;id
-      :filter: search("feat_arch_sta__archdes$", "satisfies_back")
+      :filter: search("feat_arch_sta__archdes$", "fulfils_back")
       :colwidths: 70,30
 
 
 .. needtable:: Overview of Feature Requirements
    :style: table
    :columns: title;id
-   :filter: search("feat_arch_sta__archdes$", "satisfies_back")
+   :filter: search("feat_arch_sta__archdes$", "fulfils_back")
    :colwidths: 70,30
 
 
@@ -85,7 +85,7 @@ The live feature architecture template snippets are maintained in the
       :security: YES
       :safety: ASIL_B
       :status: invalid
-      :satisfies: feat_req__feature_name__some_title
+      :fulfils: feat_req__feature_name__some_title
       :includes: logic_arc_int__feature_name__interface_name1
       :belongs_to: feat__feature_name
 
@@ -107,7 +107,7 @@ Dynamic Architecture
       :security: YES
       :safety: ASIL_B
       :status: invalid
-      :satisfies: feat_req__feature_name__some_title
+      :fulfils: feat_req__feature_name__some_title
       :belongs_to: feat__feature_name
 
       Put here a sequence diagram
@@ -122,7 +122,7 @@ Logical Interfaces
       :security: YES
       :safety: ASIL_B
       :status: invalid
-      :satisfies: feat_req__feature_name__some_title
+      :fulfils: feat_req__feature_name__some_title
 
       General Interface Description
 

process/folder_templates/features/feature_name/requirements/index.rst

@@ -45,7 +45,7 @@ Feature Requirements
       :valid_from: v0.0.1
       :valid_until: v1.0.1
       :status: invalid
-      :belongs_to: feat__feature_name
+      :satisfied_by: feat__feature_name
 
       The Feature shall do xyz to the user to bring him to this condition at this time.
 
@@ -66,7 +66,7 @@ Feature Requirements
     The above directives must be updated according to your feature requirements.
 
     - Replace the example content by the real content for your first requirement (according to :need:`gd_guidl__req_engineering`)
-    - Set ``belongs_to`` with a link to feature ID
+    - Set ``satisfied_by`` with a link to feature ID
     - Set ``reqtype`` with a link to the right value (<Functional|Interface|Process|Non-Functional>)
     - Set ``satisfies`` with a link to the right stakeholder requirement
     - Adjust ``safety`` and ``security`` to the right value (ASIL B/QM; YES/NO)

process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst

@@ -45,7 +45,7 @@ Requirements Linked to Component Architecture
    .. needtable:: Overview of Component Requirements
       :style: table
       :columns: title;id
-      :filter: search("comp_arch_sta__archdes$", "satisfies_back")
+      :filter: search("comp_arch_sta__archdes$", "fulfils_back")
       :colwidths: 70,30
 
 Description
@@ -93,7 +93,7 @@ The live component architecture template is maintained in the
       :status: invalid
       :belongs_to: comp__component_name_template
       :uses: logic_arc_int__feature_name__interface_name1
-      :satisfies: comp_req__component_name__some_title
+      :fulfils: comp_req__component_name__some_title
 
       .. needarch::
          :scale: 50
@@ -112,7 +112,7 @@ Dynamic Architecture
       :safety: ASIL_B
       :status: invalid
       :belongs_to: comp__component_name_template
-      :satisfies: comp_req__component_name__some_title
+      :fulfils: comp_req__component_name__some_title
 
       Put here a sequence diagram
 
@@ -126,7 +126,7 @@ Interfaces
       :id: real_arc_int__<component>__<Title>
       :security: <YES|NO>
       :safety: <QM|ASIL_B>
-      :satisfies: <link to component requirement id>
+      :fulfils: <link to component requirement id>
       :language: cpp
 
 Internal Components
@@ -139,7 +139,7 @@ Internal Components
       :status: invalid
       :safety: ASIL_B
       :security: YES
-      :satisfies: comp_req__component_name__some_title
+      :fulfils: comp_req__component_name__some_title
       :belongs_to: comp__component_name_template
 
       No architecture but detailed design

process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst

@@ -46,7 +46,7 @@ Component Requirements
       :safety: ASIL_B
       :derived_from: feat_req__feature_name__some_title
       :status: invalid
-      :belongs_to: comp__component_name_template
+      :satisfied_by: comp__component_name_template
 
       The Component shall do xyz to another component to bring it to this condition at this time
 
@@ -57,7 +57,7 @@ Component Requirements
 
     - Replace the example content by the real content for your first requirement
     - Set ``satistifes`` with links to Feature requirements
-    - Set ``belongs_to`` with a link to the right Component id
+    - Set ``satisfied_by`` with a link to the right Component id
     - Set ``safety`` and ``security`` to the right value
     - Set the status to valid and start the review/merge process
     - Add other needed requirements for your component

process/general_concepts/score_review_concept.rst

@@ -187,7 +187,7 @@ Process Requirements
    :status: valid
    :tags: prio_1_automation, general
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
-   :derived_from: wf__monitor_verify_requirements
+   :satisfies: wf__monitor_verify_requirements
 
    The version of a requirement shall not change by an inspection.
 
@@ -200,7 +200,7 @@ Process Requirements
    :status: draft
    :tags: general
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
-   :derived_from: wf__mr_vy_arch
+   :satisfies: wf__mr_vy_arch
 
    The version of architecture element shall not change by an inspection.
 
@@ -215,7 +215,7 @@ Process Requirements
    :status: valid
    :tags: prio_2_automation, general
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414, std_req__iso26262__software_942
-   :derived_from: wf__monitor_verify_requirements, wf__mr_vy_arch
+   :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch
 
    For every pull request that modifies a work product subject to inspection,
    a pull‑request template containing the applicable inspection checklist items shall be provided.
@@ -227,7 +227,7 @@ Process Requirements
    :status: valid
    :tags: prio_2_automation, general
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
-   :derived_from: wf__monitor_verify_requirements, wf__mr_vy_arch
+   :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch
 
    It shall be checked that only a PR with the inspection checklist filled out can set a status to valid(inspected).
 
@@ -236,6 +236,6 @@ Process Requirements
    :status: valid
    :tags: prio_2_automation, general
    :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414
-   :derived_from: wf__monitor_verify_requirements, wf__mr_vy_arch
+   :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch
 
    It shall be checked that the status is reset to valid whenever a requirement is modified (changes version).

process/process_areas/architecture_design/architecture_concept.rst

@@ -440,7 +440,7 @@ The following section links to the rendered feature example that is now maintain
       :safety: QM
       :status: valid
       :includes: logic_arc_int__example_feature__archex_logical_interface_1, logic_arc_int__example_feature__archex_logical_interface_2
-      :satisfies: feat_req__example_feature__archdes_example_req
+      :fulfils: feat_req__example_feature__archdes_example_req
       :belongs_to: feat__example_feature
 
       .. needarch::
@@ -462,7 +462,7 @@ The rendered component examples are maintained in the
       :status: valid
       :safety: ASIL_B
       :security: NO
-      :satisfies: comp_req__example_feature__archex_example_req
+      :fulfils: comp_req__example_feature__archex_example_req
       :belongs_to: comp__component_component_getstrt
 
       .. needarch::

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -25,7 +25,7 @@ Architectural Model
    :status: valid
    :tags: manual_prio_1
    :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    For architecture design a model based approach should be used. The model shall consist of different architectural elements.
 
@@ -34,7 +34,7 @@ Architectural Model
    :status: valid
    :tags: done_automation
    :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432, std_req__iso26262__software_743
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    The architectural elements shall be hierarchically structured on two levels:
 
@@ -46,7 +46,7 @@ Architectural Model
    :status: valid
    :tags: done_automation
    :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432, std_req__aspice_40__iic-01-03, std_req__aspice_40__iic-01-50
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Following architectural elements shall be defined on the respective hierarchical level:
 
@@ -76,7 +76,7 @@ Architectural Model
    :status: valid
    :tags: done_automation
    :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    For modeling the viewpoints following relations shall be used:
 
@@ -95,7 +95,7 @@ Architectural Views
    :status: valid
    :tags: manual_prio_1
    :complies: std_req__iso26262__support_6432, std_req__iso26262__software_742, std_req__aspice_40__SWE-2-BP1, std_req__aspice_40__SWE-2-BP2
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    The architecture shall be shown on following views on each architectural level:
 
@@ -113,7 +113,7 @@ Attributes of Architectural Elements
    :status: valid
    :tags: manual_prio_1, attribute, mandatory
    :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6432
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a unique ID. It shall be in a format which is also human readable and consists of
 
@@ -127,7 +127,7 @@ Attributes of Architectural Elements
    :id: gd_req__arch_attr_security
    :status: valid
    :tags: manual_prio_1, attribute, mandatory
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a security relevance identifier:
 
@@ -139,7 +139,7 @@ Attributes of Architectural Elements
    :status: valid
    :tags: manual_prio_1, attribute, mandatory
    :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__iso26262__software_746
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a automotive safety integrity level (ASIL) identifier:
 
@@ -151,7 +151,7 @@ Attributes of Architectural Elements
    :status: valid
    :tags: manual_prio_1, attribute, mandatory
    :complies: std_req__iso26262__support_6425
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a status:
 
@@ -166,7 +166,7 @@ Traceability to Requirements and AoU
    :status: valid
    :tags: manual_prio_1, attribute
    :complies: std_req__iso26262__support_6425, std_req__aspice_40__SWE-2-BP4
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Architectural views (feature/comp_arc_sta, feature/comp_arc_dyn) and interfaces (logic/real_arc_int)
    should be linked to a requirement on the corresponding level.
@@ -181,7 +181,7 @@ Traceability to Requirements and AoU
    :status: valid
    :tags: manual_prio_1, attribute
    :complies: std_req__iso26262__support_6425, std_req__aspice_40__SWE-2-BP4
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Architectural elements (feat_arc_sta, comp) shall be linked to AoUs if the element fulfills these.
 
@@ -190,7 +190,7 @@ Traceability to Requirements and AoU
    :status: valid
    :tags: manual_prio_1
    :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-2-BP4
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Requirements shall be satisfied by an architectural element on the corresponding level.
 
@@ -209,7 +209,7 @@ Checks for Architectural Design
    :id: gd_req__arch_attr_mandatory
    :status: valid
    :tags: prio_1_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked if all mandatory attributes for each architectural element are provided by the user. For all elements following attributes shall be mandatory:
 
@@ -223,7 +223,7 @@ Checks for Architectural Design
    :id: gd_req__arch_linkage_safety
    :status: valid
    :tags: prio_1_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
    :complies: std_req__aspice_40__SWE-2-BP4
 
    It shall be checked that every valid safety architectural element is linked according to the defined model :need:`gd_req__arch_build_blocks_corr`.
@@ -232,7 +232,7 @@ Checks for Architectural Design
    :id: gd_req__arch_linkage_safety_trace
    :status: valid
    :tags: prio_1_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
    :complies: std_req__iso26262__software_746, std_req__iso26262__software_748
 
    It shall be checked that valid safety architectural elements (Safety!=QM) can only be linked against valid safety architectural elements.
@@ -241,15 +241,15 @@ Checks for Architectural Design
    :id: gd_req__arch_linkage_security_trace
    :status: valid
    :tags: prio_2_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked that security relevant architectural elements (Security==YES) can only be linked against security relevant architectural elements.
 
 .. gd_req:: Check of Architecture linkage requirement
    :id: gd_req__arch_linkage_requirement
    :status: valid
    :tags: prio_1_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked that each architectural element (safety!=QM) is linked against at least one safety requirement (safety!=QM).
    It shall be checked that architectural elements with safety=QM are not linked against safety requirements (safety!=QM).
@@ -258,7 +258,7 @@ Checks for Architectural Design
    :id: gd_req__arch_linkage_requirement_type
    :status: valid
    :tags: prio_3_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked that requirements of a respective type can only be linked to architectural elements according to following traceability:
 
@@ -269,7 +269,7 @@ Checks for Architectural Design
    :id: gd_req__arch_linkage_aou
    :status: valid
    :tags: prio_2_automation, attribute, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :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,
@@ -279,14 +279,14 @@ Checks for Architectural Design
    :id: gd_req__arch_consistency_interf
    :status: valid
    :tags: prio_2_automation, model, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked if any interface referred by the features (link from Feature to Logical Arc. Interfaces must be defined and exists) is matched by an "implements" link in the Module (from component to Logical Arc. Interface). Additionally it shall be checked if the feature architecture are linked against at least one logical architectural interface.
 
 .. gd_req:: Check of Architecture consistency in dynamic architecture
    :id: gd_req__arch_consistency_dynamic
    :status: valid
    :tags: prio_3_automation, model, check
-   :derived_from: wf__cr_mt_featarch, wf__cr_mt_comparch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked if all SW components which are mentioned in the dynamic architecture views are defined in the static architecture.