Skip to content

linking all feature requirement to architecture - #626

Open
MaciejKaszynski wants to merge 6 commits into
eclipse-score:mainfrom
etas-contrib:arch-links
Open

MaciejKaszynski wants to merge 6 commits into
eclipse-score:mainfrom
etas-contrib:arch-links

Conversation

@MaciejKaszynski

@MaciejKaszynski MaciejKaszynski commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

Adding links to feature architecture with the feature requirements that are considered for v1

Comment thread docs/features/lifecycle/architecture/health_monitor.rst
Comment thread docs/features/lifecycle/architecture/launch_manager.rst Outdated
Comment thread docs/features/lifecycle/architecture/lifecycle_client.rst Outdated
Comment thread score/launch_manager/docs/architecture/component_architecture.rst Outdated
Comment thread score/launch_manager/docs/architecture/component_architecture.rst Outdated
Comment thread docs/features/lifecycle/architecture/launch_manager.rst Outdated
Comment thread docs/features/lifecycle/architecture/_assets/launch_manager_running_dep.puml Outdated
Lifecycle Client
################

The :term:`Launch Manager` provides interfaces for communication with launched

@NicolasFussberger NicolasFussberger Sep 14, 2026

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 wonder if some of this content should be moved to the LaunchManager page.

The Lifecycle interface seems to be only relevant to the Score Applications.
Though this distinction btw. Score and Native applications seems more like Launch Manager concept to me.

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.

I did some moving on 5824e6c
I think some of this text should be maybe even moved in to the specific interface docs but I will make another ticket to sort this out and add some docs for all interfaces.

Comment thread docs/features/lifecycle/architecture/launch_manager.rst Outdated
Comment thread docs/features/lifecycle/architecture/launch_manager.rst Outdated
Comment thread docs/features/lifecycle/architecture/launch_manager.rst Outdated
Comment thread docs/features/lifecycle/architecture/launch_manager.rst Outdated
Comment thread docs/features/lifecycle/architecture/index.rst Outdated
@NicolasFussberger

Copy link
Copy Markdown
Contributor

Currently the hierarchical structure under "Feature Architecture" looks a bit random:
grafik

We have on the same level Components, APIs, concepts (external monitoring).
I wonder if we can find some consistent structure below feature architecture.

Maybe structure according to static, dynamic architecture?
Or structure according to Interfaces, components, concepts?

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.

3 participants