Use Question Groups for Competence Estimations / Measurements

This is a sub-entry of the feature request Introduction of Question Groups

1 Initial Problem

{Please give a brief description of the problem you want to be solved.}

2 Conceptual Summary

• combine a set of questions to "question groups" which acts as a carrier of a competence set. The result of all the questions that are included in the set could then be taken as a means of competence assessment. With groups of questions, it will be possible to assess the degree or level of a learner with respect to a comptence much better that it is possible now. The handling of the comptence assignment logic will be made more flexible if done at questions group level.

• questions groups have their own "internal" result
• learners can pass or fail a question group when they reach / miss a certain score or percentage
• the score depends on the results of the included questions
• the group acts within a test like a single question
• the result of a question group can assume several states:
  • not started
  • started: in order to jump back in
  • passed: determined by reaching a percentage of max possible score of all question in the question group combined
  • failed: determined by failing a percentage of max possible score  of all question in the question group combined
• the learner does not get feedback on their state / result (this is what test parts should be for) before the test if finished
• question block is marked visually on the result presentation screens
• support question groups in item statistics, i.e. give an evaluation of the collected item data for the entire question group

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

3.2 User Interface Details

{For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour.}

3.3 New User Interface Concepts

{If the proposal introduces any completely new user interface elements, please provide a link to separate feature wiki entries for each of them according to the kitchen sink template.}

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: {Please add your name.}
• Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
• 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.

• …

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

• {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.