Proj-2013-2014-SeriousGame-Parole-et-Geste

Introduction

Development of small 2D games to help children with language disorder. A second objective is the recovery of the game data to determine the progression and the troubles experienced by children. In this way, we can understand their cognitive abilities and find better ways to help them.

Team

• Tutors : Olivier Richard, Marion Dohen, Estelle Gillet-Perret, Amelie Rochet-Capellan

• Members : Mehdi NAIT-SIDOUS, Pierre-Henri GINOUX

• Departement : RICM 4, Polytech Grenoble

Links

• Kivy
• Blog on architectural patterns in game code
• Image resources
• Wiki with a lot of links on serious game

Project objectives

Le but du projet est de développer une application comprenant des mini jeux qui permettent d'évaluer scientifiquement si la gestualité manuelle peut aider des enfants présentant des troubles communicatifs à mieux apprendre de nouveaux mots. Une fois cette phase effectuée, il s'agira ensuite de finaliser afin de proposer un outil facilement utilisable à un maximum d'utilisateurs implémentant une méthode d'apprentissage de nouveaux mots en utilisant la gestualité manuelle.

Il faut garder à l'esprit que le jeu n'est qu'une composante du logiciel, nous allons donc dans un premier temps implémenter un jeu simple mais qui permettra de tester toute les composantes de l'application.

Objectifs pour le premier prototype de jeu : A REMPLIR

Objectifs pour l'application :

• Système de login pour identifier l'utilisateur de manière unique
• Facilité d'ajouter un nouveau jeu dans l'application
• Stockage des résultats en local
• Possiblité d'envoyer les résultats sur un serveur Web
• Possibilité de modifier la configuration pour chaque jeu (changer la difficulté, les images utilisées...)

http://air.imag.fr/index.php/SRS_SeriousGame_RICM_Group

Progress of the project

The project started January 14th, 2013.

Week 1 (January 13th - Janurary 19th)

• Project discovery
• Learning of Python
• Research on Kivy
• Research on serious gaming

Week 2 (January 20th - Janurary 26th)

• Defining functional specifications
• Defining the problems we may/will have to sort out, like being able to store data using a user password. More details (in French)
• Learning how SQLite works and can be use to store game data

Week 3 (January 27th - February 2th)

• Reflexion about the class structure of the application
• Find a way to create dynamically the database
• Reflexion about the storage of settings

Week 4 (February 3th - February 9th)

• Meeting with Marion Dohen and Amelie Rochet-Capellan
• Reflexions about the specifications
• Split the job in different steps (cf. documentation)

Week 5 (February 10th - February 16th)

• First UML diagrams
• Begin of the first game prototype development
• Complete the online documentation

Week 6 (February 17th - February 23th)

• Include the SQlite Data Base in the application
• game prototype development
• Complete the online documentation

Week 7 (February 24th - March 2nd)

• UML Diagrams
• Game prototype development
• Complete the online documentation

Week 8 (March 3th - March 9th)

• End of the UML documentation
• Game prototype development (drag picture OK, sound OK)
• Complete the online documentation

Week 9 (March 10th - March 16th)

• Manage collide between widgets
• Display score and time and store it in data base
• Create two different class, Object and Category

Week 10 (March 17th - March 23th)

• Add an end game Menu
• Create an "interesting" GamePlay

Week 11 (March 17th - March 23th)

• Correct bugs on prototype
• Enable video add
• Complete the online documentation

Week 12 (March 24th - March 30th)

• Correct lasts bugs on prototype

Week 12 (March 31th - March 11th)

• Game3 development
• Enable CSV export of data stored in the data base
• Objects are now loaded from a txt file thanks to a parser
• 3 items are randomly chosen and displayed on the left
• 2 forms are randomly chosen and displayed on the right+1 corresponding to an object on the left
• Correct and Wrong answers are stored in the data base and can be export in CSV
• Objects are displayed dynamically