Skip to content

Sharpen Dependable Element Definition #555

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
masc2023 merged 1 commit into from
Feb 6, 2026
Merged

Sharpen Dependable Element Definition #555

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
4 changes: 2 additions & 2 deletions process/general_concepts/_assets/score_building_blocks_example.drawio.svg
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
13 changes: 8 additions & 5 deletions process/general_concepts/score_building_blocks_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,13 +42,16 @@ Assumptions of Use** (blue box, top, 7nd column).
The platform consists of **Features** (yellow box, middle, 2nd column).

Further the project provides **Dependable Elements** (red box, middle, 1st column),
which can also be developed as a SEooC and it can be delivered as part of a Delivery
Container. A Dependable Element is consists of **Components** (green box, middle, 2nd column)
or a set of components realizing a Feature of the platform. In this sense a Dependable
Element is the highest abstraction level in our model. A Dependable Element,
which can also be developed as a SEooC and are delivered as part of a **Delivery
Container**. This Delivery Container can contain one or more Dependable Elements,
it is versioned and can be depended on by other Delivery Containers.
A Dependable Element consists of one or more **Components** (green box, middle, 2nd column),
which are in the same Delivery Container as the Dependable Element.
In this sense a Dependable Element is the highest abstraction level in our model. A Dependable Element,
delivered in a Delivery Container represents e.g. executable code or a library.
The **Dependable Element View** (red box, middle, 1st column) documents the mapping of
components to a Dependable Element.
components to a Dependable Element. Note that the term "Dependable" hints that the
element can have safety and/or security relevance (but also non of these).

Components are the major building blocks of the platform. Components consists of **Units**
(grey box, bottom, 2nd column), the lowest level in our model. The represent the source code,
Expand Down
12 changes: 6 additions & 6 deletions process/roles/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,8 +118,8 @@ Project Development Roles
(Eclipse) Open Source Role, person(s) who is(are) responsible for coordinating the resolution of Vulnerabilities within the Project.
By default, the project Security Team includes all Committers. However, the Project may choose a different arrangement and establish specific criteria for team nominations.

Project Feature Teams
---------------------
Project Teams
-------------

.. role:: Platform Team
:id: rl__platform_team
Expand All @@ -129,14 +129,14 @@ Project Feature Teams

The platform team is responsible for all artifacts within the platform SEooC. Additionally it is also responsible for the overall process including its support by tooling.

.. role:: Module Team
:id: rl__module_team
.. role:: Delivery Team
:id: rl__delivery_team
Copy link
Contributor

@masc2023 masc2023 Feb 6, 2026

Choose a reason for hiding this comment

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

Seems that role is currently not used at all?

Copy link
Contributor Author

@aschemmel-tech aschemmel-tech Feb 6, 2026

Choose a reason for hiding this comment

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

Yes, but would leave nevertheless because it is in practice part of our project organization.

:status: valid
:tags: cross_functional
: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.
The delivery team is responsible for all artifacts within the Delivery Container SEooCs containing the Dependable Elements. Each Delivery Container has only one responsible team.
One of the committers in the team acts as the "Project Manager" and is responsible for planning and reporting.

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