From c91444c98ccfbde672fc8f60ad1352491e37ec8f Mon Sep 17 00:00:00 2001 From: Stephan Lo Date: Thu, 28 Nov 2024 10:02:33 +0100 Subject: [PATCH] doc(poc-structure): WiP some thoughts on the composition or physical structure of the product --- README.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index ca7f690..74b9b56 100644 --- a/README.md +++ b/README.md @@ -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): -![](./use-cases.png) \ No newline at end of file +![](./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