New class link to handle links between components and possible errors

docs/identified_problems.md

@@ -2,11 +2,12 @@
 
 - [ ] In most of the components from 'models/' we have a method to add  input and output to the model, however this linking of components is already done in oc-schedule when parsing the MxGraph. We need to determine if adding relations between components inside the objects themself is necessary.
     - When running in debug mode with a breakpoint inside the first line of computing.addLink it is only called once
-- [ ]
+
 
 ## MxGraph
 
 - [ ] The ConsumeMxGraphModel is way too long, it should refactored and broken down in different sub methods
     - mxcell are put inside an <object> tag when the settings have been opened, wether values have been set or not. Maybe we could find a way to make mxgraph add these whenever we add a component to the graph.
     - then identify the links only 
-- [ ] It is unclear what are the inputs and the ouputs. It seems like they were implemented to link two components, but it seems redundant with the identification of links
+- [ ] It is unclear what are the inputs and the ouputs. It seems like they were implemented to link two components, but it seems redundant with the identification of links
+    - This has been potentially tackled with the creation of a class to handle links between components. The components do no handle their own connections with other components, this task is delegated to the Link and Worlflow classes.  

docs/linking_errors.md

@@ -0,0 +1,25 @@
+# Handling errors during workflows' post
+
+Every time an user modify a worflow through oc-search's GUI its representation is sent through an XML to oc-catalog API.
+
+To ensure a correct execution of the workflow we must look for irregularities in the workflow's design. Of course an error can be the result of a workflow being currently built by the user, with the corrective action coming.
+
+This document aims at laying down all the requirements that each component must respect and show wether they have been implemented in the code or not.
+
+## Computing
+
+- [x] A computing component must be paired with a datacenter component
+
+## Data
+
+- [x] A data component must be linked to at least one computing component
+
+## Datacenter
+
+- [x] A datacenter component must be linked to at least one computing component
+
+## Storage
+
+- [x] A storage component must have at least one target or be the source of another component 
+ 
+