Skip to content

Conversation

@PandaeDo
Copy link
Contributor

@PandaeDo PandaeDo commented Jun 2, 2025

No description provided.

@github-actions
Copy link

github-actions bot commented Jun 2, 2025

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

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.

Reviewed corrections based on findings from eclipse-score/score#902

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.

Please generate a new documentation, when you have finished resolving all findings

.. figure:: _assets/safety_analysis_workflow.drawio.svg
:align: center
:width: 80%
:name: safety_analysis_workflow_fig
Copy link
Contributor

Choose a reason for hiding this comment

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

the image mentions a platform architecture wp, what is that, not defined. As discussed today, we may introduce an static overview image, currently defined as roadmap, and call that platform architecture, and a dependency graph, which is the basis for that defined platform feature dfa?

What about the numbers, are they explained somewhere? What are the relationship workflow names? Workflows are only called Analyse something, but Perform is not there, so can they be deleted?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed it in that way that I used the discussed description as platform feature architecture

Detailed description which steps are need for a safety analysis. In general the workflow is shown in :ref:`safety_analysis_workflow_fig`

#. To analyse the Platform Architecture DFA shall be executed.
#. Perform DFA on the Platform Architecture.
Copy link
Contributor

Choose a reason for hiding this comment

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

I would scale down these points to the workflows defined, so perform does not exists, remove it is done during analysis anyhow or not?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Changed description as discussed. Orientated on the structure of requirements engineering

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.

See comments before

@masc2023
Copy link
Contributor

masc2023 commented Jun 4, 2025

@PandaeDo , @aschemmel-tech , are the activities for Safety Analysis covered by the Safety Management Plan? If yes, some comments, hints should be added

@PandaeDo PandaeDo force-pushed the vohae_safety_analysis branch from d54b0be to 878fce2 Compare June 5, 2025 12:20
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.

most findings resolved, some additional remarks added

aschemmel-tech
aschemmel-tech previously approved these changes Jun 6, 2025
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.

All good now from my side

The analysis starts at feature level. With a DFA shall be analysed if there are dependent failures which have to be considered. The analysis
shall be done in the way that we use the static and dynamic diagrams. The following picture shall show the perspective of the User.

.. _safety_analysis_feature_example:
Copy link
Contributor

Choose a reason for hiding this comment

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

Does the Key not found error not require a message before, e.g. get key?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We have seven dynamic diagrams for kvs. I picked a simple one for the example to show how the analysis shall be done.

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.

At least the missing work product, workflow should be added before initial merge

MaximilianSoerenPollak and others added 6 commits June 10, 2025 15:24
CI/CD workflows changed, adapting to changes there.
Increasing docs-as-code to get various bugfixes.
Ref: closes #310

process: switch process description of safety analysis to process_description

process: rebase

Ref: closes #310

process: solve building error

Ref: closes #310

process: including actual review findings. clearance of platform level after decission

Ref: closes #316

process: review

process: include review findings

Ref: closes #316

process: fix building errors

Ref: closes #316

process: include review finding

Ref: closes #316

process: include review findings

Ref: closes #310

process: include review findings

Ref: closes #310
@PandaeDo PandaeDo force-pushed the vohae_safety_analysis branch from fc91db0 to 1d644b3 Compare June 10, 2025 13:26
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.

Fine for the first, initial version

@masc2023 masc2023 merged commit c607d5a into eclipse-score:main Jun 10, 2025
5 checks passed
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.

4 participants