Question Pool (Test)-related Quiz-Game Quiz & Conquer

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ.

1 Initial Problem

Actually its not a problem, but an idea. The following new feature is designed to improve learners motivation for doing preparation tests by the approach of gamification. I'm affraid, I'm no programmer, so some details might be missing or confusing. I'm sorry if this isn't the right place for such a feature request. Just gimme feedback and if necessary, I withdraw it. 

2 Conceptual Summary

“Quiz & Conquer”
Improve learner motivation with question pool (test)-related quiz-game
 
Idea:
We created the Idea of a Quiz-Game that is connected to a question pool (test).  Our goal is to improve students motivation for answering  exam questions in preparation. In this gamification based approach teams of students are in competition for answering questions to win the game. As they do, they prepare the necessary knowledge for their exam.
 
The goal of the game:
The board is divided in several fields. Each field is randomly connected with a question from a question pool (test).  There are at least two teams of students. The goal is to conquer as many fields as possible for your team by answering questions correctly. Winner of the game is the team that conquered the most fields until a determined deadline.
 
Course of play:
All members of a course are (automatically) divided in at least two groups (i. e. blue and red).
At the beginning of the game every field on the board is free (value = 0).
When the game is started every course member can klick on a field to get a question.
 
If the question is answered
- correctly, its +1 point for the team and the field gets the color of the team (i. e. blue)
- wrong, its -2 points for the team
There is a maximum of 10 points for each field and team.
Negative points on a field (i. e. fields value is 1, wrong answer gets -2) are not allowed. The field’s minimum is 0 and with this value it gets free (gray) again.
 
But you can also weaken and steal fields from the other team by clicking on a field that is controlled by an opponent. When the upcoming question is
- correct, its -1
- wrong, its +2 for your opponent’s field

3 User Interface Modifications

3.1 List of Affected Views

Several new screens would be necessary: 

Main Screen

Main Screen Mobile

Start Screen

Main Settings

Team Settings

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.}

Still to come...

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.}

Still to come...

4 Technical Information

- Connection to a question pool (test)
- Fields are randomly linked with questions
- Questions must be available repetitive
 
- Course admin can create teams [optionally with a maximum of members like in a group]
- Course members choose their team after entering the game
[- or are allocated automatically to a team (Connection to course member list needed)]
- List of team members afterwards
 
- Availability to determine the duration of the game
 
- Database for current field points
- Display of current points on every field
- Button to refresh field points
 
- Message after each answer, if it was right or wrong
 
- Mobile skin should be available
 
- Help section for rules and gameplay

5 Contact

• Author of the Request: [florian.tettenhammer]
• 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

What do you think? Is this idea worth the ressources?

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}.