process: add DR-005 for independent feature delivery #2346

arsibo · 2025-12-16T07:35:38Z

Add design decision to enable SCORE features as independent SEooC delivery units in dedicated repositories.

github-actions · 2025-12-16T07:39:54Z

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

a-zw · 2025-12-16T09:29:22Z

Generate HTML version of the DR: https://eclipse-score.github.io/score/pr-2346/design_decisions/DR-005-process.html

a-zw · 2025-12-16T10:43:14Z

docs/design_decisions/DR-005-process.rst

+This creates the necessity to provide features as independent SEooC
+units. Furthermore, the current repository structure does not allow
+features to be released independently from the platform repository.
+


A lot here seems to depend on the understanding of "feature" and "module". Please, add a clear definition here.

I am sorry, but for me the "word definitions" are still unclear, especially if it comes to the version 2b. Sub-feature, sub-component. Hard to understand.

masc2023 · 2025-12-17T14:31:53Z

docs/design_decisions/_assets/alternative_1_simplified.puml

-"Integration Repo" ..> "Module Repo" : uses
-"S-Core Repo" -[hidden]d- "Module Repo"
+"Integration Repo" ..> "SW-Module Repo" : uses
+"S-Core Repo" -[hidden]d- "SW-Module Repo"


S-CORE, as used allover the reset of the document

Add design decision to enable SCORE features as independent SEooC delivery units in dedicated repositories (incl. correction of review findings).

aschemmel-tech

see inline comments

docs/design_decisions/DR-005-process.rst

aschemmel-tech · 2026-01-13T14:55:57Z

docs/design_decisions/DR-005-process.rst

+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+The platform artifacts are located in the S-CORE platform repository.
+The feature artifacts are located in the SW module repository.


Please add something like "A SW module is no architecture element, just a “container” for work products to do a collective versioning/baseline. Especially it is not a component or a set of components as it is currently."

See here, this is not quite correct, https://eclipse-score.github.io/process_description/main/general_concepts/score_building_blocks_concept.html#

Further the project provides Software Modules (red box, middle, 1st column), which can also be developed as a SEooC. A Software Module is defined as a Component (green box, middle, 2nd column) or a set of components realizing a Feature of the platform. In this sense a Software Module is the highest level component in our model. A Software Module represents e.g. executable code or a library.

The formulation above was discussed and agreed in the meeting on Jan-13. It will need a modification to our current definition as you rightly point out.

"SW module repository" should be replaced by "Delivery Container repository" - see metamodel https://eclipse-score.github.io/process_description/main/_images/score_building_blocks_meta_model.drawio.svg

FScholPer · 2026-01-14T07:10:16Z

For me this is highly coupled with #2400. My proposal would be to first decide the working model or at least to discuss both in one meeting

…d prevent duplicates POC for eclipse-score/score#2346

…mentation POC for eclipse-score#2346

… architecture POC for eclipse-score/score#2346

POC for eclipse-score/score#2346 Replace local path override with git override using branch arsibo_dr_005_poc for score_platform dependency. This allows the build to work with remote branch after pushing.

…e module dependencies POC for eclipse-score/score#2346

POC for eclipse-score/score#2346 Replace local path override with git override using branch arsibo_dr_005_poc for score_platform dependency. This allows the build to work with remote branch after pushing.

POC for eclipse-score/score#2346 Add comprehensive architecture documentation with focus on architecture modeling: - Logging feature (mw-fr_logging) with feature architecture - Component architectures for: - data_router_recorder - datarouter - file_recorder - log_bridge - recorders Note: Documentation templates are not yet completely filled out. Further refinement and completion of templates is required in future iterations.

…ependencies POC for eclipse-score/score#2346 Replace local path overrides with git overrides using branch arsibo_dr_005_poc for: - score_docs_as_code - score_platform - score_baselibs - score_baselibs_rust This allows the build to work with remote branches after pushing.

POC for eclipse-score/score#2346 Replace local path override with git override using branch arsibo_dr_005_poc for score_platform dependency. This allows the build to work with remote branch after pushing.

aschemmel-tech

Alternative 2b not approved

aschemmel-tech · 2026-02-05T07:49:08Z

docs/design_decisions/DR-005-process.rst

+
+       Features bound to platform release cycle, split between platform
+       and modules
+     - **(+)**


The artifacts in the SW-platform are relevant for the "Feature SEooC" still, Stakeholder requirements are the "Assumed Technical Safety Requirements" which need to be mapped to the "System Requirements" of the User. And also the platform wide AoU are relevant and need to be covered by any Feature user. So you would still depend on one platform release version.

aschemmel-tech · 2026-02-05T07:52:10Z

docs/design_decisions/DR-005-process.rst

+   * - Independence of Release / Topic Coherence (How independently can
+       features be released and how well are related artifacts kept
+       together?)
+     - **(-)**


In my understanding eclipse-score/tooling#95 proposes a way to produce all needed documentation for a SEooC within one module repo by using also artefacts defined in other used repos including the platform repo. So this would enable also staying with alternative 1.

aschemmel-tech

