|
|
|
@ -120,12 +120,12 @@ they are willing to consult ideas or problems during development with us.
|
|
|
|
|
|
|
|
|
|
## Current system
|
|
|
|
|
|
|
|
|
|
Currently used grading solution at the Faculty of Mathematics and Physics of
|
|
|
|
|
the Charles University in Prague which was implemented in 2006 by a group
|
|
|
|
|
of students. It is called [CodEx -- The Code Examiner](http://codex.ms.mff.cuni.cz/project/)
|
|
|
|
|
and it has been used with some improvements since then. The original plan was
|
|
|
|
|
to use the system only for basic programming courses, but there was a demand
|
|
|
|
|
for adapting it for many different subjects.
|
|
|
|
|
The grading solution currently used at the Faculty of Mathematics and Physics of
|
|
|
|
|
the Charles University in Prague was implemented in 2006 by a group of students.
|
|
|
|
|
It is called [CodEx -- The Code Examiner](http://codex.ms.mff.cuni.cz/project/)
|
|
|
|
|
and it has been used with some improvements since then. The original plan was to
|
|
|
|
|
use the system only for basic programming courses, but there was a demand for
|
|
|
|
|
adapting it for many different subjects.
|
|
|
|
|
|
|
|
|
|
CodEx is based on dynamic analysis. It features a web-based interface, where
|
|
|
|
|
supervisors can assign exercises to their students and the students have a time
|
|
|
|
@ -182,7 +182,7 @@ happen during evaluation process.
|
|
|
|
|
|
|
|
|
|
First thing users have to do is to submit their solutions through web user
|
|
|
|
|
interface. The system checks assignment invariants (deadlines, count of
|
|
|
|
|
submissions, ...) and stores submitted file. The runtime environment is
|
|
|
|
|
submissions, ...) and stores the submitted file. The runtime environment is
|
|
|
|
|
automatically detected based on input file and a suitable evaluation
|
|
|
|
|
configuration variant is chosen (one exercise can have multiple variants, for
|
|
|
|
|
example C and Java languages). This exercise configuration is then used for
|
|
|
|
@ -277,9 +277,8 @@ addons (mostly administrative features).
|
|
|
|
|
- _customizable grading system_ -- teachers need to specify the way of
|
|
|
|
|
computation of the final score, which will be awarded to the student's
|
|
|
|
|
submissions depending on their quality
|
|
|
|
|
- _viewing student details_ -- teachers should be able to view detailed data
|
|
|
|
|
about their students (members of their groups), including all submitted
|
|
|
|
|
solutions;
|
|
|
|
|
- _viewing student details_ -- teachers should be able to view the details of
|
|
|
|
|
their students (members of their groups), including all submitted solutions
|
|
|
|
|
- _awarding additional points_ -- adding (or subtracting) points from the final
|
|
|
|
|
score of a submission by a supervisor must be supported
|
|
|
|
|
- _marking a solution as accepted_ -- the system should allow marking one
|
|
|
|
@ -931,10 +930,10 @@ protocol between these two logical parts will be described as well.
|
|
|
|
|
## Implementation analysis
|
|
|
|
|
|
|
|
|
|
When developing a project like ReCodEx there has to be some discussion over
|
|
|
|
|
implementation details and how to solve some particular problems properly.
|
|
|
|
|
This discussion is a never ending story which is done through the whole
|
|
|
|
|
development process. Some of the most important implementation problems or
|
|
|
|
|
interesting observations will be discussed in this chapter.
|
|
|
|
|
implementation details and how to solve some particular problems properly. This
|
|
|
|
|
discussion is a never ending story which goes on through the whole development
|
|
|
|
|
process. Some of the most important implementation problems or interesting
|
|
|
|
|
observations will be discussed in this chapter.
|
|
|
|
|
|
|
|
|
|
### General communication
|
|
|
|
|
|
|
|
|
|