This is not a questions so I am not sure if this is the correct place to post this? But I hope it is shareable and informative, it was fun anyway and I hope it prompts other users to contribute any similar experiments!
I suspect like other QDC users we have several dataflow constructs where output from dataflow A is input to dataflow B and so on...
An example of such a dependency tree is given below, where Octagons are QDC Sources, Rectangles Dataflows and Ellipses are Entities. The arrowheads show the direction of the data flow as either into a dataflow (LOADER) or output from the dataflow (STORE).
I am not aware of any QDC feature that can currently produce this inter-dataflow dependency (but I would be happy to be corrected!), so I built one - this was constructed in Python by creating a graph (DAG) where the Nodes and edges were derived directly from the QDC metadata database.
Possible uses for this information are:
- documenting process flows
- creating information for scheduling purposes
I have fully described the process in this github repository podium-dataflow-dependency-tree