The interface of the tool is divided into two separate parts, student part and teacher part. Although the structure of both parts is quite similar their separation was necessary due to the different access rights and security policy. While the teacher has to authenticate himself/herself at the instance of entering the teacher interface, the student has to provide his/her identification (required as a primary key for the access to the database). The teacher part contains list of courses, for each of them the list of homeworks, course related materials (course programme, notes, examination rules, etc.), and link to automatically generated course summary are available. The course summary collects all the results of homeworks and course tests for all students registered in the particular course. For each homework there exists its formulation (available in graphical representation) and solution query form (displaying homework results, depending on parameterisation). Similarly, the student section holds list of courses, each of them consists of course related data (common with teacher section), list of homeworks, and personal statistics and info (for displaying student parameters). Example of a typical layout of a course WWW page, in student section, is depicted in Figure 2. The personal statistics (Fig. 3) contains the results of all homework evaluations and course tests for a particular student. For each homework, its formulation (common with teacher part) and corresponding verification form are available.
The homework verification is based on results supplied by the student via the submission form that invokes a CGI script that automatically evaluates these results. The student is then informed about the correctness of both the whole homework and individual subresults. The homework evaluation output should contain more detailed information, mainly in the case of an unsuccessful attempt, which helps student to find his/her mistake more easily. Every successful (optionally also unsuccessful) student trial adds corresponding record into database. The number of trials is unlimited.