|
|
|
@ -279,6 +279,21 @@ facts, it is clear that the new system has to be written from scratch. This
|
|
|
|
|
implies, that only subset of all features will be implemented in the first
|
|
|
|
|
version, the others following later.
|
|
|
|
|
|
|
|
|
|
Gathered features are categorized based on priorities for the whole system. The
|
|
|
|
|
highest priority has main functionality similar to current CodEx. It is a base
|
|
|
|
|
line to be useful in production environment, but a new design allows to easily
|
|
|
|
|
develop further. On top of that, most of ideas from faculty staff belongs to
|
|
|
|
|
second priority bucket, which will be implemented as part of the project. Most
|
|
|
|
|
advanced tasks from this category are advanced low-level evaluation
|
|
|
|
|
configuration format, using modern tools, connecting to a university systems and
|
|
|
|
|
merging separate system instances into single one. Other tasks are scheduled for
|
|
|
|
|
next releases after successful project defense. Namely, these are high-level
|
|
|
|
|
exercise evaluation configuration with user-friendly interface for common
|
|
|
|
|
exercise types, SIS integration (when some API will be available from their
|
|
|
|
|
side) and command-line submit tool. Plagiarism detection is not likely to be
|
|
|
|
|
part of any release in near future unless someone other makes the engine. The
|
|
|
|
|
detection problem is too hard to be solved as part of this project.
|
|
|
|
|
|
|
|
|
|
The new project is **ReCodEx -- ReCodEx Code Examiner**. The name should point
|
|
|
|
|
to CodEx, previous evaluation solution, but also reflect new approach to solve
|
|
|
|
|
issues. **Re** as part of the name means redesigned, rewritten, renewed or
|
|
|
|
|