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
 
 
@@ -80,17 +80,24 @@ The live feature architecture template snippets are maintained in the
 
 .. code-block:: rst
 
+   .. feat:: Feature Name
+      :id: feat__feature_name
+      :security: YES
+      :safety: ASIL_B
+      :status: invalid
+      :includes: logic_arc_int__feature_name__interface_name1
+
+      General Feature Description
+
    .. feat_arc_sta:: Feature Static View
       :id: feat_arc_sta__feature_name__static_view
       :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
 
-      General Feature Description
-
       .. needarch::
          :scale: 50
          :align: center
@@ -107,7 +114,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 +129,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::
@@ -452,6 +452,8 @@ The following section links to the rendered feature example that is now maintain
 Component Architecture
 ^^^^^^^^^^^^^^^^^^^^^^
 
+The following section is an example, how an component looks like and how the detail design of an component is described. Please note that components with an "ASIL_B" safety rating are highlighted with red borders in the diagram (e.g., "Component 1").
+
 The rendered component examples are maintained in the
 `module template documentation <https://eclipse-score.github.io/module_template/main/>`__.
 
@@ -462,7 +464,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::