general concepts

Rewritten-docs.md

@@ -390,12 +390,21 @@ like "memory limit exceeded") and amount of awarded points.
 ### Solution concepts analysis
 
 @todo: what problems were solved on abstract and high levels, how they can be solved and what was the final solution
-        - which problems are they?
 
-#### Structure of the project
+  - which problems are they? ... these ones ↓
+  - what type of users there should be, why they are needed
+  - explain why there is exercise and assignment division, what means what and how they are used
+  - explain instances why they are usefull what they solve and also discuss licences concept
+  - groups, they can be public and private and why is that, what it solves, explain amd discuss treshold and other group features
+  - extended execution pipeline (not just compilation/execution/evaluation) and why it is needed
+  - progress state, how it can be done and displayed to user, why random messages
+  - how to display generally all outputs of executed programs to user (supervisor, student), what students can or cannot see and why
+  - judges, discuss what they possibly can do and what it can be used for (returning for instance 2 numbers instead of 1 and why we return just one)
+  - discuss points assigned to solution, why are there bonus points, explain minimal point threshold
+  - discuss several ways how points can be assigned to solution, propose basic systems but also general systems which can use outputs from judges or other executed programs, there is need for variables or other concept, explain why
+  - and many many more general concepts which can be discussed and solved... please append more of them if something comes to your mind... thanks
 
-@todo: move "General backend implementation" here
+#### Structure of the project
-@todo: move "General frontend implementation" here
 
 The ReCodEx project is divided into two logical parts – the *Backend*
 and the *Frontend* – which interact which each other and which cover the
@@ -455,6 +464,9 @@ Frontend parts will be introduced separately and covered in more detail.
 The communication protocol between these two logical parts will be
 described as well.
 
+@todo: move "General backend implementation" here
+@todo: move "General frontend implementation" here
+
 #### Evaluation unit executed on backend
 
 @todo: describe possibilities of "piece of work" which can backend execute, how they can look like, describe our job and its tasks
@@ -569,7 +581,7 @@ As described in fileserver section stored supplementary files have special filen
 
 @todo: why are there instances and for which they can be used for, describe licences and its implementation
 
-@todo: groups and hierarchy, describe arbitrary nesting which should be possible within instance
+@todo: groups and hierarchy, describe arbitrary nesting which should be possible within instance and how it is implemented and how it could be implemented
 
 @todo: where is stored which workers can be used by supervisors and which runtimes are available, describe possibilities and why is not implemented automatic solution