From 02ee2bccfe3c170d86a50fa97914f498548611b4 Mon Sep 17 00:00:00 2001 From: "Schu, Markus" Date: Wed, 15 Jul 2026 08:41:56 +0200 Subject: [PATCH 1/6] update of change management to consider new FEP proposal --- .../platform/docs/change/decision_record.rst | 12 +++++++++++- .../change_management_concept.rst | 14 ++++++++++---- .../change_management_getstrt.rst | 8 +++++--- .../change_management_workflow.rst | 16 ++++++++-------- 4 files changed, 34 insertions(+), 16 deletions(-) diff --git a/process/folder_templates/platform/docs/change/decision_record.rst b/process/folder_templates/platform/docs/change/decision_record.rst index 530d09de83..fe3954b508 100644 --- a/process/folder_templates/platform/docs/change/decision_record.rst +++ b/process/folder_templates/platform/docs/change/decision_record.rst @@ -32,7 +32,7 @@ In each DR file, include the following sections: :id: dec_rec____, dec_rec__<arch|proc|strat|infra|int>__<slug> :status: <proposed|accepted|deprecated|rejected|superseded> :tracking: <link to GitHub issue URL, required once a DR is confirmed> - :version: 1 + :version: 2 :affects: <link> <Description> @@ -77,6 +77,14 @@ In each DR file, include the following sections: ------------------------------ <your text> + + Impact Analysis (Optional) + -------------------------- + The impact analysis template can be used to detail out the impact on safety/security. + Copy the relevant parts from the impact analysis template and fill it out. + The impact analysis template is available here [1]_. + + .. attention:: The above directive must be updated according to your decision record. @@ -90,3 +98,5 @@ In each DR file, include the following sections: - Add ``Context`` to describe the issue or motivation behind this decision or change (mandatory) - Add ``decision`` to detail the proposed change or decision (mandatory) - Add ``consequences`` to explain the impact of this change, including what becomes easier or more difficult (recommended) + +.. [1] The impact analysis template is available here: :ref:`Impact Analysis Template <chm_impact_analysis_templates>` diff --git a/process/process_areas/change_management/change_management_concept.rst b/process/process_areas/change_management/change_management_concept.rst index 1eeb10f56c..8b14158c94 100644 --- a/process/process_areas/change_management/change_management_concept.rst +++ b/process/process_areas/change_management/change_management_concept.rst @@ -18,7 +18,7 @@ Concept Description .. doc_concept:: Concept Description :id: doc_concept__change_process :status: valid - :version: 1 + :version: 2 :tags: change_management In this section a concept for the Change Management will be discussed. Inputs for this concepts @@ -95,12 +95,14 @@ Activities for a Change Request Creation of the Change Request ============================== -Use the content :ref:`Feature Request Template <chm_feature_templates>` or -:ref:`Component Request Template <chm_component_templates>` to create a Change Request. + +Use the content :ref:`Decision Record Template <decision_record_template>` to create a +Change Request. In case safety or security is affected, in addition the impact analysis template : :ref:`Impact Analysis Template <chm_impact_analysis_templates>` can be used to detail -out the impact on safety/security. +out the impact on safety/security. Copy the relevant parts from the impact analysis +template into the decision record and fill it out. The impact analysis tool (:need:`gd_req__change_tool_impact_analysis`) can support to here to identify the affected work products. @@ -131,6 +133,10 @@ monitored. The Change Request implementation must be tracked until it is closed. +Use the content :ref:`Feature Request Template <chm_feature_templates>` or +:ref:`Component Request Template <chm_component_templates>` to document the implementation +of a new feature or component or the modification of an existing feature or component. + The status of the Change Request must be communicated by the :need:`Project Lead <rl__project_lead>` (for feature requests) and the lead of the :need:`Delivery Team <rl__delivery_team>` (for component requests) until diff --git a/process/process_areas/change_management/change_management_getstrt.rst b/process/process_areas/change_management/change_management_getstrt.rst index 2bd3cb384d..7a5e43361f 100644 --- a/process/process_areas/change_management/change_management_getstrt.rst +++ b/process/process_areas/change_management/change_management_getstrt.rst @@ -18,7 +18,7 @@ Getting Started .. doc_getstrt:: Getting Started on Change Management :id: doc_getstrt__change_process :status: valid - :version: 1 + :version: 2 :tags: change_management This document describes the steps to create a change request, and further to analyze, @@ -32,9 +32,11 @@ Examples for change requests: * New component for parsing a protocol introduced (component request). * API change for an existing component (component modification). -Therefore guidelines :need:`gd_temp__change_feature_request` and + +Therefore guideline :need:`gd_temp__change_decision_record` is available. This guideline +is complemented by the :need:`gd_temp__change_feature_request`, :need:`gd_temp__change_component_request`, :need:`gd_guidl__change_change_request` and -a :need:`doc_concept__change_process` are available. +:need:`doc_concept__change_process`. General Workflow **************** diff --git a/process/process_areas/change_management/change_management_workflow.rst b/process/process_areas/change_management/change_management_workflow.rst index 1ab9dd64c4..af1b28ac2e 100644 --- a/process/process_areas/change_management/change_management_workflow.rst +++ b/process/process_areas/change_management/change_management_workflow.rst @@ -37,8 +37,8 @@ For a detailed explanation of workflows and their role within the process model, gd_temp__change_component_request[version==1], gd_temp__change_impact_analysis[version==1], gd_temp__component_classification[version==1], - gd_temp__change_decision_record[version==1] - :has: doc_concept__change_process[version==1], doc_getstrt__change_process[version==1] + gd_temp__change_decision_record[version==2] + :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] The Change Request is created. @@ -65,8 +65,8 @@ For a detailed explanation of workflows and their role within the process model, gd_temp__change_component_request[version==1], gd_temp__change_impact_analysis[version==1], gd_temp__component_classification[version==1], - gd_temp__change_decision_record[version==1] - :has: doc_concept__change_process[version==1], doc_getstrt__change_process[version==1] + gd_temp__change_decision_record[version==2] + :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] The Change Request is analyzed. @@ -94,8 +94,8 @@ For a detailed explanation of workflows and their role within the process model, gd_temp__change_component_request[version==1], gd_temp__change_impact_analysis[version==1], gd_temp__component_classification[version==1], - gd_temp__change_decision_record[version==1] - :has: doc_concept__change_process[version==1], doc_getstrt__change_process[version==1] + gd_temp__change_decision_record[version==2] + :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] The Change Request is implemented and monitored. @@ -133,8 +133,8 @@ For a detailed explanation of workflows and their role within the process model, gd_temp__change_component_request[version==1], gd_temp__change_impact_analysis[version==1], gd_temp__component_classification[version==1], - gd_temp__change_decision_record[version==1] - :has: doc_concept__change_process[version==1], doc_getstrt__change_process[version==1] + gd_temp__change_decision_record[version==2] + :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] The Change Request is closed. From f1042b7442dd8107071152c73874045a5d733361 Mon Sep 17 00:00:00 2001 From: "Schu, Markus" <markus.schu@accenture.com> Date: Wed, 15 Jul 2026 08:50:26 +0200 Subject: [PATCH 2/6] increase version for decision record --- .../guidance/change_management_decision_record_template.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/process/process_areas/change_management/guidance/change_management_decision_record_template.rst b/process/process_areas/change_management/guidance/change_management_decision_record_template.rst index a7238aaa6a..f9daf005ce 100644 --- a/process/process_areas/change_management/guidance/change_management_decision_record_template.rst +++ b/process/process_areas/change_management/guidance/change_management_decision_record_template.rst @@ -20,7 +20,7 @@ Decision Record Template .. gd_temp:: Decision Record Template :id: gd_temp__change_decision_record :status: valid - :version: 1 + :version: 2 :complies: std_req__aspice_40__SWE-2-BP3[version==1], std_req__aspice_40__iic-17-00[version==1] For the content see here: :ref:`decision_record_template`. From 5984b2b11db338386f6372cc3512fbc30a6c843e Mon Sep 17 00:00:00 2001 From: "Schu, Markus" <markus.schu@accenture.com> Date: Wed, 15 Jul 2026 08:54:30 +0200 Subject: [PATCH 3/6] add delete or keep proposal in feature request template --- .../platform/features/feature_name/index.rst | 26 +++++++++---------- 1 file changed, 13 insertions(+), 13 deletions(-) diff --git a/process/folder_templates/platform/features/feature_name/index.rst b/process/folder_templates/platform/features/feature_name/index.rst index 69cfb821ed..b17be29e6d 100644 --- a/process/folder_templates/platform/features/feature_name/index.rst +++ b/process/folder_templates/platform/features/feature_name/index.rst @@ -36,7 +36,7 @@ - Adjust ``status`` to be ``valid`` - Adjust ``safety``, ``security`` and ``tags`` according to your needs -Feature flag +Feature flag (KEEP this section) ============ To activate this feature, use the following feature flag: @@ -47,7 +47,7 @@ To activate this feature, use the following feature flag: The feature flag must reflect the feature name in snake_case. Further, it is prepended with ``experimental_``, as long as the feature is not yet stable. -Abstract +Abstract (KEEP this section) ======== [Provide the feature and a brief summary of the feature] @@ -66,7 +66,7 @@ Abstract [A short (~200 word) description of the contribution being addressed.] -Motivation +Motivation (KEEP this section) ========== [Clearly explain why the existing platform/project solution is inadequate to address the topic that the CR solves.] @@ -77,7 +77,7 @@ Motivation Motivation may based on criteria as resource requirements, scheduling issues, risks, benefits, etc. CRs submissions without sufficient motivation may be rejected. -Rationale +Rationale (KEEP this section) ========= [Describe why particular design decisions were made.] @@ -87,7 +87,7 @@ Rationale For the documentation of the decision the :need:`gd_temp__change_decision_record` can be used. -Specification +Specification (KEEP this section) ============= [Describe the requirements, architecture of any new feature.] or @@ -97,13 +97,13 @@ Specification A CR shall specify the stakeholder requirements as part of our platform/project. Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR). -Backwards Compatibility +Backwards Compatibility (Delete this section) ======================= [Describe potential impact (especially including safety and security impacts) and severity on pre-existing platform/project elements.] -Security Impact +Security Impact (Delete this section) =============== [How could a malicious user take advantage of this new/modified feature?] @@ -123,7 +123,7 @@ If applicable, which additional security measures must be implemented to mitigat [Methods will be defined later in Process area Security Analysis] These analyses may not be available at the time of creation of the feature (request) but content will be improved iteratively. -Safety Impact +Safety Impact (Delete this section) ============= [How could the safety be impacted by the new/modified feature?] @@ -146,13 +146,13 @@ For new feature contributions: [What is the expected ASIL level?] -License Impact +License Impact (Keep this section) ============== [How could the copyright impacted by the license of the new contribution?] -How to Teach This +How to Teach This (Keep this section) ================= [How to teach users, new and experienced, how to apply the CR to their work.] @@ -161,7 +161,7 @@ How to Teach This For a CR that adds new functionality or changes behaviour, it is helpful to include a section on how to teach users, new and experienced, how to apply the CR to their work. -Rejected Ideas +Rejected Ideas (Keep this section) ============== [Why certain ideas that were brought while discussing this CR were not ultimately pursued.] @@ -172,7 +172,7 @@ Rejected Ideas This both helps record the thought process behind the final version of the CR as well as preventing people from bringing up the same rejected idea again in subsequent discussions. In a way this section can be thought of as a breakout section of the Rationale section that is focused specifically on why certain ideas were not ultimately pursued. -Open Issues +Open Issues (Keep this section) =========== [Any points that are still being decided/discussed.] @@ -182,7 +182,7 @@ Open Issues Those ideas should be recorded so people know that they are being thought about but do not have a concrete resolution. This helps make sure all issues required for the CR to be ready for consideration are complete and reduces people duplicating prior discussion. -Footnotes +Footnotes (Keep this section) ========= [A collection of footnotes cited in the CR, and a place to list non-inline hyperlink targets.] From 9c26b5e81654cee2e28c26c9477f1f39e5334027 Mon Sep 17 00:00:00 2001 From: "Schu, Markus" <markus.schu@accenture.com> Date: Wed, 15 Jul 2026 09:05:42 +0200 Subject: [PATCH 4/6] fix doc build errors --- .../platform/docs/change/decision_record.rst | 3 ++- .../platform/features/feature_name/index.rst | 26 +++++++++---------- .../safety_management_workflow.rst | 2 +- 3 files changed, 16 insertions(+), 15 deletions(-) diff --git a/process/folder_templates/platform/docs/change/decision_record.rst b/process/folder_templates/platform/docs/change/decision_record.rst index fe3954b508..d2748b0e92 100644 --- a/process/folder_templates/platform/docs/change/decision_record.rst +++ b/process/folder_templates/platform/docs/change/decision_record.rst @@ -82,8 +82,9 @@ In each DR file, include the following sections: -------------------------- The impact analysis template can be used to detail out the impact on safety/security. Copy the relevant parts from the impact analysis template and fill it out. - The impact analysis template is available here [1]_. + The impact analysis template is available in [1]. +The impact analysis template is available here [1]_. .. attention:: The above directive must be updated according to your decision record. diff --git a/process/folder_templates/platform/features/feature_name/index.rst b/process/folder_templates/platform/features/feature_name/index.rst index b17be29e6d..5eb7bd5cd2 100644 --- a/process/folder_templates/platform/features/feature_name/index.rst +++ b/process/folder_templates/platform/features/feature_name/index.rst @@ -37,7 +37,7 @@ - Adjust ``safety``, ``security`` and ``tags`` according to your needs Feature flag (KEEP this section) -============ +================================ To activate this feature, use the following feature flag: @@ -48,7 +48,7 @@ To activate this feature, use the following feature flag: long as the feature is not yet stable. Abstract (KEEP this section) -======== +============================ [Provide the feature and a brief summary of the feature] @@ -67,7 +67,7 @@ Abstract (KEEP this section) [A short (~200 word) description of the contribution being addressed.] Motivation (KEEP this section) -========== +============================== [Clearly explain why the existing platform/project solution is inadequate to address the topic that the CR solves.] @@ -78,7 +78,7 @@ Motivation (KEEP this section) CRs submissions without sufficient motivation may be rejected. Rationale (KEEP this section) -========= +============================= [Describe why particular design decisions were made.] @@ -88,7 +88,7 @@ Rationale (KEEP this section) Specification (KEEP this section) -============= +================================= [Describe the requirements, architecture of any new feature.] or [Describe the change to requirements, architecture, implementation, process, documentation, infrastructure of any change request.] @@ -98,13 +98,13 @@ Specification (KEEP this section) Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR). Backwards Compatibility (Delete this section) -======================= +============================================= [Describe potential impact (especially including safety and security impacts) and severity on pre-existing platform/project elements.] Security Impact (Delete this section) -=============== +===================================== [How could a malicious user take advantage of this new/modified feature?] @@ -124,7 +124,7 @@ If applicable, which additional security measures must be implemented to mitigat These analyses may not be available at the time of creation of the feature (request) but content will be improved iteratively. Safety Impact (Delete this section) -============= +=================================== [How could the safety be impacted by the new/modified feature?] @@ -147,13 +147,13 @@ For new feature contributions: License Impact (Keep this section) -============== +================================== [How could the copyright impacted by the license of the new contribution?] How to Teach This (Keep this section) -================= +===================================== [How to teach users, new and experienced, how to apply the CR to their work.] @@ -162,7 +162,7 @@ How to Teach This (Keep this section) Rejected Ideas (Keep this section) -============== +================================== [Why certain ideas that were brought while discussing this CR were not ultimately pursued.] @@ -173,7 +173,7 @@ Rejected Ideas (Keep this section) In a way this section can be thought of as a breakout section of the Rationale section that is focused specifically on why certain ideas were not ultimately pursued. Open Issues (Keep this section) -=========== +=============================== [Any points that are still being decided/discussed.] @@ -183,7 +183,7 @@ Open Issues (Keep this section) This helps make sure all issues required for the CR to be ready for consideration are complete and reduces people duplicating prior discussion. Footnotes (Keep this section) -========= +============================= [A collection of footnotes cited in the CR, and a place to list non-inline hyperlink targets.] diff --git a/process/process_areas/safety_management/safety_management_workflow.rst b/process/process_areas/safety_management/safety_management_workflow.rst index a086692bfb..4f043d3270 100644 --- a/process/process_areas/safety_management/safety_management_workflow.rst +++ b/process/process_areas/safety_management/safety_management_workflow.rst @@ -161,7 +161,7 @@ Safety Management Workflows wp__sw_component_class[version==1], wp__safety_tailoring[version==1] :output: wp__issue_track_system[version==1] - :contains: gd_temp__change_component_request[version==1], gd_temp__change_decision_record[version==1], gd_temp__change_impact_analysis[version==1] + :contains: gd_temp__change_component_request[version==1], gd_temp__change_decision_record[version==2], gd_temp__change_impact_analysis[version==1] :has: doc_concept__safety_management_process[version==1], doc_getstrt__safety_management_process[version==1] | In accordance with ISO 26262-2:2018 section 5.2.2.3 d/e (Impact Analysis), the project implements a dedicated workflow for analyzing change requests. From 85b94286b84c11f20279ccf55a77c71fb93e7307 Mon Sep 17 00:00:00 2001 From: "Schu, Markus" <markus.schu@accenture.com> Date: Wed, 15 Jul 2026 11:03:55 +0200 Subject: [PATCH 5/6] update review findings --- .../platform/docs/change/decision_record.rst | 3 +- .../platform/features/feature_name/index.rst | 106 +++--------------- .../change_management_workflow.rst | 16 +-- .../change_management_feature_template.rst | 2 +- ...ge_management_impact_analysis_template.rst | 14 +-- .../safety_management_workflow.rst | 2 +- 6 files changed, 33 insertions(+), 110 deletions(-) diff --git a/process/folder_templates/platform/docs/change/decision_record.rst b/process/folder_templates/platform/docs/change/decision_record.rst index d2748b0e92..681fa18154 100644 --- a/process/folder_templates/platform/docs/change/decision_record.rst +++ b/process/folder_templates/platform/docs/change/decision_record.rst @@ -80,7 +80,8 @@ In each DR file, include the following sections: Impact Analysis (Optional) -------------------------- - The impact analysis template can be used to detail out the impact on safety/security. + The impact analysis template can be used to detail out the impact on the platform + and if applicable, especially for safety/security. Copy the relevant parts from the impact analysis template and fill it out. The impact analysis template is available in [1]. diff --git a/process/folder_templates/platform/features/feature_name/index.rst b/process/folder_templates/platform/features/feature_name/index.rst index 5eb7bd5cd2..241a71fd11 100644 --- a/process/folder_templates/platform/features/feature_name/index.rst +++ b/process/folder_templates/platform/features/feature_name/index.rst @@ -22,7 +22,7 @@ .. document:: [Your Feature Name] :id: doc__feature_name :status: draft - :version: 1 + :version: 2 :safety: ASIL_B :security: YES :realizes: wp__feat_request[version==1] @@ -36,8 +36,8 @@ - Adjust ``status`` to be ``valid`` - Adjust ``safety``, ``security`` and ``tags`` according to your needs -Feature flag (KEEP this section) -================================ +Feature flag +============ To activate this feature, use the following feature flag: @@ -47,8 +47,8 @@ To activate this feature, use the following feature flag: The feature flag must reflect the feature name in snake_case. Further, it is prepended with ``experimental_``, as long as the feature is not yet stable. -Abstract (KEEP this section) -============================ +Abstract +======== [Provide the feature and a brief summary of the feature] @@ -66,8 +66,8 @@ Abstract (KEEP this section) [A short (~200 word) description of the contribution being addressed.] -Motivation (KEEP this section) -============================== +Motivation +========== [Clearly explain why the existing platform/project solution is inadequate to address the topic that the CR solves.] @@ -77,18 +77,8 @@ Motivation (KEEP this section) Motivation may based on criteria as resource requirements, scheduling issues, risks, benefits, etc. CRs submissions without sufficient motivation may be rejected. -Rationale (KEEP this section) -============================= - -[Describe why particular design decisions were made.] - -.. note:: - The rationale should provide evidence of consensus within the community and discuss important objections or concerns raised during discussion. - For the documentation of the decision the :need:`gd_temp__change_decision_record` can be used. - - -Specification (KEEP this section) -================================= +Specification +============= [Describe the requirements, architecture of any new feature.] or [Describe the change to requirements, architecture, implementation, process, documentation, infrastructure of any change request.] @@ -97,72 +87,16 @@ Specification (KEEP this section) A CR shall specify the stakeholder requirements as part of our platform/project. Thereby the :need:`rl__project_lead` will approve these requirements as part of accepting the CR (e.g. merging the PR with the CR). -Backwards Compatibility (Delete this section) -============================================= - -[Describe potential impact (especially including safety and security impacts) and severity on pre-existing platform/project elements.] - - -Security Impact (Delete this section) -===================================== - -[How could a malicious user take advantage of this new/modified feature?] - -.. note:: - If there are security concerns in relation to the CR, those concerns should be explicitly written out to make sure reviewers of the CR are aware of them. - -Which security requirements are affected or has to be changed? -Could the new/modified feature enable new threat scenarios? -Could the new/modified feature enable new attack paths? -Could the new/modified feature impact functional safety? -If applicable, which additional security measures must be implemented to mitigate the risk? - -.. note:: - Use Trust Boundary, Defense in Depth Analysis and/or Security Software Critically Analysis, - Vulnerability Analysis. - [Methods will be defined later in Process area Security Analysis] - These analyses may not be available at the time of creation of the feature (request) but content will be improved iteratively. - -Safety Impact (Delete this section) -=================================== - -[How could the safety be impacted by the new/modified feature?] - -.. note:: - If there are safety concerns in relation to the CR, those concerns should be explicitly written out to make sure reviewers of the CR are aware of them. - Link here to the filled out :need:`Impact Analysis Template <gd_temp__change_impact_analysis>` or copy the template in this chapter. - -Which safety requirements are affected or has to be changed? -Could the new/modified feature be a potential common cause or cascading failure initiator? -If applicable, which additional safety measures must be implemented to mitigate the risk? - -.. note:: - Use Dependency Failure Analysis and/or Safety Software Critically Analysis. - [Methods will be defined later in Process area Safety Analysis] - These analyses may not be available at the time of creation of the feature (request) but content will be improved iteratively. - -For new feature contributions: - -[What is the expected ASIL level?] - - -License Impact (Keep this section) -================================== - -[How could the copyright impacted by the license of the new contribution?] - - -How to Teach This (Keep this section) -===================================== +How to Teach This +================= [How to teach users, new and experienced, how to apply the CR to their work.] .. note:: For a CR that adds new functionality or changes behaviour, it is helpful to include a section on how to teach users, new and experienced, how to apply the CR to their work. - -Rejected Ideas (Keep this section) -================================== +Rejected Ideas +============== [Why certain ideas that were brought while discussing this CR were not ultimately pursued.] @@ -172,18 +106,8 @@ Rejected Ideas (Keep this section) This both helps record the thought process behind the final version of the CR as well as preventing people from bringing up the same rejected idea again in subsequent discussions. In a way this section can be thought of as a breakout section of the Rationale section that is focused specifically on why certain ideas were not ultimately pursued. -Open Issues (Keep this section) -=============================== - -[Any points that are still being decided/discussed.] - -.. note:: - While a CR is in draft, ideas can come up which warrant further discussion. - Those ideas should be recorded so people know that they are being thought about but do not have a concrete resolution. - This helps make sure all issues required for the CR to be ready for consideration are complete and reduces people duplicating prior discussion. - -Footnotes (Keep this section) -============================= +Footnotes +========= [A collection of footnotes cited in the CR, and a place to list non-inline hyperlink targets.] diff --git a/process/process_areas/change_management/change_management_workflow.rst b/process/process_areas/change_management/change_management_workflow.rst index af1b28ac2e..66acecbadd 100644 --- a/process/process_areas/change_management/change_management_workflow.rst +++ b/process/process_areas/change_management/change_management_workflow.rst @@ -33,9 +33,9 @@ For a detailed explanation of workflows and their role within the process model, wp__cmpt_request[version==1] :output: wp__issue_track_system[version==1], wp__feat_request[version==1], wp__cmpt_request[version==1] :contains: gd_guidl__change_change_request[version==1], - gd_temp__change_feature_request[version==1], + gd_temp__change_feature_request[version==2], gd_temp__change_component_request[version==1], - gd_temp__change_impact_analysis[version==1], + gd_temp__change_impact_analysis[version==2], gd_temp__component_classification[version==1], gd_temp__change_decision_record[version==2] :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] @@ -61,9 +61,9 @@ For a detailed explanation of workflows and their role within the process model, wp__cmpt_request[version==1] :output: wp__issue_track_system[version==1], wp__feat_request[version==1], wp__cmpt_request[version==1] :contains: gd_guidl__change_change_request[version==1], - gd_temp__change_feature_request[version==1], + gd_temp__change_feature_request[version==2], gd_temp__change_component_request[version==1], - gd_temp__change_impact_analysis[version==1], + gd_temp__change_impact_analysis[version==2], gd_temp__component_classification[version==1], gd_temp__change_decision_record[version==2] :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] @@ -90,9 +90,9 @@ For a detailed explanation of workflows and their role within the process model, :input: wp__issue_track_system[version==1], wp__feat_request[version==1], wp__cmpt_request[version==1] :output: wp__issue_track_system[version==1], wp__feat_request[version==1], wp__cmpt_request[version==1] :contains: gd_guidl__change_change_request[version==1], - gd_temp__change_feature_request[version==1], + gd_temp__change_feature_request[version==2], gd_temp__change_component_request[version==1], - gd_temp__change_impact_analysis[version==1], + gd_temp__change_impact_analysis[version==2], gd_temp__component_classification[version==1], gd_temp__change_decision_record[version==2] :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] @@ -129,9 +129,9 @@ For a detailed explanation of workflows and their role within the process model, :input: wp__issue_track_system[version==1], wp__feat_request[version==1], wp__cmpt_request[version==1] :output: wp__issue_track_system[version==1], wp__feat_request[version==1], wp__cmpt_request[version==1] :contains: gd_guidl__change_change_request[version==1], - gd_temp__change_feature_request[version==1], + gd_temp__change_feature_request[version==2], gd_temp__change_component_request[version==1], - gd_temp__change_impact_analysis[version==1], + gd_temp__change_impact_analysis[version==2], gd_temp__component_classification[version==1], gd_temp__change_decision_record[version==2] :has: doc_concept__change_process[version==2], doc_getstrt__change_process[version==2] diff --git a/process/process_areas/change_management/guidance/change_management_feature_template.rst b/process/process_areas/change_management/guidance/change_management_feature_template.rst index 4ae4f94682..005fea45ee 100644 --- a/process/process_areas/change_management/guidance/change_management_feature_template.rst +++ b/process/process_areas/change_management/guidance/change_management_feature_template.rst @@ -20,7 +20,7 @@ Feature Template .. gd_temp:: Feature Request Template :id: gd_temp__change_feature_request :status: valid - :version: 1 + :version: 2 :complies: std_req__aspice_40__SUP-10-BP1[version==1], std_req__aspice_40__SUP-10-BP2[version==1], std_req__aspice_40__SUP-10-BP3[version==1], diff --git a/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst b/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst index 4f9778660c..4b118ad3da 100644 --- a/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst +++ b/process/process_areas/change_management/guidance/change_management_impact_analysis_template.rst @@ -20,7 +20,7 @@ Impact Analysis Template .. gd_temp:: Impact Analysis Template :id: gd_temp__change_impact_analysis :status: valid - :version: 1 + :version: 2 :complies: std_req__aspice_40__SUP-10-BP2[version==1], std_req__aspice_40__iic-18-57[version==1], std_req__iso26262__support_8431[version==1], @@ -72,16 +72,14 @@ Estimates for Realization A draft realization plan may support the realization proposal. +Potential Impact on the platform +-------------------------------- + + Potential Impact on Security ----------------------------- -Add the potential impact in the chapter Security Impact of the concerned Feature Request -(compare :need:`Feature Request Template <gd_temp__change_feature_request>`) or Component Request -(compare :need:`Component Request Template <gd_temp__change_component_request>`). + Potential Impact on Safety -------------------------- - -Add the potential impact in the chapter Safety Impact of the concerned Feature Request -(compare :need:`Feature Request Template <gd_temp__change_feature_request>`) or Component Request -(compare :need:`Component Request Template <gd_temp__change_component_request>`). diff --git a/process/process_areas/safety_management/safety_management_workflow.rst b/process/process_areas/safety_management/safety_management_workflow.rst index 4f043d3270..8ea0397de7 100644 --- a/process/process_areas/safety_management/safety_management_workflow.rst +++ b/process/process_areas/safety_management/safety_management_workflow.rst @@ -161,7 +161,7 @@ Safety Management Workflows wp__sw_component_class[version==1], wp__safety_tailoring[version==1] :output: wp__issue_track_system[version==1] - :contains: gd_temp__change_component_request[version==1], gd_temp__change_decision_record[version==2], gd_temp__change_impact_analysis[version==1] + :contains: gd_temp__change_component_request[version==1], gd_temp__change_decision_record[version==2], gd_temp__change_impact_analysis[version==2] :has: doc_concept__safety_management_process[version==1], doc_getstrt__safety_management_process[version==1] | In accordance with ISO 26262-2:2018 section 5.2.2.3 d/e (Impact Analysis), the project implements a dedicated workflow for analyzing change requests. From 1b515a0fd62285f2921bc2b0ba7a25a4387f09fa Mon Sep 17 00:00:00 2001 From: "Schu, Markus" <markus.schu@accenture.com> Date: Wed, 15 Jul 2026 11:24:13 +0200 Subject: [PATCH 6/6] Add information for scope change --- .../change_management/change_management_concept.rst | 3 +++ 1 file changed, 3 insertions(+) diff --git a/process/process_areas/change_management/change_management_concept.rst b/process/process_areas/change_management/change_management_concept.rst index 8b14158c94..7eb5f78245 100644 --- a/process/process_areas/change_management/change_management_concept.rst +++ b/process/process_areas/change_management/change_management_concept.rst @@ -33,6 +33,9 @@ As features are built-up by components a Change Request is also needed to add ne components or to modify the scope of existing components. All statements here for components are also valid for *SW Modules*. +As a rule of thumb, a Change Request is needed, if feature or component requirements +are changed. + Inputs ******