From ce7947ab2dd7bdb3c5a755b401c487a963ec0ba1 Mon Sep 17 00:00:00 2001 From: "rahul.singh" Date: Mon, 23 Mar 2026 06:58:32 +0100 Subject: [PATCH 1/3] rename relations for Codebeamer compatibility --- .../feature_name/architecture/index.rst | 21 +-- .../feature_name/requirements/index.rst | 2 +- .../docs/architecture/index.rst | 10 +- .../docs/requirements/index.rst | 2 +- .../architecture_concept.rst | 144 +++++++++++++++--- .../guidance/architecture_process_reqs.rst | 42 ++--- .../guidance/change_management_reqs.rst | 22 +-- .../guidance/configuration_process_req.rst | 8 +- .../guidance/implementation_process_reqs.rst | 54 +++---- .../guidance/problem_resolution_reqs.rst | 24 +-- .../guidance/process_management_reqs.rst | 8 +- .../guidance/process_management_templates.rst | 2 +- .../guidance/quality_process_reqs.rst | 2 +- .../guidance/release_process_reqs.rst | 2 +- .../guidance/requirements_process_reqs.rst | 54 +++---- .../guidance/requirements_templates.rst | 12 ++ .../guidance/process_req.rst | 4 +- .../security_analysis_process_reqs.rst | 42 ++--- .../security_management_process_reqs.rst | 4 +- .../guidance/tool_management_reqs.rst | 14 +- .../guidance/verification_process_reqs.rst | 20 +-- 21 files changed, 303 insertions(+), 190 deletions(-) diff --git a/process/folder_templates/features/feature_name/architecture/index.rst b/process/folder_templates/features/feature_name/architecture/index.rst index 85aeed5e32..1ecc0067c1 100644 --- a/process/folder_templates/features/feature_name/architecture/index.rst +++ b/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$", "fulfils_back") + :filter: search("feat_arch_sta__archdes$", "satisfies_back") :colwidths: 70,30 .. needtable:: Overview of Feature Requirements :style: table :columns: title;id - :filter: search("feat_arch_sta__archdes$", "fulfils_back") + :filter: search("feat_arch_sta__archdes$", "satisfies_back") :colwidths: 70,30 @@ -80,24 +80,17 @@ 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 - :fulfils: feat_req__feature_name__some_title + :satisfies: 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 @@ -114,7 +107,7 @@ Dynamic Architecture :security: YES :safety: ASIL_B :status: invalid - :fulfils: feat_req__feature_name__some_title + :satisfies: feat_req__feature_name__some_title :belongs_to: feat__feature_name Put here a sequence diagram @@ -129,7 +122,7 @@ Logical Interfaces :security: YES :safety: ASIL_B :status: invalid - :fulfils: feat_req__feature_name__some_title + :satisfies: feat_req__feature_name__some_title General Interface Description diff --git a/process/folder_templates/features/feature_name/requirements/index.rst b/process/folder_templates/features/feature_name/requirements/index.rst index 0e98c7d280..481ae21c3b 100644 --- a/process/folder_templates/features/feature_name/requirements/index.rst +++ b/process/folder_templates/features/feature_name/requirements/index.rst @@ -41,7 +41,7 @@ Feature Requirements :reqtype: Process :security: NO :safety: ASIL_B - :satisfies: stkh_req__requirements__template + :derived_from: stkh_req__requirements__template :valid_from: v0.0.1 :valid_until: v1.0.1 :status: invalid diff --git a/process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst b/process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst index 4a660a35d3..3846b1e939 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst +++ b/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$", "fulfils_back") + :filter: search("comp_arch_sta__archdes$", "satisfies_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 - :fulfils: comp_req__component_name__some_title + :satisfies: 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 - :fulfils: comp_req__component_name__some_title + :satisfies: comp_req__component_name__some_title Put here a sequence diagram @@ -126,7 +126,7 @@ Interfaces :id: real_arc_int____ :security: <YES|NO> :safety: <QM|ASIL_B> - :fulfils: <link to component requirement id> + :satisfies: <link to component requirement id> :language: cpp Internal Components @@ -139,7 +139,7 @@ Internal Components :status: invalid :safety: ASIL_B :security: YES - :fulfils: comp_req__component_name__some_title + :satisfies: comp_req__component_name__some_title :belongs_to: comp__component_name_template No architecture but detailed design diff --git a/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst b/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst index d705cf1b44..82a5b2cf7f 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst +++ b/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst @@ -44,7 +44,7 @@ Component Requirements :reqtype: Process :security: YES :safety: ASIL_B - :satisfies: feat_req__feature_name__some_title + :derived_from: feat_req__feature_name__some_title :status: invalid :belongs_to: comp__component_name_template diff --git a/process/process_areas/architecture_design/architecture_concept.rst b/process/process_areas/architecture_design/architecture_concept.rst index f1e6c5fcbb..4538170ad4 100644 --- a/process/process_areas/architecture_design/architecture_concept.rst +++ b/process/process_areas/architecture_design/architecture_concept.rst @@ -123,8 +123,22 @@ The feature architecture contain the following views: Static View ----------- -The first viewpoint is named as *feature architecture*. It displays the SW Components within the SW modules (= dependable elements) which are required to realize the feature including their interactions. Also the *logical interfaces* and the interaction between the feature and the user are included in this view. On this architectural level the feature requirements shall be allocated. A full rendered example for the static architecture is maintained in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +The first viewpoint is named as *feature architecture*. It displays the SW Components within the SW modules (= dependable elements) which are required to realize the feature including their interactions. Also the *logical interfaces* and the interaction between the feature and the user are included in this view. On this architectural level the feature requirements shall be allocated. An example for the static architecture is shown here: + +.. feat_arc_sta:: Feature 1 Architecture + :id: feat_arc_sta__example_feature__feature_1 + :security: YES + :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 + :belongs_to: feat__example_feature + + .. needarch:: + :scale: 50 + :align: center + + {{ draw_feature(need(), needs) }} In all views, the components which are marked as ASIL_B related are drawn with red borders. @@ -150,8 +164,20 @@ See :ref:`uml_diagram_selection` in guideline for further information about the Interface View -------------- -On the feature level only *logical interfaces* shall be displayed. This means that only logical names shall be provided for both the interface and the operations within. Those *logical interfaces* shall be connected to component interfaces on the module view. A rendered logical-interface example is maintained in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +On the feature level only *logical interfaces* shall be displayed. This means that only logical names shall be provided for both the interface and the operations within. Those *logical interfaces* shall be connected to component interfaces on the module view. + +.. logic_arc_int:: Logical Interface 1 + :id: logic_arc_int__example_feature__archcon_logical_interface_1 + :security: YES + :safety: ASIL_B + :status: valid + :satisfies: feat_req__example_feature__archdes_example_req + + .. needarch:: + :scale: 50 + :align: center + + {{ draw_interface(need(), needs) }} SW Module View ============== @@ -171,8 +197,19 @@ Static View The *component architecture* describes the implementation of the functionalities in a white-box view. It describes the internal structure of SW components and their decomposition. It provides a more detailed information concerning the respective interfaces of a component. If a SW component interacts with a different component it is also included via a *use* relationship in the diagram. An example of the *component architecture* is displayed here: -A full rendered component-architecture example is maintained in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +.. comp_arc_sta:: Component 1 Static View + :id: comp_arc_sta__example_feature__archdes_component_concept_1 + :status: valid + :safety: ASIL_B + :security: NO + :satisfies: comp_req__example_feature__archex_example_req + :belongs_to: comp__component_example_1 + + .. needarch:: + :scale: 50 + :align: center + + {{ draw_component(need(), needs) }} The decomposition is optional and relies on the complexity of the component. Thus there is no graphic representation required for it. In all views the components which are marked as ASIL_B related are drawn in red color. @@ -197,8 +234,21 @@ Following scenarios should be included: Interface View -------------- -The component interface view shows the actual interfaces of the component. Also links to their corresponding logical interfaces are displayed in this view. A rendered component-interface example is maintained in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +The component interface view shows the actual interfaces of the component. Also links to their corresponding logical interfaces are displayed in this view: + +.. real_arc_int:: Component Interface 1 + :id: real_arc_int__example_feature__archdes_component_interface_1 + :status: valid + :safety: ASIL_B + :security: NO + :satisfies: comp_req__example_feature__archex_example_req + :language: cpp + + .. needarch:: + :scale: 50 + :align: center + + {{ draw_interface(need(), needs)}} Platform View ============= @@ -421,8 +471,29 @@ Here are some excerpts of UML diagrams made from the requirements of that file. Feature Architecture ^^^^^^^^^^^^^^^^^^^^ -The following section links to the rendered feature example that is now maintained in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +The following section is an example, how an `Feature <https://eclipse-score.github.io/score/main/features/index.html>`_ looks like and how the architecture of an Feature is described. Please note that components with an "ASIL_B" safety rating are highlighted with red borders in the diagram (e.g., "Component 1"). + +.. feat:: Feature Name + :id: feat__feature_name_example + :security: YES + :safety: ASIL_B + :status: invalid + :includes: logic_arc_int__example_feature__archex_logical_interface_1 + +.. feat_arc_sta:: Feature Static Architecture View - Rendered Example + :id: feat_arc_sta__example_feature__archdes_getstrt + :security: YES + :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 + :belongs_to: feat__example_feature + + .. needarch:: + :scale: 50 + :align: center + + {{ draw_feature(need(), needs) }} .. code-block:: rst @@ -440,7 +511,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 - :fulfils: feat_req__example_feature__archdes_example_req + :satisfies: feat_req__example_feature__archdes_example_req :belongs_to: feat__example_feature .. needarch:: @@ -454,8 +525,19 @@ 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/>`__. +.. comp_arc_sta:: Component Static View - Rendered Example + :id: comp_arc_sta__example_feature__component_getstrt + :status: valid + :safety: ASIL_B + :security: NO + :satisfies: comp_req__example_feature__archex_example_req + :belongs_to: comp__component_example_1 + + .. needarch:: + :scale: 50 + :align: center + + {{ draw_component( need(), needs ) }} .. code-block:: rst @@ -464,7 +546,7 @@ The rendered component examples are maintained in the :status: valid :safety: ASIL_B :security: NO - :fulfils: comp_req__example_feature__archex_example_req + :satisfies: comp_req__example_feature__archex_example_req :belongs_to: comp__component_component_getstrt .. needarch:: @@ -506,8 +588,20 @@ Besides storing the output it is also possible to display the generated PlantUML Debug example for component architecture: -See the rendered debug example in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +.. comp_arc_sta:: Component Static View - Rendered Debug Example + :id: comp_arc_sta__example_feature__component_getstrt_debug + :status: valid + :safety: ASIL_B + :security: NO + :satisfies: comp_req__example_feature__archex_example_req + :belongs_to: comp__component_example_1 + + .. needarch:: + :scale: 50 + :align: center + :debug: + + {{ draw_component( need(), needs ) }} .. _manual_addition_uml: @@ -536,8 +630,22 @@ To make *needuml* work we have to replace the *need()* call with a different fun } CM -> LI1: EXTRA_LINKAGE_MANUALLY_ADDED -See the rendered manual-edit example in the -`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. +.. comp_arc_sta:: Component Architecture Static View - Rendered Example Manually Edited + :id: comp_arc_sta__example_feature__component_manual_getstrt + :status: valid + :safety: ASIL_B + :security: NO + :uses: logic_arc_int__example_feature__archex_logical_interface_1 + :satisfies: comp_req__example_feature__archex_example_req + :belongs_to: comp__component_example_1 + + .. needarch:: + + {{ draw_component( needs.get('comp__component_example_1'), needs ) }} + + component "Component Manual" as CM { + } + CM -> logic_arc_int__example_feature__archex_logical_interface_1: EXTRA_LINKAGE_MANUALLY_ADDED You can add any layout or additional configuration you want before you call the *draw_xyz*. diff --git a/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst b/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst index 13f9df5991..dd7dbbc8d7 100644 --- a/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst +++ b/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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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,7 +241,7 @@ Checks for Architectural Design :id: gd_req__arch_linkage_security_trace :status: valid :tags: prio_2_automation, attribute, check - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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. @@ -249,7 +249,7 @@ Checks for Architectural Design :id: gd_req__arch_linkage_requirement :status: valid :tags: prio_1_automation, attribute, check - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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 - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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,7 +279,7 @@ Checks for Architectural Design :id: gd_req__arch_consistency_interf :status: valid :tags: prio_2_automation, model, check - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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. @@ -287,6 +287,6 @@ Checks for Architectural Design :id: gd_req__arch_consistency_dynamic :status: valid :tags: prio_3_automation, model, check - :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch + :derived_from: 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. diff --git a/process/process_areas/change_management/guidance/change_management_reqs.rst b/process/process_areas/change_management/guidance/change_management_reqs.rst index e05e1b2c97..cade3764f9 100644 --- a/process/process_areas/change_management/guidance/change_management_reqs.rst +++ b/process/process_areas/change_management/guidance/change_management_reqs.rst @@ -24,7 +24,7 @@ Change Request Attributes :id: gd_req__change_attr_uid :status: valid :tags: done_automation, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP1, std_req__iso26262__support_8411, std_req__iso26262__support_8421, std_req__iso26262__support_8432, std_req__iso26262__support_8453 Each Change Request shall have a unique ID. It shall be in an integer number. @@ -33,7 +33,7 @@ Change Request Attributes :id: gd_req__change_attr_status :status: valid :tags: done_automation, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP3, std_req__aspice_40__SUP-10-BP5, std_req__aspice_40__SUP-10-BP6, std_req__iso26262__support_8411, std_req__iso26262__support_8422, std_req__iso26262__support_8432, std_req__iso26262__support_8442 Each Change Request shall have a status: @@ -48,7 +48,7 @@ Change Request Attributes :id: gd_req__change_attr_title :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP1, std_req__iso26262__support_8411, std_req__iso26262__support_8422 Reason for the Change Request @@ -57,7 +57,7 @@ Change Request Attributes :id: gd_req__change_attr_impact_description :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8411, std_req__iso26262__support_8422, std_req__iso26262__support_8431, std_req__iso26262__support_8432, std_req__iso26262__support_8452, std_req__iso26262__support_8453 Exact description of the Change Request, including impact analysis on functional safety, @@ -67,7 +67,7 @@ Change Request Attributes :id: gd_req__change_attr_impact_safety :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8422 Each Change Request shall have a automotive safety integrity level (ASIL) identifier: @@ -79,7 +79,7 @@ Change Request Attributes :id: gd_req__change_attr_impact_security :status: valid :tags: prio_2_automation, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8422 Each Change Request shall have a security relevance identifier: @@ -91,7 +91,7 @@ Change Request Attributes :id: gd_req__change_attr_types :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP1 * Feature @@ -120,7 +120,7 @@ Change Request Attributes :id: gd_req__change_attr_affected_wp :status: draft :tags: attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP4, std_req__iso26262__support_8412, std_req__iso26262__support_8422, std_req__iso26262__support_8452, std_req__iso26262__support_8453 Links to the work products affected by the Change Request @@ -129,7 +129,7 @@ Change Request Attributes :id: gd_req__change_attr_milestone :status: valid :tags: done_automation, attribute, mandatory - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP6, std_req__iso26262__support_8413 Milestone until the Change Request must be implemented (used for prioritization) @@ -144,7 +144,7 @@ Change Request Checks :id: gd_req__change_attr_mandatory :status: valid :tags: prio_2_automation, attribute, check - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__iic-13-51 It shall be checked if all mandatory attributes for each Change Request @@ -166,7 +166,7 @@ Change Request Traceability Impact Analysis Tool :id: gd_req__change_tool_impact_analysis :status: valid :tags: prio_3_automation, check, tool - :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__iic-13-51 It shall be reported, which work products and elements are affected by adding a new diff --git a/process/process_areas/configuration_management/guidance/configuration_process_req.rst b/process/process_areas/configuration_management/guidance/configuration_process_req.rst index 6f366a26dd..46bfd4ebf7 100644 --- a/process/process_areas/configuration_management/guidance/configuration_process_req.rst +++ b/process/process_areas/configuration_management/guidance/configuration_process_req.rst @@ -20,7 +20,7 @@ Configuration Management Process Requirements :status: valid :tags: done_automation, config_mgt :complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8 - :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch, wf__mr_saf_analyses_dfa, wf__vy_saf_analyses_dfa, wf__platform_mr_im_platform_mgmt_plan + :derived_from: wf__monitor_verify_requirements, wf__mr_vy_arch, wf__mr_saf_analyses_dfa, wf__vy_saf_analyses_dfa, wf__platform_mr_im_platform_mgmt_plan The Docs-as-Code tool shall check that the Id's of the configuration items (documented in doc-as-code) are unique. @@ -31,7 +31,7 @@ Configuration Management Process Requirements :status: valid :tags: prio_3_automation, config_mgt :complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8 - :satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note + :derived_from: wf__rel_platform_rel_note, wf__rel_mod_rel_note At least every platform release shall be stored permanently as a collection of text documents (docs and code) including the used OSS tooling on project owned servers. @@ -44,7 +44,7 @@ Configuration Management Process Requirements :status: valid :tags: prio_2_automation, config_mgt :complies: std_req__iso26262__support_6433, std_req__iso26262__software_7414 - :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch + :derived_from: wf__monitor_verify_requirements, wf__mr_vy_arch The content of pull requests (conversation, commits, files changed) shall be stored permanently for every release. @@ -56,7 +56,7 @@ Configuration Management Process Requirements :status: valid :tags: prio_2_automation, config_mgt :complies: std_req__iso26262__support_741 - :satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note + :derived_from: wf__rel_platform_rel_note, wf__rel_mod_rel_note It shall be possible to show the differences between two baselines. diff --git a/process/process_areas/implementation/guidance/implementation_process_reqs.rst b/process/process_areas/implementation/guidance/implementation_process_reqs.rst index 9b78eddd09..a85ffd3284 100644 --- a/process/process_areas/implementation/guidance/implementation_process_reqs.rst +++ b/process/process_areas/implementation/guidance/implementation_process_reqs.rst @@ -19,7 +19,7 @@ Process Requirements :id: gd_req__impl_static_diagram :status: valid :tags: manual_prio_1, mandatory - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP1 The static diagram shall represent the unit and their relationships using UML notations. @@ -31,7 +31,7 @@ Diagram Attributes :id: gd_req__impl_diagram_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP2 Each diagram shall have a unique ID. It shall consist of three parts: @@ -46,7 +46,7 @@ Diagram Attributes :id: gd_req__impl_diagram_title :status: valid :tags: manual_prio_1 attribute, mandatory - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP3, std_req__aspice_40__SWE-3-BP4 The title of the diagram shall provide a short summary of the description, but is not an "additional" requirement. @@ -57,7 +57,7 @@ Diagram Attributes :id: gd_req__impl_diagram_security :status: valid :tags: manual_prio_2, attribute, mandatory - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall have a security relevance identifier: @@ -69,7 +69,7 @@ Diagram Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall have a automotive safety integrity level (ASIL) identifier: @@ -81,7 +81,7 @@ Diagram Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall have a status: @@ -93,7 +93,7 @@ Diagram Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall have a description. The description shall provide a needarch or image of the diagram. @@ -107,7 +107,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__aspice_40__iic-13-51 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be linked to the corresponding component requirement via the attribute implements. @@ -116,7 +116,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding component requirement via the "implemented by" linkage. @@ -125,7 +125,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__aspice_40__iic-13-51 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be linked to the corresponding component architecture via the attribute satisfies. @@ -134,7 +134,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding component architecture via the "satisfied by" linkage. @@ -143,7 +143,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be linked to the corresponding component id via the attribute belongs_to. @@ -152,7 +152,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding component id via the "belongs by" linkage. @@ -161,7 +161,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be linked to the corresponding - SW Unit @@ -173,7 +173,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding - SW Unit @@ -188,7 +188,7 @@ Diagram Checks :status: valid :tags: prio_2_automation, attribute, check :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design It shall be checked if all mandatory attributes for each diagram are provided by the user. For all diagrams following attributes shall be mandatory: @@ -205,7 +205,7 @@ Unit Attributes :id: gd_req__impl_unit_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 Each unit shall have a unique ID. It shall consist of three parts: @@ -221,7 +221,7 @@ Unit Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each unit shall have a description. @@ -233,7 +233,7 @@ Unit Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each unit shall be linked to the corresponding component id via the attribute belongs_to. @@ -242,7 +242,7 @@ Unit Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each unit shall be automatically linked (inverse direction) to the corresponding component id via the "belongs by" linkage. @@ -253,7 +253,7 @@ Interface Attributes :id: gd_req__impl_interface_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 Each interface shall have a unique ID. It shall consist of three parts: @@ -269,7 +269,7 @@ Interface Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each interface shall have a description. @@ -281,7 +281,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each interface shall be linked to the corresponding SW Unit id via the attribute belongs_to. @@ -290,7 +290,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each interface shall be automatically linked (inverse direction) to the corresponding SW Unit id via the "belongs by" linkage. @@ -299,7 +299,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each interface shall be linked to the corresponding architecture via the attribute implements. @@ -308,7 +308,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__sw_detailed_design + :derived_from: wf__sw_detailed_design Each interface shall be automatically linked (inverse direction) to the corresponding architecture via the "implemented by" linkage. @@ -319,7 +319,7 @@ Dependency Analysis :id: gd_req__impl_dependency_analysis :status: valid :tags: prio_2_automation - :satisfies: wf__sw_verify_implementation + :derived_from: wf__sw_verify_implementation :complies: std_req__iso26262__software_942 For each component a dependency tree view shall be created to support design inspection and Safety Analysis. diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst index 5f4b1fdd45..1cf2e5d1db 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst @@ -26,7 +26,7 @@ Problem Attributes :id: gd_req__problem_attr_uid :status: valid :tags: done_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a unique ID. It shall be in an integer number. @@ -35,7 +35,7 @@ Problem Attributes :id: gd_req__problem_attr_status :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a status: @@ -50,7 +50,7 @@ Problem Attributes :id: gd_req__problem_attr_title :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Reason for Problem Report @@ -59,7 +59,7 @@ Problem Attributes :id: gd_req__problem_attr_impact_description :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 Exact description of the Problem, including potential cause and impact of the problem. @@ -73,7 +73,7 @@ Problem Attributes :id: gd_req__problem_attr_analysis_results :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP2 Record analysis results (e.g. reason for rejection, safety, security, quality impact) as comments. @@ -82,7 +82,7 @@ Problem Attributes :id: gd_req__problem_attr_stakeholder :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP5 Assign responsible stakeholder for analyzing the problem @@ -92,7 +92,7 @@ Problem Attributes :id: gd_req__problem_attr_classification :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 Each Problem shall have a classification identifier: @@ -106,7 +106,7 @@ Problem Attributes :id: gd_req__problem_attr_safety_affected :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a safety relevance identifier: @@ -120,7 +120,7 @@ Problem Attributes :id: gd_req__problem_attr_security_affected :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a security relevance identifier: @@ -134,7 +134,7 @@ Problem Attributes :id: gd_req__problem_attr_milestone :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP6 Milestone until the Problem must be implemented (used for prioritization) @@ -147,7 +147,7 @@ Problem Resolution Checks :id: gd_req__problem_check_mandatory :status: valid :tags: prio_2_automation, problem_resolution, attribute, check - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 It shall be checked if all mandatory attributes for each Problem @@ -165,7 +165,7 @@ Problem Resolution Checks :id: gd_req__problem_check_closing :status: valid :tags: prio_1_automation, problem_resolution, attribute, check - :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 ISSUEs related to Problem Reports shall not automatically closed, if linked ISSUEs or PRs are closed or merged and diff --git a/process/process_areas/process_management/guidance/process_management_reqs.rst b/process/process_areas/process_management/guidance/process_management_reqs.rst index a1161eb942..ee8a88fb1d 100644 --- a/process/process_areas/process_management/guidance/process_management_reqs.rst +++ b/process/process_areas/process_management/guidance/process_management_reqs.rst @@ -23,7 +23,7 @@ Process Requirements :id: gd_req__process_management_build_blocks :status: valid :tags: done_automation, attribute, mandatory - :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 The process model building blocks are defined. Compare also the process model @@ -67,7 +67,7 @@ Process Building Blocks Attributes :id: gd_req__process_management_build_blocks_attr :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 Each building block shall have defined attributes as defined here: @@ -89,7 +89,7 @@ Process Building Blocks Linkage :id: gd_req__process_management_build_blocks_link :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 Each building block shall have defined links as defined here: @@ -103,7 +103,7 @@ Process Building Blocks Checks :id: gd_req__process_management_build_blocks_check :status: valid :tags: done_automation - :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 It shall be checked, that all attributes defined here diff --git a/process/process_areas/process_management/guidance/process_management_templates.rst b/process/process_areas/process_management/guidance/process_management_templates.rst index 8235ffd31c..6f8a5b22d4 100644 --- a/process/process_areas/process_management/guidance/process_management_templates.rst +++ b/process/process_areas/process_management/guidance/process_management_templates.rst @@ -175,7 +175,7 @@ Templates :id: gd_req__<process area or abbreviation>_<...> :status: <draft|valid> :tags: <process area or abbreviation> - :satisfies: <defined workflow:wf__<...>>, ..., <defined workflow:wf__<...>> + :derived_from: <defined workflow:wf__<...>>, ..., <defined workflow:wf__<...>> :complies: <standard requirement:std_req__<...>>, ..., <standard requirement:std_req__<...>> diff --git a/process/process_areas/quality_management/guidance/quality_process_reqs.rst b/process/process_areas/quality_management/guidance/quality_process_reqs.rst index ce3662bb49..995611e561 100644 --- a/process/process_areas/quality_management/guidance/quality_process_reqs.rst +++ b/process/process_areas/quality_management/guidance/quality_process_reqs.rst @@ -19,7 +19,7 @@ Process Requirements :id: gd_req__quality_report :status: valid :tags: prio_3_automation, quality_management - :satisfies: wf__mr_imp_qlm_plan_processes + :derived_from: wf__mr_imp_qlm_plan_processes :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6 | The quality report shall be generated progressively and automatically compiling the work products. diff --git a/process/process_areas/release_management/guidance/release_process_reqs.rst b/process/process_areas/release_management/guidance/release_process_reqs.rst index 7c1a77b651..5c9a0d250e 100644 --- a/process/process_areas/release_management/guidance/release_process_reqs.rst +++ b/process/process_areas/release_management/guidance/release_process_reqs.rst @@ -19,7 +19,7 @@ Process Requirements :id: gd_req__release_note :status: valid :tags: prio_2_automation, release_management - :satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note + :derived_from: wf__rel_platform_rel_note, wf__rel_mod_rel_note :complies: std_req__iso26262__management_64134, std_req__iso26262__management_64135, std_req__aspice_40__SUP-8-BP7 | The release note shall be generated progressively and automatically compiling the content as far as possible. diff --git a/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst b/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst index 7562994e53..1ed48163aa 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst @@ -21,7 +21,7 @@ Process Requirements :id: gd_req__req_structure :status: valid :tags: done_automation, structure - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432 Requirements shall be hierarchically grouped into three levels. @@ -46,7 +46,7 @@ Process Requirement Attributes :id: gd_req__req_attr_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6432 Each requirement shall have a unique ID. It shall consist of three parts: @@ -61,7 +61,7 @@ Process Requirement Attributes :id: gd_req__req_attr_title :status: valid :tags: manual_prio_1 attribute, mandatory - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6424 The title of the requirement shall provide a short summary of the description, but is not an "additional" requirement. @@ -72,7 +72,7 @@ Process Requirement Attributes :id: gd_req__req_attr_description :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6424 Each requirement shall have a description. @@ -87,7 +87,7 @@ Process Requirement Attributes :id: gd_req__req_attr_type :status: valid :tags: manual_prio_2, attribute, mandatory - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__aspice_40__iic-17-00 Each requirement, apart from process and tool requirements, shall have a type of one of following options: @@ -101,7 +101,7 @@ Process Requirement Attributes :id: gd_req__req_attr_security :status: valid :tags: manual_prio_2, attribute, mandatory - :satisfies: wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou Each requirement, apart from process and tool requirements, shall have a security relevance identifier: @@ -113,7 +113,7 @@ Process Requirement Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou Each requirement, apart from process and tool requirements, shall have a automotive safety integrity level (ASIL) identifier: @@ -125,7 +125,7 @@ Process Requirement Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6425 - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou Each requirement, apart from process and tool requirements, shall have a status: @@ -136,7 +136,7 @@ Process Requirement Attributes :id: gd_req__req_attr_rationale :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__req_stkh_req + :derived_from: wf__req_stkh_req Each stakeholder requirement shall provide an attribute called rationale. The rationale shall contain the reason why the requirement is needed. @@ -145,7 +145,7 @@ Process Requirement Attributes :id: gd_req__req_attr_valid_from :status: valid :tags: manual_prio_2, attribute - :satisfies: wf__req_stkh_req, wf__req_feat_req + :derived_from: wf__req_stkh_req, wf__req_feat_req :complies: std_req__aspice_40__SWE-1-BP2, std_req__aspice_40__iic-17-54 Stakeholder and feature requirements can have a validity attribute that tells @@ -161,7 +161,7 @@ Process Requirement Attributes :id: gd_req__req_attr_valid_until :status: valid :tags: manual_prio_2, attribute - :satisfies: wf__req_stkh_req, wf__req_feat_req + :derived_from: wf__req_stkh_req, wf__req_feat_req :complies: std_req__aspice_40__SWE-1-BP2, std_req__aspice_40__iic-17-54 Stakeholder and feature requirements can have a validity attribute that tells @@ -183,7 +183,7 @@ Process Requirement Linkage :status: valid :tags: manual_prio_1, attribute :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5 - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool Requirements shall be linked to its adjacent level via the attribute derived_from. @@ -196,7 +196,7 @@ Process Requirement Linkage :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 + :derived_from: wf__req_feat_req, wf__req_comp_req Requirements shall be linked to AoU via the attribute covers, if they already cover these. @@ -211,7 +211,7 @@ Process Requirement Linkage :status: valid :tags: done_automation, attribute :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5 - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool Bi-directional traceability shall be provided by adding a "back-link" via attribute derives (i.e. make a <-> out of the <- in :need:`gd_req__req_linkage`). @@ -220,7 +220,7 @@ Process Requirement Linkage :status: valid :tags: manual_prio_1, attribute :complies: std_req__iso26262__support_6423, std_req__aspice_40__iic-13-51 - :satisfies: wf__req_stkh_req, wf__req_feat_req + :derived_from: wf__req_stkh_req, wf__req_feat_req It shall be possible to specify the requirement coverage, meaning the requirement is covered fully by its linked children. @@ -231,7 +231,7 @@ Process Requirement Linkage :id: gd_req__req_attr_impl :status: valid :tags: prio_2_automation, attribute - :satisfies: wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_feat_req, wf__req_comp_req It shall be possible to link requirements to code (to the respective line of code in an attribute of the requirement). @@ -239,7 +239,7 @@ Process Requirement Linkage :id: gd_req__req_attr_testlink :status: valid :tags: prio_1_automation, attribute - :satisfies: wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6433, std_req__iso26262__software_944 It shall be possible to link requirements to tests and automatically include a link to the test case in the attribute testlink. @@ -248,7 +248,7 @@ Process Requirement Linkage :id: gd_req__req_attr_test_covered :status: valid :tags: manual_prio_1, attribute - :satisfies: wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6433, std_req__iso26262__software_944, std_req__aspice_40__iic-13-51 It shall be possible to specify if a requirement is completely satisfied by the linked test case(s). @@ -260,7 +260,7 @@ Process Requirement Linkage :id: gd_req__req_attr_version :status: valid :tags: prio_1_automation, attribute - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6434 A versioning for requirements shall be provided. For this all mandatory attributes shall be taken into account: see :need:`gd_req__req_check_mandatory` @@ -274,7 +274,7 @@ Process Requirements Checks :id: gd_req__req_suspicious :status: valid :tags: prio_2_automation, check - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6434, std_req__aspice_40__iic-13-51 Based on the requirement versioning it shall be checked if a parent requirement was updated but not the linked child requirements (or tests). @@ -286,7 +286,7 @@ Process Requirements Checks :id: gd_req__req_check_mandatory :status: valid :tags: done_automation, check - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou It shall be checked if all mandatory attributes for each requirement is provided by the user. For all requirements following attributes shall be mandatory: @@ -302,7 +302,7 @@ Process Requirements Checks :id: gd_req__req_desc_weak :status: valid :tags: done_automation, check - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou It shall be ensured that no *weak words* are contained in the requirement description for: @@ -319,7 +319,7 @@ Process Requirements Checks :status: valid :tags: done_automation, check :complies: std_req__iso26262__support_6432, std_req__aspice_40__iic-13-51 - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req Every feature- and component requirement shall be linked to at least one parent requirement according to the defined traceability scheme: @@ -330,7 +330,7 @@ Process Requirements Checks :status: valid :tags: prio_2_automation, check :complies: std_req__iso26262__support_6423 - :satisfies: wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_feat_req, wf__req_comp_req It shall be checked if every feature- and component requirement is linked at least to one valid architectural element on the same level. This should also include requirement type checking: @@ -346,7 +346,7 @@ Process Requirements Checks :status: valid :tags: prio_2_automation, check :complies: std_req__iso26262__support_6423 - :satisfies: wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_feat_req, wf__req_comp_req The check :need:`gd_req__req_linkage_architecture` shall only be enabled for a release build, otherwise it would block creating requirements first without architecture. @@ -354,7 +354,7 @@ Process Requirements Checks :id: gd_req__req_linkage_safety :status: valid :tags: done_automation, check - :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6422 It shall be checked that (child) QM requirements (Safety == QM) can not be linked against a (parent) safety requirement (Safety != QM). @@ -365,7 +365,7 @@ Process Requirements Checks :id: gd_req__req_validity :status: valid :tags: prio_3_automation, check - :satisfies: wf__req_stkh_req, wf__req_feat_req + :derived_from: wf__req_stkh_req, wf__req_feat_req Validity attributes (:need:`gd_req__req_attr_valid_from` and :need:`gd_req__req_attr_valid_until`) shall be checked for correctness (i.e. they denote an existing milestone) and consistent (e.g. the until is not before from) Several of the above checks are not to be executed on requirements not valid in the next milestone, these are TBD diff --git a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst index 54b95bc70e..38e4692744 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst @@ -49,6 +49,18 @@ Templates See the Assumption of Use requirement snippets in the `module template documentation <https://eclipse-score.github.io/module_template/aou_requirements_template.html>`__. +.. gd_temp:: Process Requirements Template + :id: gd_temp__req_process_req + :status: valid + :complies: std_req__iso26262__support_641, std_req__iso26262__support_6421, std_req__iso26262__support_6425 + + .. code-block:: rst + + .. gd_req:: <Title> + :id: gd_req__<process>__<Title> + :derived_from: <link to guidance id> + :complies: <link to standard requirement> + :status: <valid|invalid> .. gd_temp:: Tool Requirements Template :id: gd_temp__req_tool_req diff --git a/process/process_areas/safety_management/guidance/process_req.rst b/process/process_areas/safety_management/guidance/process_req.rst index 5ae83d9ca9..c3b32fe119 100644 --- a/process/process_areas/safety_management/guidance/process_req.rst +++ b/process/process_areas/safety_management/guidance/process_req.rst @@ -20,7 +20,7 @@ Safety Management Process Requirements :status: valid :tags: done_automation :complies: std_req__iso26262__management_6468 - :satisfies: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual + :derived_from: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual Safety plans shall contain documents references where the status is derived automatically. @@ -31,7 +31,7 @@ Safety Management Process Requirements :status: valid :tags: prio_2_automation :complies: std_req__iso26262__management_6468 - :satisfies: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual + :derived_from: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual Safety plans shall contain work product references where the accumulated status is derived automatically. diff --git a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst index a49e767e9e..28cc47d01e 100644 --- a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst +++ b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst @@ -25,7 +25,7 @@ Security Analysis Process Requirements :id: gd_req__sec_structure :status: valid :tags: done_automation, security_analysis - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8321, std_req__isosae21434__continual_8621, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Security Analysis shall be hierarchically grouped into different levels. @@ -45,7 +45,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_uid :status: valid :tags: done_automation, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8321 Each Security Analysis shall have a unique ID. It shall be in a format which is also human readable and consists of @@ -60,7 +60,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_title :status: valid :tags: manual_prio_1, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8321 The title of the Security Analysis shall provide a short summary of the description @@ -69,7 +69,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_mitigated_by :status: valid :tags: prio_1_automation, attribute, optional - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Each threat shall have an associated treatment (accept, avoid, reduce, share) or AoU. @@ -80,7 +80,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_mitigation_issue :status: valid :tags: prio_1_automation, attribute, optional - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8322, std_req__isosae21434__continual_8323, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15921 If a new security mitigation (avoid, reduce, or share) is needed, link to the issue and keep status invalid until the mitigation is sufficient. @@ -89,7 +89,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_sufficient :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 The mitigation(s) shall be rated as sufficient with <yes> or <no>. @@ -99,7 +99,7 @@ Process Security Analysis Attributes :id: gd_req__sec_argument :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8421, std_req__isosae21434__continual_8521, std_req__isosae21434__continual_8522, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 The argument shall describe why the mitigation is sufficient or not. If it is not sufficient, the argument shall describe how the mitigation @@ -109,7 +109,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_status :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8322, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15921 Each Security Analysis shall have the status invalid until the analysis is finished. @@ -119,7 +119,7 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_teffect :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8321, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Every Security Analysis shall have a short description of the threat impact @@ -134,7 +134,7 @@ Security Analysis Linkage :id: gd_req__sec_linkage_check :status: valid :tags: prio_1_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Security Analysis shall be linked to the architecture view on the corresponding level @@ -144,7 +144,7 @@ Security Analysis Linkage :id: gd_req__sec_linkage :status: valid :tags: prio_2_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Each Security Analysis shall be automatically linked (inverse direction) to the @@ -154,7 +154,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_requirements_check :status: valid :tags: prio_1_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Security Analysis shall be linked to a requirement on the corresponding level via @@ -164,7 +164,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_requirements :status: valid :tags: prio_2_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Each Security Analysis shall be automatically linked to the corresponding Security @@ -174,7 +174,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_aou :status: valid :tags: prio_1_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be possible to link AoU. @@ -183,7 +183,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_ver :status: valid :tags: prio_2_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be possible to detect any differences in mandatory attributes compared to @@ -193,7 +193,7 @@ Security Analysis Linkage :id: gd_req__sec_linkage_status_check :status: valid :tags: prio_3_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be checked that the Security Analysis can only be linked against valid @@ -209,7 +209,7 @@ Security Analysis Checks :id: gd_req__sec_attr_mandatory :status: valid :tags: prio_1_automation, attribute, check - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__continual_8621, It shall be checked if all mandatory attributes for each Security Analysis are @@ -226,7 +226,7 @@ Security Analysis Checks :id: gd_req__sec_linkage_security :status: valid :tags: prio_2_automation, attribute, check - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be checked that Security Analysis can only be linked via mitigate_by against @@ -238,7 +238,7 @@ Security Analysis Checks :id: gd_req__sec_finalization_check :status: valid :tags: prio_2_automation, attribute, automated - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be checked if all artifacts of the analysis are "valid" and "sufficient". @@ -250,7 +250,7 @@ Threat Scenario Security Process Requirements :id: gd_req__sec_attr_threat_scenario_id :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Each threat scenario used for the Security Analysis shall have a threat scenario ID. @@ -266,7 +266,7 @@ Threat Models Process Requirements :id: gd_req__sec_attr_stride_threat_id :status: valid :tags: prio_1_automation, attribute, mandatory - :satisfies: wf__analyse_sec_featarch, wf__analyse_sec_comparch + :derived_from: wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Each threat used for Security Analysis shall have a threat ID. The threat ID is used diff --git a/process/process_areas/security_management/guidance/security_management_process_reqs.rst b/process/process_areas/security_management/guidance/security_management_process_reqs.rst index 0d5e01cb3a..8342bc5350 100644 --- a/process/process_areas/security_management/guidance/security_management_process_reqs.rst +++ b/process/process_areas/security_management/guidance/security_management_process_reqs.rst @@ -20,7 +20,7 @@ Security Management Process Requirements :id: gd_req__security_doc_status :status: valid :tags: done_automation, attribute, mandatory - :satisfies: wf__cr_mt_security_plan + :derived_from: wf__cr_mt_security_plan :complies: std_req__isosae21434__prj_management_6429 Security Plans shall contain documents references where the status is derived automatically. @@ -31,7 +31,7 @@ Security Management Process Requirements :id: gd_req__security_wp_status :status: valid :tags: prio_2_automation, attribute, mandatory - :satisfies: wf__cr_mt_security_plan + :derived_from: wf__cr_mt_security_plan :complies: std_req__isosae21434__prj_management_6429 Security Plans shall contain work product references where the accumulated status is derived automatically. diff --git a/process/process_areas/tool_management/guidance/tool_management_reqs.rst b/process/process_areas/tool_management/guidance/tool_management_reqs.rst index 86456eb44a..dc4dfee16a 100644 --- a/process/process_areas/tool_management/guidance/tool_management_reqs.rst +++ b/process/process_areas/tool_management/guidance/tool_management_reqs.rst @@ -26,7 +26,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_uid :status: valid :tags: done_automation, tool_management, attribute, mandatory - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a unique ID. @@ -35,7 +35,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_status :status: valid :tags: prio_1_automation, tool_management, attribute, mandatory - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a status. @@ -50,7 +50,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_version :status: valid :tags: manual_prio_1, tool_management, attribute, mandatory - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a version: @@ -61,7 +61,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_tcl :status: valid :tags: manual_prio_1, tool_management, attribute, mandatory - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a tool confidence level: @@ -73,7 +73,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_safety_affected :status: valid :tags: manual_prio_1, tool_management, attribute, mandatory - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a safety relevance identifier: @@ -85,7 +85,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_security_affected :status: valid :tags: manual_prio_2, tool_management, attribute, mandatory - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__isosae21434__org_management_5451, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a security relevance identifier: @@ -101,7 +101,7 @@ Tool Verification Report Checks :id: gd_req__tool_check_mandatory :status: valid :tags: prio_1_automation, tool_management, attribute, check - :satisfies: wf__tool_create_tool_verification_report + :derived_from: wf__tool_create_tool_verification_report :complies: std_req__aspice_40__SUP-8-BP1 It shall be checked if all mandatory attributes for each Tool Verification Report diff --git a/process/process_areas/verification/guidance/verification_process_reqs.rst b/process/process_areas/verification/guidance/verification_process_reqs.rst index 29c22d10ed..bc6c578b9f 100644 --- a/process/process_areas/verification/guidance/verification_process_reqs.rst +++ b/process/process_areas/verification/guidance/verification_process_reqs.rst @@ -21,7 +21,7 @@ Process Requirements :id: gd_req__verification_link_tests :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432 @@ -53,7 +53,7 @@ Process Requirements :id: gd_req__verification_link_tests_cpp :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 @@ -68,7 +68,7 @@ Process Requirements :id: gd_req__verification_link_tests_python :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 @@ -90,7 +90,7 @@ Process Requirements :id: gd_req__verification_link_tests_rust :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 For linking Rust tests to requirements **#[record_property]** shall be used: @@ -101,7 +101,7 @@ Process Requirements :id: gd_req__verification_independence :status: valid :tags: done_automation, verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 The approver of a pull request shall differ from the author(s) of the pull request in all pull requests. @@ -110,7 +110,7 @@ Process Requirements :id: gd_req__verification_reporting :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_mod_ver_report + :derived_from: wf__verification_mod_ver_report :complies: The tool automation shall automatically generate the Verification reports. @@ -121,7 +121,7 @@ Process Requirements :id: gd_req__verification_report_archiving :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_mod_ver_report + :derived_from: wf__verification_mod_ver_report :complies: The tool automation shall automatically archive the Verification reports for releases. @@ -131,7 +131,7 @@ Process Requirements :id: gd_req__verification_checks :status: valid :tags: prio_1_automation, verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: The following checks shall be implemented on test metadata: @@ -147,7 +147,7 @@ Process Requirements :id: gd_req__verification_checks_extended :status: draft :tags: verification - :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: The following checks shall be implemented on test metadata: @@ -159,7 +159,7 @@ Process Requirements :id: gd_req__verification_external_aou :status: valid :tags: prio_2_automation, verification - :satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test + :derived_from: wf__verification_comp_int_test, wf__verification_feat_int_test :complies: External components AoUs shall be verified by integration tests or static analysis tooling. From 09e30ff62afc97123c0aa819f73d3cc3e2164d1d Mon Sep 17 00:00:00 2001 From: "rahul.singh" <rahul.sa.singh@partner.bmwgroup.com> Date: Fri, 10 Apr 2026 14:21:50 +0200 Subject: [PATCH 2/3] remove out-of-scope gd_req and inline example changes --- .../general_concepts/score_review_concept.rst | 10 +- .../architecture_concept.rst | 142 ++---------------- .../guidance/process_management_templates.rst | 2 +- .../guidance/requirements_templates.rst | 4 +- .../security_analysis_process_reqs.rst | 24 +-- 5 files changed, 36 insertions(+), 146 deletions(-) diff --git a/process/general_concepts/score_review_concept.rst b/process/general_concepts/score_review_concept.rst index 920a2ff1f1..2fcc454678 100644 --- a/process/general_concepts/score_review_concept.rst +++ b/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 - :satisfies: wf__monitor_verify_requirements + :derived_from: 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 - :satisfies: wf__mr_vy_arch + :derived_from: 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 - :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch + :derived_from: 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 - :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch + :derived_from: 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 - :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch + :derived_from: 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). diff --git a/process/process_areas/architecture_design/architecture_concept.rst b/process/process_areas/architecture_design/architecture_concept.rst index 4538170ad4..18bd9a5ff6 100644 --- a/process/process_areas/architecture_design/architecture_concept.rst +++ b/process/process_areas/architecture_design/architecture_concept.rst @@ -123,22 +123,8 @@ The feature architecture contain the following views: Static View ----------- -The first viewpoint is named as *feature architecture*. It displays the SW Components within the SW modules (= dependable elements) which are required to realize the feature including their interactions. Also the *logical interfaces* and the interaction between the feature and the user are included in this view. On this architectural level the feature requirements shall be allocated. An example for the static architecture is shown here: - -.. feat_arc_sta:: Feature 1 Architecture - :id: feat_arc_sta__example_feature__feature_1 - :security: YES - :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 - :belongs_to: feat__example_feature - - .. needarch:: - :scale: 50 - :align: center - - {{ draw_feature(need(), needs) }} +The first viewpoint is named as *feature architecture*. It displays the SW Components within the SW modules (= dependable elements) which are required to realize the feature including their interactions. Also the *logical interfaces* and the interaction between the feature and the user are included in this view. On this architectural level the feature requirements shall be allocated. A full rendered example for the static architecture is maintained in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. In all views, the components which are marked as ASIL_B related are drawn with red borders. @@ -164,20 +150,8 @@ See :ref:`uml_diagram_selection` in guideline for further information about the Interface View -------------- -On the feature level only *logical interfaces* shall be displayed. This means that only logical names shall be provided for both the interface and the operations within. Those *logical interfaces* shall be connected to component interfaces on the module view. - -.. logic_arc_int:: Logical Interface 1 - :id: logic_arc_int__example_feature__archcon_logical_interface_1 - :security: YES - :safety: ASIL_B - :status: valid - :satisfies: feat_req__example_feature__archdes_example_req - - .. needarch:: - :scale: 50 - :align: center - - {{ draw_interface(need(), needs) }} +On the feature level only *logical interfaces* shall be displayed. This means that only logical names shall be provided for both the interface and the operations within. Those *logical interfaces* shall be connected to component interfaces on the module view. A rendered logical-interface example is maintained in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. SW Module View ============== @@ -197,19 +171,8 @@ Static View The *component architecture* describes the implementation of the functionalities in a white-box view. It describes the internal structure of SW components and their decomposition. It provides a more detailed information concerning the respective interfaces of a component. If a SW component interacts with a different component it is also included via a *use* relationship in the diagram. An example of the *component architecture* is displayed here: -.. comp_arc_sta:: Component 1 Static View - :id: comp_arc_sta__example_feature__archdes_component_concept_1 - :status: valid - :safety: ASIL_B - :security: NO - :satisfies: comp_req__example_feature__archex_example_req - :belongs_to: comp__component_example_1 - - .. needarch:: - :scale: 50 - :align: center - - {{ draw_component(need(), needs) }} +A full rendered component-architecture example is maintained in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. The decomposition is optional and relies on the complexity of the component. Thus there is no graphic representation required for it. In all views the components which are marked as ASIL_B related are drawn in red color. @@ -234,21 +197,8 @@ Following scenarios should be included: Interface View -------------- -The component interface view shows the actual interfaces of the component. Also links to their corresponding logical interfaces are displayed in this view: - -.. real_arc_int:: Component Interface 1 - :id: real_arc_int__example_feature__archdes_component_interface_1 - :status: valid - :safety: ASIL_B - :security: NO - :satisfies: comp_req__example_feature__archex_example_req - :language: cpp - - .. needarch:: - :scale: 50 - :align: center - - {{ draw_interface(need(), needs)}} +The component interface view shows the actual interfaces of the component. Also links to their corresponding logical interfaces are displayed in this view. A rendered component-interface example is maintained in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. Platform View ============= @@ -471,29 +421,8 @@ Here are some excerpts of UML diagrams made from the requirements of that file. Feature Architecture ^^^^^^^^^^^^^^^^^^^^ -The following section is an example, how an `Feature <https://eclipse-score.github.io/score/main/features/index.html>`_ looks like and how the architecture of an Feature is described. Please note that components with an "ASIL_B" safety rating are highlighted with red borders in the diagram (e.g., "Component 1"). - -.. feat:: Feature Name - :id: feat__feature_name_example - :security: YES - :safety: ASIL_B - :status: invalid - :includes: logic_arc_int__example_feature__archex_logical_interface_1 - -.. feat_arc_sta:: Feature Static Architecture View - Rendered Example - :id: feat_arc_sta__example_feature__archdes_getstrt - :security: YES - :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 - :belongs_to: feat__example_feature - - .. needarch:: - :scale: 50 - :align: center - - {{ draw_feature(need(), needs) }} +The following section links to the rendered feature example that is now maintained in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. .. code-block:: rst @@ -523,21 +452,8 @@ The following section is an example, how an `Feature <https://eclipse-score.gith 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"). - -.. comp_arc_sta:: Component Static View - Rendered Example - :id: comp_arc_sta__example_feature__component_getstrt - :status: valid - :safety: ASIL_B - :security: NO - :satisfies: comp_req__example_feature__archex_example_req - :belongs_to: comp__component_example_1 - - .. needarch:: - :scale: 50 - :align: center - - {{ draw_component( need(), needs ) }} +The rendered component examples are maintained in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. .. code-block:: rst @@ -588,20 +504,8 @@ Besides storing the output it is also possible to display the generated PlantUML Debug example for component architecture: -.. comp_arc_sta:: Component Static View - Rendered Debug Example - :id: comp_arc_sta__example_feature__component_getstrt_debug - :status: valid - :safety: ASIL_B - :security: NO - :satisfies: comp_req__example_feature__archex_example_req - :belongs_to: comp__component_example_1 - - .. needarch:: - :scale: 50 - :align: center - :debug: - - {{ draw_component( need(), needs ) }} +See the rendered debug example in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. .. _manual_addition_uml: @@ -630,22 +534,8 @@ To make *needuml* work we have to replace the *need()* call with a different fun } CM -> LI1: EXTRA_LINKAGE_MANUALLY_ADDED -.. comp_arc_sta:: Component Architecture Static View - Rendered Example Manually Edited - :id: comp_arc_sta__example_feature__component_manual_getstrt - :status: valid - :safety: ASIL_B - :security: NO - :uses: logic_arc_int__example_feature__archex_logical_interface_1 - :satisfies: comp_req__example_feature__archex_example_req - :belongs_to: comp__component_example_1 - - .. needarch:: - - {{ draw_component( needs.get('comp__component_example_1'), needs ) }} - - component "Component Manual" as CM { - } - CM -> logic_arc_int__example_feature__archex_logical_interface_1: EXTRA_LINKAGE_MANUALLY_ADDED +See the rendered manual-edit example in the +`module template documentation <https://eclipse-score.github.io/module_template/main/>`__. You can add any layout or additional configuration you want before you call the *draw_xyz*. diff --git a/process/process_areas/process_management/guidance/process_management_templates.rst b/process/process_areas/process_management/guidance/process_management_templates.rst index 6f8a5b22d4..8235ffd31c 100644 --- a/process/process_areas/process_management/guidance/process_management_templates.rst +++ b/process/process_areas/process_management/guidance/process_management_templates.rst @@ -175,7 +175,7 @@ Templates :id: gd_req__<process area or abbreviation>_<...> :status: <draft|valid> :tags: <process area or abbreviation> - :derived_from: <defined workflow:wf__<...>>, ..., <defined workflow:wf__<...>> + :satisfies: <defined workflow:wf__<...>>, ..., <defined workflow:wf__<...>> :complies: <standard requirement:std_req__<...>>, ..., <standard requirement:std_req__<...>> diff --git a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst index 38e4692744..0ee95a34a8 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst @@ -58,7 +58,7 @@ Templates .. gd_req:: <Title> :id: gd_req__<process>__<Title> - :derived_from: <link to guidance id> + :satisfies: <link to guidance id> :complies: <link to standard requirement> :status: <valid|invalid> @@ -73,7 +73,7 @@ Templates :id: tool_req__<tool>__<Title> :security: <YES|NO> :safety: <QM|ASIL_B> - :derived_from: <link to process req id> + :satisfies: <link to process req id> :status: <valid|invalid> :implemented: <YES|PARTIAL|NO> diff --git a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst index 28cc47d01e..15c803b753 100644 --- a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst +++ b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst @@ -26,7 +26,7 @@ Security Analysis Process Requirements :status: valid :tags: done_automation, security_analysis :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8321, std_req__isosae21434__continual_8621, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: Security Analysis shall be hierarchically grouped into different levels. @@ -46,7 +46,7 @@ Process Security Analysis Attributes :status: valid :tags: done_automation, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8321 + :complies: Each Security Analysis shall have a unique ID. It shall be in a format which is also human readable and consists of @@ -61,7 +61,7 @@ Process Security Analysis Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8321 + :complies: The title of the Security Analysis shall provide a short summary of the description @@ -70,7 +70,7 @@ Process Security Analysis Attributes :status: valid :tags: prio_1_automation, attribute, optional :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: Each threat shall have an associated treatment (accept, avoid, reduce, share) or AoU. If mitigation has not yet been implemented, do not use this option. @@ -81,7 +81,7 @@ Process Security Analysis Attributes :status: valid :tags: prio_1_automation, attribute, optional :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8322, std_req__isosae21434__continual_8323, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15921 + :complies: If a new security mitigation (avoid, reduce, or share) is needed, link to the issue and keep status invalid until the mitigation is sufficient. @@ -90,7 +90,7 @@ Process Security Analysis Attributes :status: valid :tags: prio_1_automation, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: The mitigation(s) shall be rated as sufficient with <yes> or <no>. A mitigation can only be sufficient if a mitigation is linked via the attribute mitigation. @@ -100,7 +100,7 @@ Process Security Analysis Attributes :status: valid :tags: prio_1_automation, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8421, std_req__isosae21434__continual_8521, std_req__isosae21434__continual_8522, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: The argument shall describe why the mitigation is sufficient or not. If it is not sufficient, the argument shall describe how the mitigation can be improved to achieve sufficiency. The argument shall be written in the content. @@ -110,7 +110,7 @@ Process Security Analysis Attributes :status: valid :tags: prio_1_automation, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8322, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15921 + :complies: Each Security Analysis shall have the status invalid until the analysis is finished. The status shall be set to valid if the analysis is finished and all issues are closed. @@ -120,7 +120,7 @@ Process Security Analysis Attributes :status: valid :tags: prio_1_automation, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8321, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: Every Security Analysis shall have a short description of the threat impact (e.g. threat leads to unauthorized access of the analyzed element) @@ -210,7 +210,7 @@ Security Analysis Checks :status: valid :tags: prio_1_automation, attribute, check :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__continual_8621, + :complies: It shall be checked if all mandatory attributes for each Security Analysis are provided by the user. For all Security Analysis following attributes shall be mandatory: @@ -251,7 +251,7 @@ Threat Scenario Security Process Requirements :status: valid :tags: prio_1_automation, attribute, mandatory :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: Each threat scenario used for the Security Analysis shall have a threat scenario ID. The threat scenario ID is used to identify the related threat <:need:`gd_guidl__sec_ana_threat_scenarios`>. @@ -267,7 +267,7 @@ Threat Models Process Requirements :status: valid :tags: prio_1_automation, attribute, mandatory :derived_from: wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 + :complies: Each threat used for Security Analysis shall have a threat ID. The threat ID is used to identify the related threat <:need:`gd_guidl__threat_models_stride`>. From 405d75b2b9baee6dba307c4b11aff01381e0dd34 Mon Sep 17 00:00:00 2001 From: rahulsasingh <rahul.sa.singh@partner.bmwgroup.com> Date: Wed, 13 May 2026 09:37:39 +0200 Subject: [PATCH 3/3] Revert gd_req/arch links per review, add satisfied_by for requirements --- .../feature_name/architecture/index.rst | 21 ++++-- .../feature_name/requirements/index.rst | 4 +- .../docs/architecture/index.rst | 10 +-- .../docs/requirements/index.rst | 4 +- .../general_concepts/score_review_concept.rst | 10 +-- .../architecture_concept.rst | 6 +- .../guidance/architecture_process_reqs.rst | 42 ++++++------ .../guidance/change_management_reqs.rst | 22 +++---- .../guidance/configuration_process_req.rst | 8 +-- .../guidance/documentation_process_reqs.rst | 6 +- .../guidance/implementation_process_reqs.rst | 54 +++++++-------- .../guidance/problem_resolution_reqs.rst | 24 +++---- .../guidance/process_management_reqs.rst | 8 +-- .../guidance/quality_process_reqs.rst | 2 +- .../guidance/release_process_reqs.rst | 2 +- .../guidance/requirements_process_reqs.rst | 54 +++++++-------- .../guidance/requirements_templates.rst | 15 +---- .../guidance/process_req.rst | 4 +- .../security_analysis_process_reqs.rst | 66 +++++++++---------- .../security_management_process_reqs.rst | 4 +- .../guidance/tool_management_reqs.rst | 14 ++-- .../guidance/verification_process_reqs.rst | 20 +++--- 22 files changed, 198 insertions(+), 202 deletions(-) diff --git a/process/folder_templates/features/feature_name/architecture/index.rst b/process/folder_templates/features/feature_name/architecture/index.rst index 1ecc0067c1..85aeed5e32 100644 --- a/process/folder_templates/features/feature_name/architecture/index.rst +++ b/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 diff --git a/process/folder_templates/features/feature_name/requirements/index.rst b/process/folder_templates/features/feature_name/requirements/index.rst index 481ae21c3b..bcce0631a1 100644 --- a/process/folder_templates/features/feature_name/requirements/index.rst +++ b/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) diff --git a/process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst b/process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst index 3846b1e939..4a660a35d3 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/architecture/index.rst +++ b/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 diff --git a/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst b/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst index 82a5b2cf7f..c31c54e631 100644 --- a/process/folder_templates/modules/module_name/component_name/docs/requirements/index.rst +++ b/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 diff --git a/process/general_concepts/score_review_concept.rst b/process/general_concepts/score_review_concept.rst index 2fcc454678..920a2ff1f1 100644 --- a/process/general_concepts/score_review_concept.rst +++ b/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). diff --git a/process/process_areas/architecture_design/architecture_concept.rst b/process/process_areas/architecture_design/architecture_concept.rst index 18bd9a5ff6..f1e6c5fcbb 100644 --- a/process/process_areas/architecture_design/architecture_concept.rst +++ b/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:: diff --git a/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst b/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst index dd7dbbc8d7..13f9df5991 100644 --- a/process/process_areas/architecture_design/guidance/architecture_process_reqs.rst +++ b/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,7 +241,7 @@ 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. @@ -249,7 +249,7 @@ Checks for Architectural Design :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,7 +279,7 @@ 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. @@ -287,6 +287,6 @@ Checks for Architectural Design :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. diff --git a/process/process_areas/change_management/guidance/change_management_reqs.rst b/process/process_areas/change_management/guidance/change_management_reqs.rst index cade3764f9..e05e1b2c97 100644 --- a/process/process_areas/change_management/guidance/change_management_reqs.rst +++ b/process/process_areas/change_management/guidance/change_management_reqs.rst @@ -24,7 +24,7 @@ Change Request Attributes :id: gd_req__change_attr_uid :status: valid :tags: done_automation, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP1, std_req__iso26262__support_8411, std_req__iso26262__support_8421, std_req__iso26262__support_8432, std_req__iso26262__support_8453 Each Change Request shall have a unique ID. It shall be in an integer number. @@ -33,7 +33,7 @@ Change Request Attributes :id: gd_req__change_attr_status :status: valid :tags: done_automation, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP3, std_req__aspice_40__SUP-10-BP5, std_req__aspice_40__SUP-10-BP6, std_req__iso26262__support_8411, std_req__iso26262__support_8422, std_req__iso26262__support_8432, std_req__iso26262__support_8442 Each Change Request shall have a status: @@ -48,7 +48,7 @@ Change Request Attributes :id: gd_req__change_attr_title :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP1, std_req__iso26262__support_8411, std_req__iso26262__support_8422 Reason for the Change Request @@ -57,7 +57,7 @@ Change Request Attributes :id: gd_req__change_attr_impact_description :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8411, std_req__iso26262__support_8422, std_req__iso26262__support_8431, std_req__iso26262__support_8432, std_req__iso26262__support_8452, std_req__iso26262__support_8453 Exact description of the Change Request, including impact analysis on functional safety, @@ -67,7 +67,7 @@ Change Request Attributes :id: gd_req__change_attr_impact_safety :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8422 Each Change Request shall have a automotive safety integrity level (ASIL) identifier: @@ -79,7 +79,7 @@ Change Request Attributes :id: gd_req__change_attr_impact_security :status: valid :tags: prio_2_automation, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP2, std_req__iso26262__support_8422 Each Change Request shall have a security relevance identifier: @@ -91,7 +91,7 @@ Change Request Attributes :id: gd_req__change_attr_types :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP1 * Feature @@ -120,7 +120,7 @@ Change Request Attributes :id: gd_req__change_attr_affected_wp :status: draft :tags: attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP4, std_req__iso26262__support_8412, std_req__iso26262__support_8422, std_req__iso26262__support_8452, std_req__iso26262__support_8453 Links to the work products affected by the Change Request @@ -129,7 +129,7 @@ Change Request Attributes :id: gd_req__change_attr_milestone :status: valid :tags: done_automation, attribute, mandatory - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__SUP-10-BP6, std_req__iso26262__support_8413 Milestone until the Change Request must be implemented (used for prioritization) @@ -144,7 +144,7 @@ Change Request Checks :id: gd_req__change_attr_mandatory :status: valid :tags: prio_2_automation, attribute, check - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__iic-13-51 It shall be checked if all mandatory attributes for each Change Request @@ -166,7 +166,7 @@ Change Request Traceability Impact Analysis Tool :id: gd_req__change_tool_impact_analysis :status: valid :tags: prio_3_automation, check, tool - :derived_from: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr + :satisfies: wf__change_create_cr, wf__change_analyze_cr, wf__change_implement_monitor_cr, wf__change_close_cr :complies: std_req__aspice_40__iic-13-51 It shall be reported, which work products and elements are affected by adding a new diff --git a/process/process_areas/configuration_management/guidance/configuration_process_req.rst b/process/process_areas/configuration_management/guidance/configuration_process_req.rst index 46bfd4ebf7..6f366a26dd 100644 --- a/process/process_areas/configuration_management/guidance/configuration_process_req.rst +++ b/process/process_areas/configuration_management/guidance/configuration_process_req.rst @@ -20,7 +20,7 @@ Configuration Management Process Requirements :status: valid :tags: done_automation, config_mgt :complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8 - :derived_from: wf__monitor_verify_requirements, wf__mr_vy_arch, wf__mr_saf_analyses_dfa, wf__vy_saf_analyses_dfa, wf__platform_mr_im_platform_mgmt_plan + :satisfies: wf__monitor_verify_requirements, wf__mr_vy_arch, wf__mr_saf_analyses_dfa, wf__vy_saf_analyses_dfa, wf__platform_mr_im_platform_mgmt_plan The Docs-as-Code tool shall check that the Id's of the configuration items (documented in doc-as-code) are unique. @@ -31,7 +31,7 @@ Configuration Management Process Requirements :status: valid :tags: prio_3_automation, config_mgt :complies: std_req__iso26262__support_745, std_req__aspice_40__SUP-8-BP8 - :derived_from: wf__rel_platform_rel_note, wf__rel_mod_rel_note + :satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note At least every platform release shall be stored permanently as a collection of text documents (docs and code) including the used OSS tooling on project owned servers. @@ -44,7 +44,7 @@ Configuration Management Process Requirements :status: valid :tags: prio_2_automation, config_mgt :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 The content of pull requests (conversation, commits, files changed) shall be stored permanently for every release. @@ -56,7 +56,7 @@ Configuration Management Process Requirements :status: valid :tags: prio_2_automation, config_mgt :complies: std_req__iso26262__support_741 - :derived_from: wf__rel_platform_rel_note, wf__rel_mod_rel_note + :satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note It shall be possible to show the differences between two baselines. diff --git a/process/process_areas/documentation_management/guidance/documentation_process_reqs.rst b/process/process_areas/documentation_management/guidance/documentation_process_reqs.rst index 308ddc4253..91b83ade6c 100644 --- a/process/process_areas/documentation_management/guidance/documentation_process_reqs.rst +++ b/process/process_areas/documentation_management/guidance/documentation_process_reqs.rst @@ -86,7 +86,7 @@ Document Management Process Requirements .. gd_req:: Document Author :id: gd_req__doc_author :status: valid - :tags: done_automation + :tags: prio_1_automation :satisfies: wf__platform_cr_mt_platform_mgmt_plan :complies: std_req__iso26262__support_1045 @@ -96,7 +96,7 @@ Document Management Process Requirements .. gd_req:: Document Reviewer :id: gd_req__doc_reviewer :status: valid - :tags: done_automation + :tags: prio_1_automation :satisfies: wf__platform_cr_mt_platform_mgmt_plan :complies: std_req__iso26262__support_1043 @@ -106,7 +106,7 @@ Document Management Process Requirements .. gd_req:: Document Approver :id: gd_req__doc_approver :status: valid - :tags: done_automation + :tags: prio_1_automation :satisfies: wf__platform_cr_mt_platform_mgmt_plan :complies: std_req__iso26262__support_1045 diff --git a/process/process_areas/implementation/guidance/implementation_process_reqs.rst b/process/process_areas/implementation/guidance/implementation_process_reqs.rst index a85ffd3284..9b78eddd09 100644 --- a/process/process_areas/implementation/guidance/implementation_process_reqs.rst +++ b/process/process_areas/implementation/guidance/implementation_process_reqs.rst @@ -19,7 +19,7 @@ Process Requirements :id: gd_req__impl_static_diagram :status: valid :tags: manual_prio_1, mandatory - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP1 The static diagram shall represent the unit and their relationships using UML notations. @@ -31,7 +31,7 @@ Diagram Attributes :id: gd_req__impl_diagram_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP2 Each diagram shall have a unique ID. It shall consist of three parts: @@ -46,7 +46,7 @@ Diagram Attributes :id: gd_req__impl_diagram_title :status: valid :tags: manual_prio_1 attribute, mandatory - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__iso26262__software_844, std_req__iso26262__software_845, std_req__aspice_40__SWE-3-BP3, std_req__aspice_40__SWE-3-BP4 The title of the diagram shall provide a short summary of the description, but is not an "additional" requirement. @@ -57,7 +57,7 @@ Diagram Attributes :id: gd_req__impl_diagram_security :status: valid :tags: manual_prio_2, attribute, mandatory - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall have a security relevance identifier: @@ -69,7 +69,7 @@ Diagram Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall have a automotive safety integrity level (ASIL) identifier: @@ -81,7 +81,7 @@ Diagram Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall have a status: @@ -93,7 +93,7 @@ Diagram Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall have a description. The description shall provide a needarch or image of the diagram. @@ -107,7 +107,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__aspice_40__iic-13-51 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be linked to the corresponding component requirement via the attribute implements. @@ -116,7 +116,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding component requirement via the "implemented by" linkage. @@ -125,7 +125,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425, std_req__aspice_40__iic-13-51 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be linked to the corresponding component architecture via the attribute satisfies. @@ -134,7 +134,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding component architecture via the "satisfied by" linkage. @@ -143,7 +143,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be linked to the corresponding component id via the attribute belongs_to. @@ -152,7 +152,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding component id via the "belongs by" linkage. @@ -161,7 +161,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be linked to the corresponding - SW Unit @@ -173,7 +173,7 @@ Diagram Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each diagram shall be automatically linked (inverse direction) to the corresponding - SW Unit @@ -188,7 +188,7 @@ Diagram Checks :status: valid :tags: prio_2_automation, attribute, check :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design It shall be checked if all mandatory attributes for each diagram are provided by the user. For all diagrams following attributes shall be mandatory: @@ -205,7 +205,7 @@ Unit Attributes :id: gd_req__impl_unit_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 Each unit shall have a unique ID. It shall consist of three parts: @@ -221,7 +221,7 @@ Unit Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each unit shall have a description. @@ -233,7 +233,7 @@ Unit Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each unit shall be linked to the corresponding component id via the attribute belongs_to. @@ -242,7 +242,7 @@ Unit Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each unit shall be automatically linked (inverse direction) to the corresponding component id via the "belongs by" linkage. @@ -253,7 +253,7 @@ Interface Attributes :id: gd_req__impl_interface_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design :complies: std_req__iso26262__software_843, std_req__aspice_40__SWE-3-BP1 Each interface shall have a unique ID. It shall consist of three parts: @@ -269,7 +269,7 @@ Interface Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each interface shall have a description. @@ -281,7 +281,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each interface shall be linked to the corresponding SW Unit id via the attribute belongs_to. @@ -290,7 +290,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each interface shall be automatically linked (inverse direction) to the corresponding SW Unit id via the "belongs by" linkage. @@ -299,7 +299,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each interface shall be linked to the corresponding architecture via the attribute implements. @@ -308,7 +308,7 @@ Interface Linkage :status: valid :tags: prio_2_automation, attribute, automated :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__sw_detailed_design + :satisfies: wf__sw_detailed_design Each interface shall be automatically linked (inverse direction) to the corresponding architecture via the "implemented by" linkage. @@ -319,7 +319,7 @@ Dependency Analysis :id: gd_req__impl_dependency_analysis :status: valid :tags: prio_2_automation - :derived_from: wf__sw_verify_implementation + :satisfies: wf__sw_verify_implementation :complies: std_req__iso26262__software_942 For each component a dependency tree view shall be created to support design inspection and Safety Analysis. diff --git a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst index 1cf2e5d1db..5f4b1fdd45 100644 --- a/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst +++ b/process/process_areas/problem_resolution/guidance/problem_resolution_reqs.rst @@ -26,7 +26,7 @@ Problem Attributes :id: gd_req__problem_attr_uid :status: valid :tags: done_automation, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a unique ID. It shall be in an integer number. @@ -35,7 +35,7 @@ Problem Attributes :id: gd_req__problem_attr_status :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a status: @@ -50,7 +50,7 @@ Problem Attributes :id: gd_req__problem_attr_title :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Reason for Problem Report @@ -59,7 +59,7 @@ Problem Attributes :id: gd_req__problem_attr_impact_description :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 Exact description of the Problem, including potential cause and impact of the problem. @@ -73,7 +73,7 @@ Problem Attributes :id: gd_req__problem_attr_analysis_results :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP2 Record analysis results (e.g. reason for rejection, safety, security, quality impact) as comments. @@ -82,7 +82,7 @@ Problem Attributes :id: gd_req__problem_attr_stakeholder :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP2, std_req__aspice_40__SUP-9-BP5 Assign responsible stakeholder for analyzing the problem @@ -92,7 +92,7 @@ Problem Attributes :id: gd_req__problem_attr_classification :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP2 Each Problem shall have a classification identifier: @@ -106,7 +106,7 @@ Problem Attributes :id: gd_req__problem_attr_safety_affected :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a safety relevance identifier: @@ -120,7 +120,7 @@ Problem Attributes :id: gd_req__problem_attr_security_affected :status: valid :tags: prio_1_automation, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 Each Problem shall have a security relevance identifier: @@ -134,7 +134,7 @@ Problem Attributes :id: gd_req__problem_attr_milestone :status: valid :tags: manual_prio_1, problem_resolution, attribute, mandatory - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1, std_req__aspice_40__SUP-9-BP6 Milestone until the Problem must be implemented (used for prioritization) @@ -147,7 +147,7 @@ Problem Resolution Checks :id: gd_req__problem_check_mandatory :status: valid :tags: prio_2_automation, problem_resolution, attribute, check - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 It shall be checked if all mandatory attributes for each Problem @@ -165,7 +165,7 @@ Problem Resolution Checks :id: gd_req__problem_check_closing :status: valid :tags: prio_1_automation, problem_resolution, attribute, check - :derived_from: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr + :satisfies: wf__problem_create_pr, wf__problem_analyze_pr, wf__problem_initiate_monitor_pr, wf__problem_close_pr :complies: std_req__aspice_40__SUP-9-BP1 ISSUEs related to Problem Reports shall not automatically closed, if linked ISSUEs or PRs are closed or merged and diff --git a/process/process_areas/process_management/guidance/process_management_reqs.rst b/process/process_areas/process_management/guidance/process_management_reqs.rst index ee8a88fb1d..a1161eb942 100644 --- a/process/process_areas/process_management/guidance/process_management_reqs.rst +++ b/process/process_areas/process_management/guidance/process_management_reqs.rst @@ -23,7 +23,7 @@ Process Requirements :id: gd_req__process_management_build_blocks :status: valid :tags: done_automation, attribute, mandatory - :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 The process model building blocks are defined. Compare also the process model @@ -67,7 +67,7 @@ Process Building Blocks Attributes :id: gd_req__process_management_build_blocks_attr :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 Each building block shall have defined attributes as defined here: @@ -89,7 +89,7 @@ Process Building Blocks Linkage :id: gd_req__process_management_build_blocks_link :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 Each building block shall have defined links as defined here: @@ -103,7 +103,7 @@ Process Building Blocks Checks :id: gd_req__process_management_build_blocks_check :status: valid :tags: done_automation - :derived_from: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description + :satisfies: wf__cr_mt_process_mgt_strategy, wf__def_app_process_description, wf__mon_imp_process_description :complies: std_req__iso26262__management_5421, std_req__iso26262__management_5422, std_req__aspice_40__gp-311 It shall be checked, that all attributes defined here diff --git a/process/process_areas/quality_management/guidance/quality_process_reqs.rst b/process/process_areas/quality_management/guidance/quality_process_reqs.rst index 995611e561..ce3662bb49 100644 --- a/process/process_areas/quality_management/guidance/quality_process_reqs.rst +++ b/process/process_areas/quality_management/guidance/quality_process_reqs.rst @@ -19,7 +19,7 @@ Process Requirements :id: gd_req__quality_report :status: valid :tags: prio_3_automation, quality_management - :derived_from: wf__mr_imp_qlm_plan_processes + :satisfies: wf__mr_imp_qlm_plan_processes :complies: std_req__iso26262__management_5423, std_req__aspice_40__SUP-1-BP5, std_req__aspice_40__SUP-1-BP6 | The quality report shall be generated progressively and automatically compiling the work products. diff --git a/process/process_areas/release_management/guidance/release_process_reqs.rst b/process/process_areas/release_management/guidance/release_process_reqs.rst index 5c9a0d250e..7c1a77b651 100644 --- a/process/process_areas/release_management/guidance/release_process_reqs.rst +++ b/process/process_areas/release_management/guidance/release_process_reqs.rst @@ -19,7 +19,7 @@ Process Requirements :id: gd_req__release_note :status: valid :tags: prio_2_automation, release_management - :derived_from: wf__rel_platform_rel_note, wf__rel_mod_rel_note + :satisfies: wf__rel_platform_rel_note, wf__rel_mod_rel_note :complies: std_req__iso26262__management_64134, std_req__iso26262__management_64135, std_req__aspice_40__SUP-8-BP7 | The release note shall be generated progressively and automatically compiling the content as far as possible. diff --git a/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst b/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst index 1ed48163aa..7562994e53 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst @@ -21,7 +21,7 @@ Process Requirements :id: gd_req__req_structure :status: valid :tags: done_automation, structure - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432 Requirements shall be hierarchically grouped into three levels. @@ -46,7 +46,7 @@ Process Requirement Attributes :id: gd_req__req_attr_uid :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6432 Each requirement shall have a unique ID. It shall consist of three parts: @@ -61,7 +61,7 @@ Process Requirement Attributes :id: gd_req__req_attr_title :status: valid :tags: manual_prio_1 attribute, mandatory - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6424 The title of the requirement shall provide a short summary of the description, but is not an "additional" requirement. @@ -72,7 +72,7 @@ Process Requirement Attributes :id: gd_req__req_attr_description :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__iso26262__support_6424 Each requirement shall have a description. @@ -87,7 +87,7 @@ Process Requirement Attributes :id: gd_req__req_attr_type :status: valid :tags: manual_prio_2, attribute, mandatory - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou :complies: std_req__aspice_40__iic-17-00 Each requirement, apart from process and tool requirements, shall have a type of one of following options: @@ -101,7 +101,7 @@ Process Requirement Attributes :id: gd_req__req_attr_security :status: valid :tags: manual_prio_2, attribute, mandatory - :derived_from: wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou Each requirement, apart from process and tool requirements, shall have a security relevance identifier: @@ -113,7 +113,7 @@ Process Requirement Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425 - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou Each requirement, apart from process and tool requirements, shall have a automotive safety integrity level (ASIL) identifier: @@ -125,7 +125,7 @@ Process Requirement Attributes :status: valid :tags: manual_prio_1, attribute, mandatory :complies: std_req__iso26262__support_6425 - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_feat_aou, wf__req_comp_aou Each requirement, apart from process and tool requirements, shall have a status: @@ -136,7 +136,7 @@ Process Requirement Attributes :id: gd_req__req_attr_rationale :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__req_stkh_req + :satisfies: wf__req_stkh_req Each stakeholder requirement shall provide an attribute called rationale. The rationale shall contain the reason why the requirement is needed. @@ -145,7 +145,7 @@ Process Requirement Attributes :id: gd_req__req_attr_valid_from :status: valid :tags: manual_prio_2, attribute - :derived_from: wf__req_stkh_req, wf__req_feat_req + :satisfies: wf__req_stkh_req, wf__req_feat_req :complies: std_req__aspice_40__SWE-1-BP2, std_req__aspice_40__iic-17-54 Stakeholder and feature requirements can have a validity attribute that tells @@ -161,7 +161,7 @@ Process Requirement Attributes :id: gd_req__req_attr_valid_until :status: valid :tags: manual_prio_2, attribute - :derived_from: wf__req_stkh_req, wf__req_feat_req + :satisfies: wf__req_stkh_req, wf__req_feat_req :complies: std_req__aspice_40__SWE-1-BP2, std_req__aspice_40__iic-17-54 Stakeholder and feature requirements can have a validity attribute that tells @@ -183,7 +183,7 @@ Process Requirement Linkage :status: valid :tags: manual_prio_1, attribute :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5 - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool Requirements shall be linked to its adjacent level via the attribute derived_from. @@ -196,7 +196,7 @@ Process Requirement Linkage :status: valid :tags: manual_prio_1, attribute :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5 - :derived_from: wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_feat_req, wf__req_comp_req Requirements shall be linked to AoU via the attribute covers, if they already cover these. @@ -211,7 +211,7 @@ Process Requirement Linkage :status: valid :tags: done_automation, attribute :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-1-BP5 - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool Bi-directional traceability shall be provided by adding a "back-link" via attribute derives (i.e. make a <-> out of the <- in :need:`gd_req__req_linkage`). @@ -220,7 +220,7 @@ Process Requirement Linkage :status: valid :tags: manual_prio_1, attribute :complies: std_req__iso26262__support_6423, std_req__aspice_40__iic-13-51 - :derived_from: wf__req_stkh_req, wf__req_feat_req + :satisfies: wf__req_stkh_req, wf__req_feat_req It shall be possible to specify the requirement coverage, meaning the requirement is covered fully by its linked children. @@ -231,7 +231,7 @@ Process Requirement Linkage :id: gd_req__req_attr_impl :status: valid :tags: prio_2_automation, attribute - :derived_from: wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_feat_req, wf__req_comp_req It shall be possible to link requirements to code (to the respective line of code in an attribute of the requirement). @@ -239,7 +239,7 @@ Process Requirement Linkage :id: gd_req__req_attr_testlink :status: valid :tags: prio_1_automation, attribute - :derived_from: wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6433, std_req__iso26262__software_944 It shall be possible to link requirements to tests and automatically include a link to the test case in the attribute testlink. @@ -248,7 +248,7 @@ Process Requirement Linkage :id: gd_req__req_attr_test_covered :status: valid :tags: manual_prio_1, attribute - :derived_from: wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6433, std_req__iso26262__software_944, std_req__aspice_40__iic-13-51 It shall be possible to specify if a requirement is completely satisfied by the linked test case(s). @@ -260,7 +260,7 @@ Process Requirement Linkage :id: gd_req__req_attr_version :status: valid :tags: prio_1_automation, attribute - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6434 A versioning for requirements shall be provided. For this all mandatory attributes shall be taken into account: see :need:`gd_req__req_check_mandatory` @@ -274,7 +274,7 @@ Process Requirements Checks :id: gd_req__req_suspicious :status: valid :tags: prio_2_automation, check - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6434, std_req__aspice_40__iic-13-51 Based on the requirement versioning it shall be checked if a parent requirement was updated but not the linked child requirements (or tests). @@ -286,7 +286,7 @@ Process Requirements Checks :id: gd_req__req_check_mandatory :status: valid :tags: done_automation, check - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou It shall be checked if all mandatory attributes for each requirement is provided by the user. For all requirements following attributes shall be mandatory: @@ -302,7 +302,7 @@ Process Requirements Checks :id: gd_req__req_desc_weak :status: valid :tags: done_automation, check - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_proc_tool, wf__req_feat_aou, wf__req_comp_aou + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req, wf__req_tool, wf__req_feat_aou, wf__req_comp_aou It shall be ensured that no *weak words* are contained in the requirement description for: @@ -319,7 +319,7 @@ Process Requirements Checks :status: valid :tags: done_automation, check :complies: std_req__iso26262__support_6432, std_req__aspice_40__iic-13-51 - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req Every feature- and component requirement shall be linked to at least one parent requirement according to the defined traceability scheme: @@ -330,7 +330,7 @@ Process Requirements Checks :status: valid :tags: prio_2_automation, check :complies: std_req__iso26262__support_6423 - :derived_from: wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_feat_req, wf__req_comp_req It shall be checked if every feature- and component requirement is linked at least to one valid architectural element on the same level. This should also include requirement type checking: @@ -346,7 +346,7 @@ Process Requirements Checks :status: valid :tags: prio_2_automation, check :complies: std_req__iso26262__support_6423 - :derived_from: wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_feat_req, wf__req_comp_req The check :need:`gd_req__req_linkage_architecture` shall only be enabled for a release build, otherwise it would block creating requirements first without architecture. @@ -354,7 +354,7 @@ Process Requirements Checks :id: gd_req__req_linkage_safety :status: valid :tags: done_automation, check - :derived_from: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req + :satisfies: wf__req_stkh_req, wf__req_feat_req, wf__req_comp_req :complies: std_req__iso26262__support_6422 It shall be checked that (child) QM requirements (Safety == QM) can not be linked against a (parent) safety requirement (Safety != QM). @@ -365,7 +365,7 @@ Process Requirements Checks :id: gd_req__req_validity :status: valid :tags: prio_3_automation, check - :derived_from: wf__req_stkh_req, wf__req_feat_req + :satisfies: wf__req_stkh_req, wf__req_feat_req Validity attributes (:need:`gd_req__req_attr_valid_from` and :need:`gd_req__req_attr_valid_until`) shall be checked for correctness (i.e. they denote an existing milestone) and consistent (e.g. the until is not before from) Several of the above checks are not to be executed on requirements not valid in the next milestone, these are TBD diff --git a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst index 0ee95a34a8..32eb21de8b 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_templates.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_templates.rst @@ -49,19 +49,6 @@ Templates See the Assumption of Use requirement snippets in the `module template documentation <https://eclipse-score.github.io/module_template/aou_requirements_template.html>`__. -.. gd_temp:: Process Requirements Template - :id: gd_temp__req_process_req - :status: valid - :complies: std_req__iso26262__support_641, std_req__iso26262__support_6421, std_req__iso26262__support_6425 - - .. code-block:: rst - - .. gd_req:: <Title> - :id: gd_req__<process>__<Title> - :satisfies: <link to guidance id> - :complies: <link to standard requirement> - :status: <valid|invalid> - .. gd_temp:: Tool Requirements Template :id: gd_temp__req_tool_req :status: valid @@ -73,7 +60,7 @@ Templates :id: tool_req__<tool>__<Title> :security: <YES|NO> :safety: <QM|ASIL_B> - :satisfies: <link to process req id> + :derived_from: <link to process req id> :status: <valid|invalid> :implemented: <YES|PARTIAL|NO> diff --git a/process/process_areas/safety_management/guidance/process_req.rst b/process/process_areas/safety_management/guidance/process_req.rst index c3b32fe119..5ae83d9ca9 100644 --- a/process/process_areas/safety_management/guidance/process_req.rst +++ b/process/process_areas/safety_management/guidance/process_req.rst @@ -20,7 +20,7 @@ Safety Management Process Requirements :status: valid :tags: done_automation :complies: std_req__iso26262__management_6468 - :derived_from: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual + :satisfies: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual Safety plans shall contain documents references where the status is derived automatically. @@ -31,7 +31,7 @@ Safety Management Process Requirements :status: valid :tags: prio_2_automation :complies: std_req__iso26262__management_6468 - :derived_from: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual + :satisfies: wf__cr_mt_safety_plan, wf__cr_comp_class, wf__cr_mt_safety_manual Safety plans shall contain work product references where the accumulated status is derived automatically. diff --git a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst index 15c803b753..a49e767e9e 100644 --- a/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst +++ b/process/process_areas/security_analysis/guidance/security_analysis_process_reqs.rst @@ -25,8 +25,8 @@ Security Analysis Process Requirements :id: gd_req__sec_structure :status: valid :tags: done_automation, security_analysis - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8321, std_req__isosae21434__continual_8621, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Security Analysis shall be hierarchically grouped into different levels. @@ -45,8 +45,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_uid :status: valid :tags: done_automation, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8321 Each Security Analysis shall have a unique ID. It shall be in a format which is also human readable and consists of @@ -60,8 +60,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_title :status: valid :tags: manual_prio_1, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8321 The title of the Security Analysis shall provide a short summary of the description @@ -69,8 +69,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_mitigated_by :status: valid :tags: prio_1_automation, attribute, optional - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Each threat shall have an associated treatment (accept, avoid, reduce, share) or AoU. If mitigation has not yet been implemented, do not use this option. @@ -80,8 +80,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_mitigation_issue :status: valid :tags: prio_1_automation, attribute, optional - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8322, std_req__isosae21434__continual_8323, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15921 If a new security mitigation (avoid, reduce, or share) is needed, link to the issue and keep status invalid until the mitigation is sufficient. @@ -89,8 +89,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_sufficient :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 The mitigation(s) shall be rated as sufficient with <yes> or <no>. A mitigation can only be sufficient if a mitigation is linked via the attribute mitigation. @@ -99,8 +99,8 @@ Process Security Analysis Attributes :id: gd_req__sec_argument :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8421, std_req__isosae21434__continual_8521, std_req__isosae21434__continual_8522, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 The argument shall describe why the mitigation is sufficient or not. If it is not sufficient, the argument shall describe how the mitigation can be improved to achieve sufficiency. The argument shall be written in the content. @@ -109,8 +109,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_status :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8322, std_req__isosae21434__continual_8621, std_req__isosae21434__continual_8622, std_req__isosae21434__assessment_15921 Each Security Analysis shall have the status invalid until the analysis is finished. The status shall be set to valid if the analysis is finished and all issues are closed. @@ -119,8 +119,8 @@ Process Security Analysis Attributes :id: gd_req__sec_attr_teffect :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8321, std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15721, std_req__isosae21434__assessment_15722, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Every Security Analysis shall have a short description of the threat impact (e.g. threat leads to unauthorized access of the analyzed element) @@ -134,7 +134,7 @@ Security Analysis Linkage :id: gd_req__sec_linkage_check :status: valid :tags: prio_1_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Security Analysis shall be linked to the architecture view on the corresponding level @@ -144,7 +144,7 @@ Security Analysis Linkage :id: gd_req__sec_linkage :status: valid :tags: prio_2_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Each Security Analysis shall be automatically linked (inverse direction) to the @@ -154,7 +154,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_requirements_check :status: valid :tags: prio_1_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Security Analysis shall be linked to a requirement on the corresponding level via @@ -164,7 +164,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_requirements :status: valid :tags: prio_2_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: Each Security Analysis shall be automatically linked to the corresponding Security @@ -174,7 +174,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_aou :status: valid :tags: prio_1_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be possible to link AoU. @@ -183,7 +183,7 @@ Security Analysis Linkage :id: gd_req__sec_attr_ver :status: valid :tags: prio_2_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be possible to detect any differences in mandatory attributes compared to @@ -193,7 +193,7 @@ Security Analysis Linkage :id: gd_req__sec_linkage_status_check :status: valid :tags: prio_3_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be checked that the Security Analysis can only be linked against valid @@ -209,8 +209,8 @@ Security Analysis Checks :id: gd_req__sec_attr_mandatory :status: valid :tags: prio_1_automation, attribute, check - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__continual_8621, It shall be checked if all mandatory attributes for each Security Analysis are provided by the user. For all Security Analysis following attributes shall be mandatory: @@ -226,7 +226,7 @@ Security Analysis Checks :id: gd_req__sec_linkage_security :status: valid :tags: prio_2_automation, attribute, check - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be checked that Security Analysis can only be linked via mitigate_by against @@ -238,7 +238,7 @@ Security Analysis Checks :id: gd_req__sec_finalization_check :status: valid :tags: prio_2_automation, attribute, automated - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch :complies: It shall be checked if all artifacts of the analysis are "valid" and "sufficient". @@ -250,8 +250,8 @@ Threat Scenario Security Process Requirements :id: gd_req__sec_attr_threat_scenario_id :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_platform_featarch, wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Each threat scenario used for the Security Analysis shall have a threat scenario ID. The threat scenario ID is used to identify the related threat <:need:`gd_guidl__sec_ana_threat_scenarios`>. @@ -266,8 +266,8 @@ Threat Models Process Requirements :id: gd_req__sec_attr_stride_threat_id :status: valid :tags: prio_1_automation, attribute, mandatory - :derived_from: wf__analyse_sec_featarch, wf__analyse_sec_comparch - :complies: + :satisfies: wf__analyse_sec_featarch, wf__analyse_sec_comparch + :complies: std_req__isosae21434__assessment_15621, std_req__isosae21434__assessment_15622, std_req__isosae21434__assessment_15723, std_req__isosae21434__assessment_15724, std_req__isosae21434__assessment_15725, std_req__isosae21434__assessment_15821, std_req__isosae21434__assessment_15822, std_req__isosae21434__assessment_15921 Each threat used for Security Analysis shall have a threat ID. The threat ID is used to identify the related threat <:need:`gd_guidl__threat_models_stride`>. diff --git a/process/process_areas/security_management/guidance/security_management_process_reqs.rst b/process/process_areas/security_management/guidance/security_management_process_reqs.rst index 8342bc5350..0d5e01cb3a 100644 --- a/process/process_areas/security_management/guidance/security_management_process_reqs.rst +++ b/process/process_areas/security_management/guidance/security_management_process_reqs.rst @@ -20,7 +20,7 @@ Security Management Process Requirements :id: gd_req__security_doc_status :status: valid :tags: done_automation, attribute, mandatory - :derived_from: wf__cr_mt_security_plan + :satisfies: wf__cr_mt_security_plan :complies: std_req__isosae21434__prj_management_6429 Security Plans shall contain documents references where the status is derived automatically. @@ -31,7 +31,7 @@ Security Management Process Requirements :id: gd_req__security_wp_status :status: valid :tags: prio_2_automation, attribute, mandatory - :derived_from: wf__cr_mt_security_plan + :satisfies: wf__cr_mt_security_plan :complies: std_req__isosae21434__prj_management_6429 Security Plans shall contain work product references where the accumulated status is derived automatically. diff --git a/process/process_areas/tool_management/guidance/tool_management_reqs.rst b/process/process_areas/tool_management/guidance/tool_management_reqs.rst index dc4dfee16a..86456eb44a 100644 --- a/process/process_areas/tool_management/guidance/tool_management_reqs.rst +++ b/process/process_areas/tool_management/guidance/tool_management_reqs.rst @@ -26,7 +26,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_uid :status: valid :tags: done_automation, tool_management, attribute, mandatory - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a unique ID. @@ -35,7 +35,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_status :status: valid :tags: prio_1_automation, tool_management, attribute, mandatory - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a status. @@ -50,7 +50,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_version :status: valid :tags: manual_prio_1, tool_management, attribute, mandatory - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a version: @@ -61,7 +61,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_tcl :status: valid :tags: manual_prio_1, tool_management, attribute, mandatory - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a tool confidence level: @@ -73,7 +73,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_safety_affected :status: valid :tags: manual_prio_1, tool_management, attribute, mandatory - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__iso26262__support_1141, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a safety relevance identifier: @@ -85,7 +85,7 @@ Tool Verification Report Attributes :id: gd_req__tool_attr_security_affected :status: valid :tags: manual_prio_2, tool_management, attribute, mandatory - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__isosae21434__org_management_5451, std_req__aspice_40__SUP-8-BP1 Each Tool Verification Report shall have a security relevance identifier: @@ -101,7 +101,7 @@ Tool Verification Report Checks :id: gd_req__tool_check_mandatory :status: valid :tags: prio_1_automation, tool_management, attribute, check - :derived_from: wf__tool_create_tool_verification_report + :satisfies: wf__tool_create_tool_verification_report :complies: std_req__aspice_40__SUP-8-BP1 It shall be checked if all mandatory attributes for each Tool Verification Report diff --git a/process/process_areas/verification/guidance/verification_process_reqs.rst b/process/process_areas/verification/guidance/verification_process_reqs.rst index bc6c578b9f..29c22d10ed 100644 --- a/process/process_areas/verification/guidance/verification_process_reqs.rst +++ b/process/process_areas/verification/guidance/verification_process_reqs.rst @@ -21,7 +21,7 @@ Process Requirements :id: gd_req__verification_link_tests :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432 @@ -53,7 +53,7 @@ Process Requirements :id: gd_req__verification_link_tests_cpp :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 @@ -68,7 +68,7 @@ Process Requirements :id: gd_req__verification_link_tests_python :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 @@ -90,7 +90,7 @@ Process Requirements :id: gd_req__verification_link_tests_rust :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__iso26262__support_6432, std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 For linking Rust tests to requirements **#[record_property]** shall be used: @@ -101,7 +101,7 @@ Process Requirements :id: gd_req__verification_independence :status: valid :tags: done_automation, verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: std_req__aspice_40__SWE-4-BP4, std_req__aspice_40__SWE-5-BP6, std_req__aspice_40__SWE-6-BP4 The approver of a pull request shall differ from the author(s) of the pull request in all pull requests. @@ -110,7 +110,7 @@ Process Requirements :id: gd_req__verification_reporting :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_mod_ver_report + :satisfies: wf__verification_mod_ver_report :complies: The tool automation shall automatically generate the Verification reports. @@ -121,7 +121,7 @@ Process Requirements :id: gd_req__verification_report_archiving :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_mod_ver_report + :satisfies: wf__verification_mod_ver_report :complies: The tool automation shall automatically archive the Verification reports for releases. @@ -131,7 +131,7 @@ Process Requirements :id: gd_req__verification_checks :status: valid :tags: prio_1_automation, verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: The following checks shall be implemented on test metadata: @@ -147,7 +147,7 @@ Process Requirements :id: gd_req__verification_checks_extended :status: draft :tags: verification - :derived_from: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test + :satisfies: wf__verification_unit_test, wf__verification_comp_int_test, wf__verification_feat_int_test, wf__verification_platform_int_test :complies: The following checks shall be implemented on test metadata: @@ -159,7 +159,7 @@ Process Requirements :id: gd_req__verification_external_aou :status: valid :tags: prio_2_automation, verification - :derived_from: wf__verification_comp_int_test, wf__verification_feat_int_test + :satisfies: wf__verification_comp_int_test, wf__verification_feat_int_test :complies: External components AoUs shall be verified by integration tests or static analysis tooling.