From bea2a88f2fb1072a6256e514a5d0a074102c6bc2 Mon Sep 17 00:00:00 2001 From: aschemmel-git Date: Tue, 29 Sep 2026 13:29:25 +0200 Subject: [PATCH] Modify valid_from/until attribute requirements --- .../guidance/requirements_process_reqs.rst | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) 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 686b01815e..b288a18609 100644 --- a/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst +++ b/process/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst @@ -188,36 +188,36 @@ Process Requirement Attributes .. gd_req:: Requirement attribute: valid_from :id: gd_req__req_attr_valid_from :status: valid - :version: 1 + :version: 2 :tags: manual_prio_2, attribute :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 and feature requirements can have a validity attribute that tells + Stakeholder, feature 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. - Milestone shall be valid release version tag, e.g. v1.0.2 as defined in - Platform Release Note Template: :need:`gd_temp__rel_plat_rel_note`. Thus the - corresponding requirement is valid from the defined milestone, including it. + Milestone should be a valid platform release version tag, e.g. v1.0.2 as defined in + Platform Release planning. If a requirement is not planned already this can also be a potential future milestone. + The corresponding requirement is valid from the defined milestone, including it. .. gd_req:: Requirement attribute: valid_until :id: gd_req__req_attr_valid_until :status: valid - :version: 1 + :version: 2 :tags: manual_prio_2, attribute :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 and feature requirements can have a validity attribute that tells + Stakeholder, feature and component requirements can have a validity attribute that tells until which milestone the requirement is part of a feature. This validity attribute is defined as excluding the defined milestone. - Milestone shall be valid release version tag, e.g. v1.0.2 as defined in - Platform Release Note Template: :need:`gd_temp__rel_plat_rel_note`. Thus the - corresponding requirement is only valid until the defined milestone, excluding it. + Milestone shall be a valid platform release version tag, e.g. v1.0.2 as defined in + Platform Release planning. + The corresponding requirement is only valid until the defined milestone, excluding it. .. _process_requirement_linkage: