basic description of whole process

Submissions-flow.md

@@ -5,6 +5,8 @@ It's assumed that readers understand [[Architecture]], [[Terminology]], [[Commun
 
 ## Web Application
 
+First thing user has to submit his/her solution to web application. Generally web application has to store submitted files and hand over all needed information about submission to broker. More detailed description follows:
+
 - user submits his solution to web application
 - T
 - O
@@ -17,6 +19,8 @@ It's assumed that readers understand [[Architecture]], [[Terminology]], [[Commun
 
 ## Broker
 
+Broker gets information about new submission from web application. At this point broker has to find suitable worker for execution of this particular submission. When worker is found and is jobless, then broker send detailed submission to worker to evaluation. More detailed description follows:
+
 - T
 - O
 - D
@@ -27,6 +31,20 @@ It's assumed that readers understand [[Architecture]], [[Terminology]], [[Commun
 
 ## Worker
 
+Worker gets request from broker to evaluate particular submission. Next step is to evaluate given submission and results upload to fileserver. After this worker only send broker that submission was evaluated. More detailed description follows:
+
+- T
+- O
+- D
+- O
+- .
+- .
+- .
+
+## Broker
+
+Broker gets done message from worker and basically only mark submission as done in its internal structures. No messages are send to web application, because of lazy evaluation on frontend side. More detailed description follows:
+
 - T
 - O
 - D
@@ -37,6 +55,8 @@ It's assumed that readers understand [[Architecture]], [[Terminology]], [[Commun
 
 ## Web Application
 
+Only remaining part is evaluation of results. This is provided on demand when user wants them. Results are obtained from fileserver and evaluated. More detailed description follows:
+
 - evaluation of execution results is provided on user demand
 - T
 - O