Skip to content

Fix safety management roles and escalation #434

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
PandaeDo merged 1 commit into from
Dec 4, 2025
Merged

Fix safety management roles and escalation #434

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
2 changes: 1 addition & 1 deletion process/process_areas/safety_management/guidance/guideline_safety_management.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ Safety Management Guideline

**Communication:**

Development teams are interdisciplinary, so the regular (sprint) planning and review meetings enable communication (as defined in in the project specific :need:`project management plan <wp__project_mgt>`). Another main communication means are the Pull Request reviews.
Development teams are interdisciplinary, so the regular planning and review meetings enable communication (as defined in in the project specific :need:`project management plan <wp__project_mgt>`). Another main communication means are the Pull Request reviews.
Also the standard Eclipse Foundation communication strategies are used (e.g. mailing lists)

**Safety anomalies:**
Expand Down
13 changes: 9 additions & 4 deletions process/process_areas/safety_management/safety_management_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,16 +40,21 @@ Inputs
Stakeholders
^^^^^^^^^^^^

#. :need:`Project Lead <rl__project_lead>`

* planning of development for module and for platform projects

#. :need:`Safety Manager <rl__safety_manager>`

* main responsible to ensure ISO 26262 compliance in the project
* role definition in :doc:`/process_areas/safety_management/safety_management_roles`
* status reporting of safety activities

#. :need:`Project Lead <rl__project_lead>`

* planning of development for platform projects

#. :need:`Committer <rl__committer>`

* planning of development for module projects (as a Module Project Lead)
* performing safety related development

#. :need:`External Auditor <rl__external_auditor>`

* Performs independent safety audits and formal document reviews (e.g., safety plans, safety packages, safety analyses).
Expand Down
3 changes: 2 additions & 1 deletion process/roles/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -133,9 +133,10 @@ Project Feature Teams
:id: rl__module_team
:status: valid
:tags: cross_functional
:contains: rl__project_lead, rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer
:contains: rl__safety_manager, rl__quality_manager, rl__security_manager, rl__contributor, rl__committer

The module team is responsible for all artifacts within the module SEooCs. Each module has only one responsible team but a team may also be responsible for several (small) modules.
One of the committers in the team acts as the "Module Project Manager" and is responsible for planning and reporting.

Project Roles List
------------------
Expand Down
Loading