-
Notifications
You must be signed in to change notification settings - Fork 76
High level Architecture for LoLa #374
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.
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
Conversation
|
The created documentation from the pull request is available at: docu-html |
|
@ltekieli could you help investigate this? |
|
@AlexanderLanin @MaximilianSoerenPollak dot is missing from the CI installation. @LittleHuba should do the trick. |
|
@ltekieli in general PlantUML in CI is working fine: https://eclipse-score.github.io/score/main/guidance/docs-as-code.html#plantuml |
It seems plantuml does not use dot always, but in this case it's definately complaining about it missing. |
You are right. It depends on the diagram type whether dot is required. I'll create a new issue for this. |
|
The created documentation from the pull request is available at: docu-html |
433a9dc to
4ff641a
Compare
License Check Results🚀 The license check preparation job ran successfully. Status: Click to expand output |
Draft of the HLA
Draft of the HLA
- create interface - resolve links
4ff641a to
ebb0e81
Compare
An own directory helps better structure the toc and sort assets.
Do not show all headings in feature request in TOC. Show architecture and roadmap in TOC.
Separate architecture into feature and component. For now component architecture is stored in feature tree because of tooling issues.

This PR brings the high-level architecture of LoLa to the IPC feature. It is the first step towards breaking down the feature requirements into component requirements.
The focus of the architecture documentation is twofold.
Firstly, we show the overall concept behind the solution
Secondly, we discuss the key aspects of the feature request, to show how they are solved.
The second point is done implicitly while explaining the overall concept, to have a better flow of the documentation.