Skip to content

Modify valid_from/until attribute description #800

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
masc2023 merged 2 commits into from
Sep 30, 2026
Merged

Modify valid_from/until attribute description #800

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7319cf7
Modify valid_from/until attribute description
aschemmel-tech Sep 29, 2026
c10394a
Modify valid_from/until attribute description - fix
aschemmel-tech Sep 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions process/process_areas/requirements_engineering/guidance/requirements_guideline.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -261,12 +261,16 @@ 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 and feature requirements, but not for
the component requirements, as these are expected to be developed during small implementation cycles.
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,
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
Expand Down
2 changes: 1 addition & 1 deletion ...s/process_areas/requirements_engineering/guidance/requirements_process_reqs.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

@masc2023 masc2023 Sep 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So Stkh, Feat Requirements needs now both mandatory, valid_from, until? Current meta model has only valdi_from mandatory, until is optional, seems ok for me, as if it shall be used for ever, valid_from is enough, until not required, means if not exists, valid for all future version

@aschemmel-tech aschemmel-tech Sep 30, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agree to keep valid_until optional, this is described in "gd_req__req_attr_valid_until" which says "Stakeholder, feature and component requirements can have a validity attribute"

@masc2023 masc2023 Sep 30, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I see, the until is still can, reading only the diff here, does not show it, so it is fine

from which milestone onwards the requirement is part of a feature.

This validity attribute is defined as including the defined milestone.
Expand Down
Loading