Skip to content

rename relations for SysML compatibility #618

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 3 commits into from
May 19, 2026
+8 −8
Merged

rename relations for SysML compatibility #618

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ce7947a
rename relations for Codebeamer compatibility
RSingh1511 Mar 23, 2026
09e30ff
remove out-of-scope gd_req and inline example changes
RSingh1511 Apr 10, 2026
534e302
Revert gd_req/arch links per review, add satisfied_by for requirements
RSingh1511 May 13, 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
8 changes: 4 additions & 4 deletions process/folder_templates/features/feature_name/requirements/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -41,11 +41,11 @@ Feature Requirements
:reqtype: Process
:security: NO
:safety: ASIL_B
:satisfies: stkh_req__requirements__template
:derived_from: stkh_req__requirements__template
:valid_from: v0.0.1
:valid_until: v1.0.1
:status: invalid
:belongs_to: feat__feature_name
:satisfied_by: feat__feature_name

The Feature shall do xyz to the user to bring him to this condition at this time.

Expand All @@ -66,9 +66,9 @@ Feature Requirements
The above directives must be updated according to your feature requirements.

- Replace the example content by the real content for your first requirement (according to :need:`gd_guidl__req_engineering`)
- Set ``belongs_to`` with a link to feature ID
- Set ``satisfied_by`` with a link to feature ID
- Set ``reqtype`` with a link to the right value (<Functional|Interface|Process|Non-Functional>)
- Set ``satisfies`` with a link to the right stakeholder requirement
- Set ``derived_from`` with a link to the right stakeholder requirement
- Adjust ``safety`` and ``security`` to the right value (ASIL B/QM; YES/NO)
- Add other needed requirements for your feature
- Adjust ``valid_from`` and ``valid_until`` to the right version numbers
Expand Down
8 changes: 4 additions & 4 deletions ...folder_templates/modules/module_name/component_name/docs/requirements/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -44,9 +44,9 @@ Component Requirements
:reqtype: Process
:security: YES
:safety: ASIL_B
:satisfies: feat_req__feature_name__some_title
:derived_from: feat_req__feature_name__some_title
:status: invalid
:belongs_to: comp__component_name_template
:satisfied_by: comp__component_name_template

The Component shall do xyz to another component to bring it to this condition at this time

Expand All @@ -56,8 +56,8 @@ Component Requirements
The above directive must be updated according to your component requirements.

- Replace the example content by the real content for your first requirement
- Set ``satistifes`` with links to Feature requirements
- Set ``belongs_to`` with a link to the right Component id
- Set ``derived_from`` with links to Feature requirements
- Set ``satisfied_by`` with a link to the right Component id
- Set ``safety`` and ``security`` to the right value
- Set the status to valid and start the review/merge process
- Add other needed requirements for your component
Expand Down
Loading