Skip to content

Improvement: Add types details to requirements_concept #205

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
aschemmel-tech merged 1 commit into from
Oct 16, 2025
Merged

Improvement: Add types details to requirements_concept #205

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
5 changes: 5 additions & 0 deletions process/process_areas/requirements_engineering/requirements_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -183,6 +183,11 @@ Following attributes need to be filled manually for each requirement:
* - Requirements Type
- The requirement type defines which category the requirement relates to. Following categories are defined: [Functional, Interface, Process, Non-Functional]

- Functional: If implemented can be verified by a test (unit, integration)
- Interface: Does not define a functionality but the API provided to use the functionality
- Process: If implemented can be verified by reviewing the process description (sub-type of non-functional)
- Non-Functional: If implemented can be checked by review/analysis (of e.g. code, documentation)

Note that the linking to the requirements is affected by these types, see :need:`gd_req__req_linkage_architecture`

Following attributes are automatically generated:
Expand Down
Loading