From 02ef2eb4dd667fc8c54a444927635fa5181d1c2f Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Fri, 20 Feb 2026 12:58:14 +0100 Subject: [PATCH 1/4] add requirement coverage in checklist --- .../feature_name/architecture/chklst_arc_inspection.rst | 9 ++++++++- .../docs/architecture/chklst_arc_inspection.rst | 9 ++++++++- 2 files changed, 16 insertions(+), 2 deletions(-) diff --git a/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst b/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst index 5dcb72506a..4c3bc8b887 100644 --- a/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst @@ -66,13 +66,20 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - - * - ARC_01_02 + - Does the software architecture design consider all the requirements allocated to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? + - manual + - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g., use cases, functional safety requirements), non-functional requirements (e.g., performance, reliability), safety requirements (e.g., ASIL-related requirements), and security requirements (e.g., confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. + - + - + - + * - ARC_01_03 - If the architectural element is related to any supplier manuals (including safety and security), are the relevant parts covered? - manual - If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are fulfilled). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered. - - - - * - ARC_01_03 + * - ARC_01_04 - Is the architectural element traceable to the lower-level artifacts as defined by the work product traceability? - automated - Will be removed from checklist once the requirement (:need:`Correlations of the architectural building blocks `) is implemented by automated tool check. See `Tool Requirements `_. diff --git a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst index a72c28f84d..b30470144d 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst @@ -66,6 +66,13 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - - * - ARC_01_02 + - Does the software architecture design consider all the requirements allocated to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? + - manual + - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g., use cases, functional safety requirements), non-functional requirements (e.g., performance, reliability), safety requirements (e.g., ASIL-related requirements), and security requirements (e.g., confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. + - + - + - + * - ARC_01_03 - If the architectural element is related to any supplier manuals (incl. safety and security) are the relevant parts covered? - manual @@ -73,7 +80,7 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - - - - * - ARC_01_03 + * - ARC_01_04 - Is the architectural element traceable to the lower level artifacts as defined by the workproduct traceability? - automated - Will be removed from checklist once the requirement (:need:`Correlations of the architectural building blocks `) is implemented by automated tool check. See `Tool Requirements `_. From a2b83eba0ba6e1129e4f91c7d7b358c8f4b53947 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 23 Feb 2026 11:06:28 +0100 Subject: [PATCH 2/4] fix review findings --- .../feature_name/architecture/chklst_arc_inspection.rst | 2 +- .../docs/architecture/chklst_arc_inspection.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst b/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst index 4c3bc8b887..531085afa1 100644 --- a/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst @@ -68,7 +68,7 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n * - ARC_01_02 - Does the software architecture design consider all the requirements allocated to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? - manual - - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g., use cases, functional safety requirements), non-functional requirements (e.g., performance, reliability), safety requirements (e.g., ASIL-related requirements), and security requirements (e.g., confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. + - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g. functional safety requirements), non-functional requirements (e.g. performance, reliability), and security requirements (e.g. confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. - - - diff --git a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst index b30470144d..8a71bd8d1b 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst @@ -66,9 +66,9 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - - * - ARC_01_02 - - Does the software architecture design consider all the requirements allocated to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? + - Does the software architecture design consider all the requirements allocated or belonging to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? - manual - - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g., use cases, functional safety requirements), non-functional requirements (e.g., performance, reliability), safety requirements (e.g., ASIL-related requirements), and security requirements (e.g., confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. + - Check if all requirements allocated or belonging to the architectural element are considered in the design. This includes functional requirements (e.g. functional safety requirements), non-functional requirements (e.g. performance, reliability), and security requirements (e.g. confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. - - - From 9e7648e8908b4d1acb59e92e21f2d07c14b7b068 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 23 Feb 2026 13:52:49 +0100 Subject: [PATCH 3/4] line fix --- .../component_name/docs/architecture/chklst_arc_inspection.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst index 8a71bd8d1b..6c5fe1bfca 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst @@ -58,8 +58,7 @@ Please note that it is mandatory to fill in the "passed" column with "yes" or "n - Remarks - Issue link * - ARC_01_01 - - Is the traceability from software architectural elements to requirements, and other level architectural - elements (e.g. component to interface) established according to the "Relations between the architectural elements" as described in :need:`doc_concept__arch_process`? + - Is the traceability from software architectural elements to requirements, and other level architectural elements (e.g. component to interface) established according to the "Relations between the architectural elements" as described in :need:`doc_concept__arch_process`? - automated - Trace should be checked automatically by tool support in the future. Will be removed from the checklist once the requirement (:need:`Correlations of the architectural building blocks `) is implemented. Refer to `Tool Requirements `_ for the current status. - From 3e503ac334df8de8e74f38e334d66ba633fba198 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 23 Feb 2026 14:07:07 +0100 Subject: [PATCH 4/4] fix table lines --- .../feature_name/architecture/chklst_arc_inspection.rst | 4 +--- .../docs/architecture/chklst_arc_inspection.rst | 2 -- 2 files changed, 1 insertion(+), 5 deletions(-) diff --git a/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst b/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst index 1494d455f4..2a7344cef5 100644 --- a/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/features/feature_name/architecture/chklst_arc_inspection.rst @@ -68,8 +68,7 @@ See also :need:`doc_concept__wp_inspections` for further information about revie - Remarks - Issue link * - ARC_01_01 - - Is the traceability from software architectural elements to requirements, and other level architectural - elements (e.g. component to interface) established according to the "Relations between the architectural elements" as described in :need:`doc_concept__arch_process`? + - Is the traceability from software architectural elements to requirements, and other level architectural elements (e.g. component to interface) established according to the "Relations between the architectural elements" as described in :need:`doc_concept__arch_process`? - Trace should be checked automatically by tool support in the future. It will be removed from the checklist once the requirement (:need:`Correlations of the architectural building blocks `) is implemented. Refer to `Tool Requirements `_ for the current status. - - @@ -80,7 +79,6 @@ See also :need:`doc_concept__wp_inspections` for further information about revie - Check if all requirements allocated to the architectural element are considered in the design. This includes functional requirements (e.g. functional safety requirements), non-functional requirements (e.g. performance, reliability), and security requirements (e.g. confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. - - - - * - ARC_01_03 - If the architectural element is related to any supplier manuals (including safety and security), are the relevant parts covered? - If the architecture makes use of supplied elements, their manuals (like safety) have to be considered (i.e. its provided functionality matches the expectation and assumptions are fulfilled). Note that in case of safety component this means that assumed Technical Safety Requirements and AoUs of the safety manual are covered. diff --git a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst index ad5097c08c..781ad63bd9 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst +++ b/process/folder_templates/modules/module_name/component_name/docs/architecture/chklst_arc_inspection.rst @@ -73,14 +73,12 @@ See also :need:`doc_concept__wp_inspections` for further information about revie - Trace should be checked automatically by tool support in the future. Will be removed from the checklist once the requirement (:need:`Correlations of the architectural building blocks `) is implemented. Refer to `Tool Requirements `_ for the current status. - - - - * - ARC_01_02 - Does the software architecture design consider all the requirements allocated or belonging to the architectural element, including functional, non-functional, safety, and security requirements and all related design decisions? - manual - Check if all requirements allocated or belonging to the architectural element are considered in the design. This includes functional requirements (e.g. functional safety requirements), non-functional requirements (e.g. performance, reliability), and security requirements (e.g. confidentiality, integrity). Additionally, ensure that all related design decisions are taken into account and documented in the architectural design. - - - - * - ARC_01_03 - If the architectural element is related to any supplier manuals (incl. safety and security) are the relevant parts covered?