documentation

docs/UML/mxgraph.puml

@@ -0,0 +1,54 @@
+@startuml mxgraph
+package MxGraph {
+
+    class MxGraphModel {
+        - XMLName xml.Name
+        + Root : RootStruct
+        + createLinks()
+    }
+
+    class RootStruct {
+        - XMLName xml.Name
+        - MxCell[] MxCell
+        - MxObject[] MxObject
+        - MxLink[] MxLink
+    }
+
+    class MxCell {
+        - XMLName xml.Name
+        + ID string
+        + RID *string
+        + Rtype string
+        + Parent *string
+        + Edge *string
+        + Source *string
+        + Target *string
+        + processLinks()
+    }
+
+    class MxLink {
+        + ID string
+        + Source string
+        + Target string
+    }
+
+    class MxObject {
+        - XMLName xml.Name
+        + ID string
+        + Settings []xml.Attr
+        + MxCell MxCell
+    }
+
+    class mxissue {
+        - msg string
+        + Error() string
+    }
+
+    MxGraphModel *-- RootStruct : Root
+    RootStruct *-- MxCell : MxCell
+    RootStruct *-- MxObject : MxObject
+    RootStruct *-- MxLink : MxLink
+    MxObject *-- MxCell : MxCell
+}
+
+@enduml

docs/UML/plantuml/diagram_object_routers.puml

@@ -0,0 +1,2 @@
+@startuml
+@enduml

docs/graph_construction.md

@@ -0,0 +1,5 @@
+For an easier parsing and constrution of dependencies we decided that :
+
+- Computing elements must be linked between one another, to represent the chaining of events
+- A storage component can be shared by several computing component, the direction of the arrow will determine if it's for writting or reading
+