Migrate UMLet diagrams to PlantUML/draw.io

[LittleHuba]

This epic is about migrating all diagrams in https://github.com/eclipse-score/communication/tree/main/score/mw/com/design from UMLet to PlantUML.

The S-CORE process specifies that diagrams have to be drawn using PlantUML (and if not supported editable SVGs with Draw.io).

UML has several weak points in its compatibility with language features of C++. In those instances try to find the most understandable way that works with PlantUML.
For diagrams where this is not possible (or ones that loose their message when migrated to PlantUML) migrate to draw-io instead. Make sure to save as "editable SVG".

[LittleHuba]

Assignees

Andreas Kaluza
Daniel Gerstle @gdaniel-cb
Chrisopher Schwager

[kalu-an]

Meeting Minutes (@LittleHuba, @gdaniel-cb, @kalu-an, Chrisopher Schwager)

• 1:1 transformation for all diagrams within design directory
• goal is all to have in PlantUML, case issues in placement or limits of PlantUML possibilities go with drawio
• For every <diagram_name>.uxf a subtask is created with <diagram_name>
• Acceptance criteria = Plant online server renders diagram successful
• Fork & subtask creation @gdaniel-cb

Theme

• FR to be created @kalu-an
• Intermediate placement of theme -> design
• Intermediate usage -> include directive within *.puml diagram !include ../puml-theme-score.puml

[kalu-an]

Related issue for theme integration indented to be a feature_request Add PlantUML Theme in S-CORE

[AlexanderLanin]

The S-CORE process specifies that diagrams have to be drawn using PlantUML

FYI: I've already reported that to the process team, as the process should not dictate any tooling. E.g. in infrastructure we are commonly using mermaid, due to its native github integration.

[cr1sschwager]

Created the PR with the first migrated diagrams. I will further report the progress there

[cr1sschwager]

@LittleHuba PR is ready. Please have a look.

[LittleHuba]

Status update:

• Merge conflicts resolved
• PR was split into multiple PRs (based on directories)

Future steps:

• Request was raised to split complex diagrams to help readers Migrate UMLet to PlantUML #24 (review)
  -> Recommendation to do this in a second step. It should also be considered to reduce the level of detail where it does not help to convey the key message. Follow-Up ticket to be created @LittleHuba