Comments added/revised based on discussions in process community

aschemmel-tech · 2026-02-11T10:25:21Z

docs/design_decisions/DR-005-process.rst

+   :caption: Alternative 2: Dedicated Feature Repository Architecture
+
+
+Alternative 2b: Feature in SW Module Repository with Sub-Features (System of Systems)


I would avoid to create a new level of architecture "Sub-Features" - because actually the reuse is done on component level. I.e. a feature is derived into internal and external component requirements and the external ones are linked to an external component (not feature) or matching external component requirements.

aschemmel-tech · 2026-02-11T10:41:00Z

docs/design_decisions/DR-005-process.rst

+
+.. uml:: _assets/DR-005-alternative_2c_simplified.puml
+   :caption: Alternative 2c: Hierarchical Feature Repository Architecture
+


In considering https://eclipse-score.github.io/score/pr-2560/design_decisions/DR-001-arch.html another alternative would be:
3 - feature artefacts are partly in platform repository and partly in module repository
this should support the intended development workflows

platform repo contains "Feature", "Feature Requirements" and "Logical Arc. Interface" - this supports platform architecture modelling in "Consistent Stack" mode

module repo contains "Feature Architecture" - as this is the decomposition into components which is a "module related" work, and also the "Feature Safety Analysis" and "Feature Integration Tests" verifying the Architecture.

masc2023 mentioned this pull request Dec 16, 2025

Improvement: correct architecture elements and modify component template eclipse-score/process_description#462

Merged

6 tasks

a-zw reviewed Dec 16, 2025

View reviewed changes

anmittag assigned arsibo Dec 17, 2025

masc2023 reviewed Dec 17, 2025

View reviewed changes

arsibo force-pushed the arsibo_dr_feature_as_seooc branch from 6997d14 to 9cd5776 Compare January 9, 2026 13:30

process: add DR-005 for independent feature delivery

6eb33f3

Add design decision to enable SCORE features as independent SEooC delivery units in dedicated repositories (incl. correction of review findings).

arsibo force-pushed the arsibo_dr_feature_as_seooc branch from 7c6de66 to 6eb33f3 Compare January 9, 2026 14:01

arsibo marked this pull request as ready for review January 9, 2026 14:05

arsibo requested review from PhilipPartsch, aschemmel-tech and pahmann as code owners January 9, 2026 14:05

arsibo requested review from FScholPer, antonkri, johannes-esr and qor-lb January 9, 2026 14:10

arsibo mentioned this pull request Jan 13, 2026

DR-005: Release strategy #2400

Draft

aschemmel-tech reviewed Jan 13, 2026

View reviewed changes

4og mentioned this pull request Jan 15, 2026

Migrate module documentation to eclipse-score/baselibs eclipse-score/baselibs#43

Open

2 tasks

FScholPer mentioned this pull request Jan 30, 2026

[module api] Initial version eclipse-score/tooling#95

Merged

arsibo added a commit to etas-contrib/score_docs-as-code that referenced this pull request Feb 2, 2026

feat: Enhance UML component rendering to support nested structures an…

73d9ffe

…d prevent duplicates POC for eclipse-score/score#2346

arsibo added a commit to etas-contrib/score_score that referenced this pull request Feb 2, 2026

docs: Remove logging feature and component references from score docu…

6829d69

…mentation POC for eclipse-score#2346

arsibo added a commit to etas-contrib/score_baselibs that referenced this pull request Feb 2, 2026

docs: Add documentation for Log C++ component and baselibs_cpp module…

3eb97cf

… architecture POC for eclipse-score/score#2346

arsibo added a commit to etas-contrib/score_baselibs_rust that referenced this pull request Feb 2, 2026

docs: Add architecture documentation for log_rust component and updat…

a4d3feb

…e module dependencies POC for eclipse-score/score#2346

arsibo mentioned this pull request Feb 2, 2026

process: DR-005 POC eclipse-score/logging#52

Draft

10 tasks

aschemmel-tech requested changes Feb 5, 2026

View reviewed changes

masc2023 mentioned this pull request Feb 8, 2026

DR-001-Arch: Consistent Stack vs. Reference Integration #2560

Open

aschemmel-tech requested changes Feb 11, 2026

View reviewed changes

		:caption: Alternative 2: Dedicated Feature Repository Architecture


		Alternative 2b: Feature in SW Module Repository with Sub-Features (System of Systems)


		.. uml:: _assets/DR-005-alternative_2c_simplified.puml
		:caption: Alternative 2c: Hierarchical Feature Repository Architecture

process: add DR-005 for independent feature delivery #2346

Are you sure you want to change the base?

process: add DR-005 for independent feature delivery #2346

Uh oh!

Conversation

arsibo commented Dec 16, 2025

Uh oh!

github-actions bot commented Dec 16, 2025

Uh oh!

a-zw commented Dec 16, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aschemmel-tech left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

FScholPer commented Jan 14, 2026

Uh oh!

aschemmel-tech left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aschemmel-tech left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

aschemmel-tech Feb 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

aschemmel-tech Feb 11, 2026 •

edited

Loading