Skip to content

Add requirement author description #577

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 1 commit into from
Feb 20, 2026
+13 −5
Merged

Add requirement author description #577

Show file tree
Hide file tree
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
17 changes: 12 additions & 5 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 @@ -52,7 +52,7 @@ Stakeholders for the requirements
* Verify that the specification is fulfilled by the elements under test
* Consider AoUs for test case specification

#. :need:`Safety Architect <rl__safety_manager>`
#. :need:`Safety Architect <rl__safety_engineer>`

* *Dependent Failure Analysis*

Expand All @@ -62,13 +62,13 @@ Stakeholders for the requirements

* Detailed element description to identify systematic errors within the element under investigation

#. :need:`Security Architect <rl__security_manager>`
#. :need:`Security Architect <rl__security_engineer>`

* Trust Boundary Analysis
* Defense in Depth Analysis
* Qualitative Security Analysis (TARA or at least Attack Potential Analysis with impact category Safety)
Copy link
Contributor

@RolandJentschETAS RolandJentschETAS Feb 19, 2026

Choose a reason for hiding this comment

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

Safety ? Or is security meaned here ?

Copy link
Contributor Author

@aschemmel-tech aschemmel-tech Feb 19, 2026

Choose a reason for hiding this comment

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

I think "impact category Safety" is correct here

Copy link
Contributor

@masc2023 masc2023 Feb 19, 2026

Choose a reason for hiding this comment

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

Security, Analysis, but considering potential impact on safety


#. :need:`Platform/Tooling SW Developer <rl__committer>`
#. :need:`Module/Tooling SW Developer <rl__delivery_team>`

* Implement the SW according to its specification
* Create traceability by linking its specification to code
Expand All @@ -80,9 +80,16 @@ Stakeholders for the requirements
* Get detailed information concerning the specification of a feature
* Be informed about its boundary conditions (AoUs)

#. :need:`Platform SW Developer of the Reference Integration <rl__committer>`
#. :need:`Platform SW Developer of the Reference Integration <rl__platform_team>`

* Requirements for Integration
* Implements Requirements for Integration

As the platform is developed in an open source working mode, in principle every :need:`rl__contributor`
can create SW requirements (as can be seen in :ref:`requirements_workflows`) but always
a :need:`rl__committer` or :need:`rl__project_lead` has to approve.
In practice the expectation is that the above stakeholders also define requirements,
mostly the :need:`SW Architect <rl__committer>` and competent persons from the module's :need:`rl__delivery_team`.
The person responsible is planned in the issue tickets for requirements definition.

Standard Requirements
=====================
Expand Down
1 change: 1 addition & 0 deletions process/process_areas/requirements_engineering/requirements_workflow.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,7 @@
# SPDX-License-Identifier: Apache-2.0
# *******************************************************************************

.. _requirements_workflows:

Requirements Engineering Workflows
##################################
Expand Down