From 4c13417213b3cc8fd7baa8d35def186527cf970b Mon Sep 17 00:00:00 2001
From: Martin Stiemerling <martin.stiemerling@h-da.de>
Date: Wed, 16 Sep 2020 16:13:18 +0000
Subject: [PATCH] Update 05-implementation.md

---
 documentation/design/05-implementation.md | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/documentation/design/05-implementation.md b/documentation/design/05-implementation.md
index f09887c25..1dc36874a 100644
--- a/documentation/design/05-implementation.md
+++ b/documentation/design/05-implementation.md
@@ -45,6 +45,25 @@ databases should be used to store the different topology graphs and their
 pontential dependencies? How should the interface between gosdn and this
 database look like?
 
+Here is an attempt to describe the above text in a graphical reprensetation:
+
+```mermaid
+graph TB
+
+  SubGraph1 --> SubGraph1Flow
+  subgraph "SubGraph 1 Flow"
+  SubGraph1Flow(SubNode 1)
+  SubGraph1Flow -- Choice1 --> DoChoice1
+  SubGraph1Flow -- Choice2 --> DoChoice2
+  end
+
+  subgraph "Main Graph"
+  Node1[Node 1] --> Node2[Node 2]
+  Node2 --> SubGraph1[Jump to SubGraph1]
+  SubGraph1 --> FinalThing[Final Thing]
+end
+```
+
 ### Potential other Inventories
 
 There may be the potential need to store information beyond pure topologies,
-- 
GitLab