update 1-bugfix issue template to align with version in score

issue template in score was changed, thus the template here must
be adapted accordingly
fix missing option security
fix missing option satisfied

Resolves: #134, #135

Author: masc2023

.github/ISSUE_TEMPLATE/1-bugfix.yml

@@ -32,7 +32,6 @@ body:
       label: Analysis results
       description: |
         Documentation of the analysis results
-        Link to Pull Request containing the results
     validations:
       required: true
   - type: textarea

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

@@ -37,6 +37,7 @@ Requirements
    :id: stkh_req__requirements__template
    :reqtype: Non-Functional
    :safety: ASIL_B
+   :security: YES
    :rationale: Exists just for the template example
    :status: invalid
 

process/process_areas/architecture_design/_assets/architecture_modeling_example.rst

@@ -210,6 +210,7 @@ Component Architecure File(s)
    :id: stkh_req__archdes_example_req
    :reqtype: Functional
    :safety: ASIL_B
+   :security: YES
    :rationale: needed for archdes example
    :status: valid
 

process/process_areas/architecture_design/guidance/architecture_process_reqs.rst

@@ -25,7 +25,7 @@ Architectural Model
    :status: valid
    :tags: manual
    :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432
-   :satisfies: wf__cr_mt_featarch
+   :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
-   :satisfies: wf__cr_mt_featarch
+   :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
-   :satisfies: wf__cr_mt_featarch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Following architectural elements shall be defined on the respective hierarchical level:
 
@@ -65,7 +65,7 @@ Architectural Model
    :status: valid
    :tags: done_automation
    :complies: std_req__iso26262__support_6431, std_req__iso26262__support_6432
-   :satisfies: wf__cr_mt_featarch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    For modeling the viewpoints following relations shall be used:
 
@@ -82,7 +82,7 @@ Architectural Views
    :status: valid
    :tags: manual
    :complies: std_req__iso26262__support_6432, std_req__iso26262__software_742
-   :satisfies: wf__cr_mt_featarch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    The architecture shall be shown on following views on each architectural level:
 
@@ -100,6 +100,7 @@ Attributes of Architectural Elements
    :status: valid
    :tags: manual, attribute, mandatory
    :complies: std_req__iso26262__support_6425, std_req__iso26262__support_6432
+   :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
 
@@ -113,6 +114,7 @@ Attributes of Architectural Elements
    :id: gd_req__arch__attr_security
    :status: valid
    :tags: manual, attribute, mandatory
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a security relevance identifier:
 
@@ -124,6 +126,7 @@ Attributes of Architectural Elements
    :status: valid
    :tags: manual, attribute, mandatory
    :complies: std_req__iso26262__support_6421, std_req__iso26262__support_6425
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a automotive safety integrity level (ASIL) identifier:
 
@@ -135,6 +138,7 @@ Attributes of Architectural Elements
    :status: valid
    :tags: manual, attribute, mandatory
    :complies: std_req__iso26262__support_6425
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall have a status:
 
@@ -149,6 +153,7 @@ Traceability to Requirements
    :status: valid
    :tags: manual, attribute, mandatory
    :complies: std_req__iso26262__support_6425
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Each architectural element shall be linked to a requirement.
 
@@ -157,7 +162,7 @@ Traceability to Requirements
    :status: valid
    :tags: manual
    :complies: std_req__iso26262__support_6432
-   :satisfies: wf__cr_mt_featarch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    Requirements shall be fulfilled by an architectural element on the corresponding level.
 
@@ -176,6 +181,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
 
    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:
 
@@ -189,27 +195,31 @@ 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
 
    It shall be checked that every valid safety architectural element is linked according to the defined model :need:`gd_req__arch__build_blocks_corr`.
 
 .. gd_req:: Architecture linkage safety
    :id: gd_req__arch__linkage_safety_trace
    :status: valid
    :tags: prio_1_automation, attribute, check
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked that valid safety architectural elements (Safety != QM) can only be linked against valid safety architectural elements.
 
 .. gd_req:: Architecture linkage security
    :id: gd_req__arch__linkage_security_trace
    :status: valid
    :tags: prio_2_automation, attribute, check
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked that security relevant architectural elements (Security == YES) can only be linked against security relevant architectural elements.
 
 .. gd_req:: Architecture linkage requirement
    :id: gd_req__arch__linkage_requirement
    :status: valid
    :tags: prio_1_automation, attribute, check
+   :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).
@@ -218,6 +228,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
 
    It shall be checked that requirements of a respective type can only be linked to architectural elements according to following traceability:
 
@@ -228,27 +239,30 @@ Checks for Architectural Design
    :id: gd_req__arch__consistency_model
    :status: valid
    :tags: prio_2_automation, model, check
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked if all mentioned SW components are available in the modules repository.
 
 .. gd_req:: Architecture check consistency interfaces
    :id: gd_req__arch__consistency_interf
    :status: valid
    :tags: prio_2_automation, model, check
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked if all mentioned component interfaces are available in the modules repository.
 
 .. gd_req:: Architecture check consistency dynamic architecture
    :id: gd_req__arch__consistency_dynamic
    :status: valid
    :tags: prio_3_automation, model, check
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be checked if all SW components which are mentioned in the dynamic architecture are defined in the static architecture.
 
 .. gd_req:: Building Blocks Dynamic Architecture
    :id: gd_req__arch__build_blocks_dynamic
    :status: valid
    :tags: done_automation
