Skip to content

Improvement: Safety Management ML 2#437

Merged
masc2023 merged 2 commits intoeclipse-score:mainfrom
qorix-group:vohae_Safety_Management_ML2
Dec 8, 2025
Merged

Improvement: Safety Management ML 2#437
masc2023 merged 2 commits intoeclipse-score:mainfrom
qorix-group:vohae_Safety_Management_ML2

Conversation

@PandaeDo
Copy link
Contributor

@PandaeDo PandaeDo commented Dec 5, 2025

Solve open review findings #398

@github-actions
Copy link

github-actions bot commented Dec 5, 2025

The created documentation from the pull request is available at: docu-html

Copy link
Contributor

@masc2023 masc2023 left a comment

Choose a reason for hiding this comment

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

Needs discussion, cannot see currently a feature safety plan, only attachment for Platform Plan, called Feature Planning?

^^^^^^^^^^^^

The SW platform project defines two levels of planning: platform and module. There will be one safety plan on platform level and several safety plans on module level (one for each module).
The SW platform project defines different levels of planning: platform, feature and module. There will be one safety plan on platform level and
Copy link
Contributor

Choose a reason for hiding this comment

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

Is that a change, currently the feature plan is part of platform plan, no separate template?
E.g. https://eclipse-score.github.io/score/main/features/frameworks/feo/safety_planning/index.html

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Need some time but now I understand it. Changed it back

Copy link
Contributor

@aschemmel-tech aschemmel-tech left a comment

Choose a reason for hiding this comment

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

see inline comment

@pahmann
Copy link
Member

pahmann commented Dec 6, 2025

@attifunel want to put your attention to this.

Copy link
Contributor

@aschemmel-tech aschemmel-tech left a comment

Choose a reason for hiding this comment

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

Comment resolved

@masc2023 masc2023 merged commit 67f6f61 into eclipse-score:main Dec 8, 2025
5 checks passed
* Create/Maintain Safety Plan
* Approve Component Classification
* Approve Safety Package
* Approve Safety Audit
Copy link
Contributor

@attifunel attifunel Dec 11, 2025

Choose a reason for hiding this comment

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

What is the exact meaning here? Audit is assigned to an external entity, why Safety Manager should approve? Perhaps "plan" + "support"?

Copy link
Contributor Author

@PandaeDo PandaeDo Dec 11, 2025

Choose a reason for hiding this comment

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

I think it makes sense that we will approve the external Audit. With this we can document that we agree on the Audit report. That the Safety Manager and the Process Community will support is defined in the workflow of the Safety Audit. Also relevant is, that we defined that all workflows has an approval. I hope this answered your question. If not I would invite to to "Eclipse S-CORE Safety Topics, Safety Management and Execution (Safety Manager Roles required)" every Tuesday, where we also can discuss your question with the complete community.

Copy link
Contributor

Choose a reason for hiding this comment

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

You need to see that in the context of the define workflows,
https://eclipse-score.github.io/process_description/main/process_areas/safety_management/safety_management_workflow.html#wf__p_fs_audit

improvement in concept description could be to include the workflows, where the Safety Manager has stakes in

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants