Michal.Wrobel/edp-doc
1
0
Fork 0
forked from DevFW-CICD/edp-doc
Code Pull requests Activity

doc(poc-structure): WiP some thoughts on the composition or physical structure of the product

Browse source
This commit is contained in:
Stephan Lo 2024-11-28 10:02:33 +01:00
parent 2cb8e342a3
commit c91444c98c
1 changed files with 11 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -33,4 +33,14 @@ This is the Storybook of the PoC content structure (content is depicted top righ
This is the illustration of the [use cases (aka 'functionality') in the PoC content](https://confluence.telekom-mms.com/display/IPCEICIS/Proof+of+Concept+2024): This is the illustration of the [use cases (aka 'functionality') in the PoC content](https://confluence.telekom-mms.com/display/IPCEICIS/Proof+of+Concept+2024):
![](./use-cases.png) ![](./use-cases.png)
## Technical composition
The 'edf_poc'-product should be as self-contained as possible.
Thus all parts coming from upstream repos should have a physical copy in this repo with a reference to the upstream repo. Therefore we need a mapping table from parts here to references in upstreams.
Alternative: Submodules
Proposal: The final product will be a export of the repo