-   :satisfies: wf__cr_mt_featarch
+   :satisfies: wf__cr_mt_featarch, wf__cr_mt_comparch
 
    It shall be possible to provide the required architectural building blocks inside the dynamic architecture.

process/process_areas/configuration_management/guidance/configuration_process_req.rst

@@ -20,6 +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
 
    The doc-as-code tool shall check that the Id's of the configuration items (documented in doc-as-code) are unique.
 
@@ -30,6 +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
 
    At least every platform release shall be stored permanently as a collection of text documents
    (docs and code) including the used OSS tooling outside of github servers.
@@ -54,6 +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
 
    It shall be possible to show the differences between two baselines.
 

process/process_areas/documentation_management/guidance/documentation_process_reqs.rst

@@ -21,6 +21,7 @@ Document Management Process Requirements
    :id: gd_req__doc__types
    :status: valid
    :tags: manual
+   :satisfies: wf__platform__cr_mt_platform_mgmt_plan
    :complies: std_req__iso26262__support_1043
 
    There are the following document types:
@@ -52,6 +53,7 @@ Document Management Process Requirements
    :id: gd_req__doc__attributes_manual
    :status: valid
    :tags: manual
+   :satisfies: wf__platform__cr_mt_platform_mgmt_plan
    :complies: std_req__iso26262__support_1043
 
    Generic documents shall have the following mandatory manual attributes:
@@ -71,6 +73,7 @@ Document Management Process Requirements
    :id: gd_req__doc__author
    :status: valid
    :tags: prio_1_automation
+   :satisfies: wf__platform__cr_mt_platform_mgmt_plan
    :complies: std_req__iso26262__support_1045
 
    The version management tool shall document and report (be able to show) the authorship of a document.
@@ -80,6 +83,7 @@ Document Management Process Requirements
    :id: gd_req__doc__reviewer
    :status: valid
    :tags: prio_1_automation
+   :satisfies: wf__platform__cr_mt_platform_mgmt_plan
    :complies: std_req__iso26262__support_1043
 
    The version management tool shall document and report (be able to show) the reviewers of a document.
@@ -89,6 +93,7 @@ Document Management Process Requirements
    :id: gd_req__doc__approver
    :status: valid
    :tags: prio_1_automation
+   :satisfies: wf__platform__cr_mt_platform_mgmt_plan
    :complies: std_req__iso26262__support_1045
 
    The version management tool shall document and report (be able to show) the approver of a document.

process/process_areas/safety_management/guidance/process_req.rst

@@ -20,6 +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
 
    Safety plans shall contain documents references where the status is derived automatically.
 
@@ -30,6 +31,7 @@ Safety Management Process Requirements
    :status: valid
    :tags: prio_1_automation
    :complies: std_req__iso26262__management_6468
+   :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.
 

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: attribute, mandatory
-   :satisfies:
+   :satisfies: wf__cr_mt_security_plan
    :complies:
 
    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: attribute, mandatory
-   :satisfies:
+   :satisfies: wf__cr_mt_security_plan
    :complies:
 
    Security plans shall contain work product references where the accumulated status is derived automatically.

process/process_areas/verification/guidance/verification_process_toolreqs.rst

@@ -22,8 +22,10 @@ Test Linking to 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_test
     :complies: std_req__iso26262__support_6432
 
+
     For linking test suites to requirements following metadata shall be used:
 
     * Verifies
@@ -52,8 +54,10 @@ Test Linking to 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_test
     :complies: std_req__iso26262__support_6432
 
+
     For linking C++ test suites to requirements **record properties** shall be used. Attributes
     which are common for all test cases can be specified in the Setup Function (SetUp()), the other
     attributes which are specific for each test case need to be specified within the test case:
@@ -83,8 +87,10 @@ Test Linking to 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_test
     :complies: std_req__iso26262__support_6432
 
+
     For linking python tests to requirements **metadata** shall be used. Attributes which are
     common for all test cases can be specified in the Test Suite (above the class), the other
     attributes which are specific for each test case need to be specified above the test case:
@@ -106,6 +112,7 @@ Test Linking to 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_test
     :complies: std_req__iso26262__support_6432
 
     For linking Rust tests to requirements **#[record_property]** shall be used:
@@ -128,13 +135,17 @@ Test Linking to 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_test
+    :complies:
 
     The approver of a pull request shall differ from the author(s) of the pull request in all pull requests.
 
 .. gd_req:: Verification Reporting
     :id: gd_req__verification__reporting
     :status: valid
     :tags: prio_1_automation, verification
+    :satisfies: wf__verification__mod_ver_report
+    :complies:
 
     Verification reports shall be automatically generated. These may be independent documents (i.e. not integrated into sphinx documentation).
     The content of the reports is specified in :need:`gd_temp__platform_ver_report` and :need:`gd_temp__mod_ver_report`.
@@ -143,6 +154,8 @@ Test Linking to 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_test
+    :complies:
 
     The following checks shall be implemented on test metadata:
 
@@ -157,6 +170,8 @@ Test Linking to 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_test
+    :complies:
 
     The following checks shall be implemented on test metadata: