Skip to content

mw/com: expose public assumptions_of_use target for safety analysis AoUs - #937

Open
akritisingh1109 wants to merge 1 commit into
eclipse-score:mainfrom
akritisingh1109:add-mw-com-assumptions-of-use
Open

mw/com: expose public assumptions_of_use target for safety analysis AoUs#937
akritisingh1109 wants to merge 1 commit into
eclipse-score:mainfrom
akritisingh1109:add-mw-com-assumptions-of-use

Conversation

@akritisingh1109

Copy link
Copy Markdown

Adds a public assumptions_of_use Bazel target wrapping aou.trlc under score/mw/com/dependability/safety_analysis

)

assumptions_of_use(
name = "assumptions_of_use",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This feels wrong. With this change we have the file aou.trlc in two targets, fmea target and the assumptions_of_use target.
If the problem is that aou.trlc contains AoUs and control measures, we should just split it first.
I cannot see the AoUs linked in the fmea in https://eclipse-score.github.io/tooling/latest/user_guide/dependability_analysis.html#fmea, is this correct? Are AoUs not linked to an fmea? I would have expected that the AoUs that are the result of hte FMEA they are linked also to the fmea.

@akritisingh1109
akritisingh1109 force-pushed the add-mw-com-assumptions-of-use branch 7 times, most recently from 57a826e to 45bb1a7 Compare August 31, 2026 04:46
Adds a public assumptions_of_use Bazel target wrapping aou.trlc under score/mw/com/dependability/safety_analysis, following the existing message_passing pattern. This enables downstream typed derived_from traceability references to mw::com AoUs without a local patch.
@akritisingh1109
akritisingh1109 force-pushed the add-mw-com-assumptions-of-use branch from 45bb1a7 to 2739193 Compare August 31, 2026 05:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants