Skip to content

first draft of dependable element#372

Draft
hoe-jo wants to merge 4 commits intomainfrom
joho_add_dependable_element_message_passing
Draft

first draft of dependable element#372
hoe-jo wants to merge 4 commits intomainfrom
joho_add_dependable_element_message_passing

Conversation

@hoe-jo
Copy link
Copy Markdown
Contributor

@hoe-jo hoe-jo commented Apr 29, 2026

No description provided.

@castler castler marked this pull request as draft May 4, 2026 05:29
@hoe-jo hoe-jo force-pushed the joho_add_dependable_element_message_passing branch from 2d6c69a to 999ebf2 Compare May 5, 2026 06:24
@@ -0,0 +1,12 @@
# *******************************************************************************
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 should be under the folder requirements

load("@trlc//:trlc.bzl", "trlc_requirements", "trlc_requirements_test")

trlc_requirements(
name = "feature_requirements_trlc",
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.

Why is this not in the feature requirements folder?

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.

Why do we call it _trlc at the end?

I also do not call my cc_library foo_cpp

":component_requirements_trlc",
],
visibility = ["//visibility:public"],
)
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.

We should have here a test_suite that executes all requirements based tests.

Comment on lines +20 to +29
trlc_requirements(
name = "failure_modes",
srcs = [
"failure_modes.trlc",
],
spec = [
"@score_tooling//bazel/rules/rules_score/trlc/config:score_requirements_model",
],
visibility = ["//visibility:public"],
)
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.

Can we please avoid this copy n paste and hide this directly in the FMEA bazel rule, that you define there directly the trlc files?

Comment on lines +31 to +43
trlc_requirements(
name = "control_measures",
srcs = [
"control_measures.trlc",
],
spec = [
"@score_tooling//bazel/rules/rules_score/trlc/config:score_requirements_model",
],
visibility = ["//visibility:public"],
deps = [
":failure_modes",
],
)
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.

Should we not place this in the "component requirements"?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Depends if the control measure is a component requirement or an AoU

@@ -0,0 +1,49 @@
# *******************************************************************************
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.

let's please call this folder software_unit_design

Comment thread score/message_passing/design/BUILD Outdated
Comment on lines +20 to +24
architectural_design(
name = "message_passing_design",
static = ["client-server.md"],
visibility = ["//visibility:public"],
)
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.

We should move this to software_architectural_design

Comment thread score/message_passing/BUILD Outdated
],
tags = ["FFI"],
visibility = [
"//score/message_passing/dependability:__subpackages__",
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.

I think these visibilities are wrong, and should be removed and the units should be moved to the code.

Comment thread MODULE.bazel Outdated
@@ -1,3 +1,16 @@
# *******************************************************************************
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 file holds already a copyright...

Comment thread MODULE.bazel
commit = "4c83c578069768c6133e4268b63929646754f6a6",
commit = "87de61455a9f699041dd0ca5a2c9cf0fcd771476",
remote = "https://github.com/eclipse-score/tooling.git",
)
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.

you will need to adapt the example folder as well, for this to work when you remove the dev dependency.

@hoe-jo hoe-jo force-pushed the joho_add_dependable_element_message_passing branch from 999ebf2 to d8b95f6 Compare May 6, 2026 09:19
"Ensure @score_tooling//tools/sphinx:plantuml is in sphinx_build data."
)
else:
plantuml = str(_plantuml_path)
)
else:
plantuml = str(_plantuml_path)
plantuml_output_format = "svg_obj"
import bazel_sphinx_needs

from pathlib import Path
import os
@hoe-jo hoe-jo force-pushed the joho_add_dependable_element_message_passing branch 4 times, most recently from 19041d7 to ef88b39 Compare May 6, 2026 15:41
@hoe-jo hoe-jo force-pushed the joho_add_dependable_element_message_passing branch from ef88b39 to 76f8202 Compare May 7, 2026 13:41
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.

2 participants