From 7319cf7bad63ae13ae7a773c3bf027d5ab09d5bd Mon Sep 17 00:00:00 2001 From: aschemmel-git Date: Tue, 29 Sep 2026 14:33:53 +0200 Subject: [PATCH 1/2] Modify valid_from/until attribute description --- .../guidance/requirements_guideline.rst | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst b/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst index 99e5f81822..2f7abbc7b3 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst @@ -265,8 +265,12 @@ For the "only specification" use case, the following attributes can be used: - :need:`gd_req__req_attr_valid_from` - :need:`gd_req__req_attr_valid_until` -These attributes can be used for stakeholder and feature requirements, but not for -the component requirements, as these are expected to be developed during small implementation cycles. +These attributes can be used for stakeholder, feature and component requirements. +Release version numbers are not synced between platform and modules, therefore for the validity +attribute only the planned (future) and done platform release numbers are allowed. +It is not recommended to use validity attribute for the component requirements, +as these are expected to be developed based on feature requirements in sync and during +small implementation cycles. If an existing requirement needs to be reworked for the new function it will be split in two. The requirement with the old specification will be valid_until the milestone before the From c10394abc2d3d3aea8733fb375d82bd6a39b0b53 Mon Sep 17 00:00:00 2001 From: aschemmel-git Date: Wed, 30 Sep 2026 08:56:15 +0200 Subject: [PATCH 2/2] Modify valid_from/until attribute description - fix --- .../guidance/requirements_guideline.rst | 4 ++-- .../guidance/requirements_process_reqs.rst | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst b/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst index 2f7abbc7b3..6bc548458e 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_guideline.rst @@ -261,11 +261,11 @@ A use case where the specification AND implementation of a new/modified feature already during the development time of an earlier milestone than the feature is planned can be realized by the feature flags (for new features) or by branching off. -For the "only specification" use case, the following attributes can be used: +For the "only specification" use case, the following attributes are defined: - :need:`gd_req__req_attr_valid_from` - :need:`gd_req__req_attr_valid_until` -These attributes can be used for stakeholder, feature and component requirements. +These attributes are defined for stakeholder, feature and component requirements. Release version numbers are not synced between platform and modules, therefore for the validity attribute only the planned (future) and done platform release numbers are allowed. It is not recommended to use validity attribute for the component requirements, 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 b288a18609..b61ec436b7 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst @@ -193,7 +193,7 @@ Process Requirement Attributes :satisfies: wf__req_stkh_req[version==1], wf__req_feat_req[version==1] :complies: std_req__aspice_40__SWE-1-BP2[version==1], std_req__aspice_40__iic-17-54[version==1] - Stakeholder, feature and component requirements can have a validity attribute that tells + Stakeholder and feature requirements shall and component requirements can have a validity attribute that tells from which milestone onwards the requirement is part of a feature. This validity attribute is defined as including the defined milestone.