Architecture documentation of the Eclipse Tractus-X Dataspace Management (new portal), following the
arc42 template (TRG 1.05). The binding source for the behaviour of every module is the
module specification (README.md, openapi.yaml, open-points.md per module) and its framework
(FRAMEWORK.md); this documentation summarises the architecture and links to the specification instead of repeating it.
| No. | Chapter | Content |
|---|---|---|
| 1 | Introduction and goals | Purpose, quality goals, stakeholders |
| 2 | Architecture constraints | Technical, organisational and legal constraints |
| 3 | Context and scope | OSP 2.0: the installation of an OSP and its neighbours |
| 4 | Solution strategy | Modular monolith, flows as data, own data per module |
| 5 | Building block view | Capabilities and modules |
| 6 | Runtime view | Onboarding of a company |
| 7 | Deployment view | Helm chart, containers, configuration |
| 8 | Crosscutting concepts | Tokens and permissions, events, errors, secrets |
| 9 | Architecture decisions | Decision log |
| 10 | Quality requirements | Quality scenarios |
| 11 | Risks and technical debt | Known risks and open points |
| 12 | Glossary | Terms |
Diagrams are written in Mermaid directly in the Markdown files (TRG 1.04), so they can be edited like text; GitHub renders them, and the Mermaid Live Editor can be used to preview changes.
This work is licensed under the CC-BY-4.0.