Merge pull request #116 from eclipse-score/aschemmel-tech-tailor-in-sm

aschemmel-tech · web-flow · commit 8a076f1c1b8e · 2025-07-16T16:05:54.000+02:00
Add safety mechanism to process
diff --git a/process/process_areas/requirements_engineering/guidance/requirements_inspection_checklist.rst b/process/process_areas/requirements_engineering/guidance/requirements_inspection_checklist.rst
@@ -20,6 +20,7 @@ Requirement Inspection Checklist
 .. gd_chklst:: Requirements Inspection Checklist Template
    :id: gd_chklst__req__inspection
    :status: valid
+   :complies: std_req__iso26262__system_6412, std_req__iso26262__system_6414, std_req__iso26262__system_6421, std_req__iso26262__system_6422
    :tags: requirements_engineering
 
    **Purpose**
@@ -122,3 +123,15 @@ Requirement Inspection Checklist
         -
         -
         -
+      * - REQ_09_01
+        - For stakeholder requirements: Do those cover assumed safety mechanisms needed by the hardware and system?
+        - Note that the feature/component requirements also cover safety mechanisms in case those are needed to mitigate failures found during :ref:`safety_analysis`
+        -
+        -
+        -
+      * - REQ_09_02
+        - For other requirements: Do the requirements defining a safety mechanism contain the error reaction leading to a safe state?
+        - Alternatively to the safe state there could also be "repair" mechanisms. Also do not forget to consider REQ_05_01 for these.
+        -
+        -
+        -
diff --git a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst
@@ -20,7 +20,7 @@ Templates
 .. gd_temp:: Stakeholder Requirements Template
    :id: gd_temp__req__stkh_req
    :status: valid
-   :complies: std_wp__iso26262__software_651, std_req__iso26262__support_641, std_req__iso26262__support_6421, std_req__iso26262__support_6425
+   :complies: std_req__iso26262__system_6411, std_req__iso26262__system_6413, std_req__iso26262__support_641, std_req__iso26262__support_6421, std_req__iso26262__support_6425
 
    .. code-block:: rst
 
diff --git a/process/process_areas/requirements_engineering/requirements_concept.rst b/process/process_areas/requirements_engineering/requirements_concept.rst
@@ -101,16 +101,19 @@ Based on the inputs of the previous chapter the types of requirements which need
 Stakeholder Requirements
 ========================
 
-On the platform level the *Stakeholder (=customer) Requirements* are defined. These requirements describe which content the platform needs to contain, and serve as a project description of the top-level functionality. An example could be e.g.
+On the platform level the *Stakeholder (=customer) Requirements* are defined. These requirements describe which content (functionality and safety mechanisms) the platform needs to contain, and serve as a project description of the top-level functionality. An example could be e.g.
 
 .. code-block:: text
 
    The platform shall support configuration of applications via files (e.g. yaml, json)
 
+Note that the *Stakeholder Requirements* represent the assumed technical safety requirements for the platform SEooC,
+i.e. the assumption on what content is needed, which shall be matched by the user to their expectations.
+
 Feature Requirements
 ====================
 
-The *Feature Requirements* addresses mainly the integration level of SW modules and components. These shall describe the behavior of the feature on platform level shall be described including the correlations of the integrated components. They serves mainly as an input for (SW + Safety) Architects, Testers, Integrators and are derived from the *Stakeholder Requirements*. To provide an example
+The *Feature Requirements* derived from stakeholder requirements address mainly the integration level of SW modules and components. These shall describe the behavior of the feature on platform level shall be described including the correlations of the integrated components. They serves mainly as an input for (SW + Safety) Architects, Testers, Integrators and are derived from the *Stakeholder Requirements*. To provide an example
 
 .. code-block:: text
 
diff --git a/process/process_areas/requirements_engineering/requirements_workproducts.rst b/process/process_areas/requirements_engineering/requirements_workproducts.rst
@@ -18,7 +18,7 @@ Workproducts Requirements Engineering
 .. workproduct:: Stakeholder Requirements
    :id: wp__requirements__stkh
    :status: valid
-   :complies: std_wp__iso26262__system_651, std_wp__iso26262__software_651
+   :complies: std_wp__iso26262__system_651
 
    Technical requirements from a stakeholder viewpoint and assumptions of use based on the integration as SW platform SEooC in an assumed context.
 
diff --git a/process/process_areas/safety_management/workproducts.rst b/process/process_areas/safety_management/workproducts.rst
@@ -139,7 +139,7 @@ Work products
 .. workproduct:: Tailoring Document Platform
    :id: wp__tailoring_platform
    :status: valid
-   :complies: std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522
+   :complies: std_wp__iso26262__management_751, std_wp__iso26262__system_652, std_wp__iso26262__system_653, std_wp__iso26262__system_654, std_wp__iso26262__system_655, std_wp__iso26262__system_656, std_wp__iso26262__system_657, std_wp__iso26262__system_751, std_wp__iso26262__system_752, std_wp__iso26262__system_851, std_wp__iso26262__system_852, std_wp__iso26262__software_652, std_wp__iso26262__software_1151, std_wp__iso26262__software_1152, std_wp__iso26262__software_app_c_52, std_wp__iso26262__software_app_c_54, std_wp__iso26262__software_app_c_57, std_wp__iso26262__support_551, std_wp__iso26262__support_552, std_wp__iso26262__support_553, std_wp__iso26262__support_554, std_wp__iso26262__support_555, std_wp__iso26262__support_1351, std_wp__iso26262__support_1352, std_wp__iso26262__support_1353, std_wp__iso26262__support_1451, std_wp__iso26262__support_1452, std_wp__iso26262__support_1551, std_wp__iso26262__support_1651, std_wp__iso26262__analysis_551, std_wp__iso26262__analysis_552, std_wp__isopas8926__4522, std_req__iso26262__system_6423, std_req__iso26262__system_6424, std_req__iso26262__system_6425
 
    This work product "definition" links to all the work products which can be tailored out
    in the platform safety plan for your project if following the same approach as S-CORE,
