Show Advanced KnowledgeHide Advanced Knowledge

Saving students answers in tests with instant feedback

This feature is covered by the feature Optional History for saved Testinput.

1 Initial Problem

ILIAS tests with STACK-questions are commonly used for homework in mathematics and other technical subjects. In the homework-scenarios students often get instant feedback from the system and are thus allowed to try each question several times.

Currently, in tests with instant feedback, only the final (usually correct) answer of a student is saved by ILIAS and can be seen by the teacher.

In order to evaluate the difficulty of the questions, to improve the automatic feedback provided to the students, and to find out possible misunderstandings and pre-concepts, it would important that the teacher could see the students' wrong answers and how many tries per question each student had.

2 Conceptual Summary

In tests, where instant feedback is available, each time a student clicks “Check” (Prüfen/Rückmeldung anfordern) the student's answer should be saved in the database.
 
The page "Ergebnisse zu Einzelfragen / Results per question" of the test module should include a new column "Tries/Versuche". Here the teacher could download an Excel-sheet per question, including all answers of all students.
 
The answers can be presented in a single table with the following columns:

• Name of the student
• Username
• Running number, how many times the student has tried the question
• Total Points received for this answer
• Answer to answer field 1
• Answer to answer field 2
• Answer to answer field 3
• etc.

These statistics should be available for the following question types (in order of priority):

• STACK Question
• Formula Question
• Numeric Question
• Cloze Question
• Single Choice
• Multiple Choice
• ...

Consider for example the following test question:

The exported excel-sheet should include following information:

3 User Interface Modifications

3.1 List of Affected Views

• Test - Statistik - Ergebnisse zu Einzelfragen

3.2 User Interface Details

• Add a column "Versuche / Tries" and a link "Herunterladen/Download" per question.

3.3 New User Interface Concepts

...

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

• Author of the Request: Mikko Vasko, Hochschule Karlsruhe
• Maintainer: (will be set by Jour Fixe / maintainer)
• Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

• , Hochschule Karlsruhe

7 Discussion

8 Implementation

{please give a description of the final implementation and add screenshots if possible}

Test Cases

Test cases completed at {date} by {user}

• {Test case numberlinked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.