PRE2017 3 Groep9: Difference between revisions
Line 38: | Line 38: | ||
Documentation: Thomas and Casper | Documentation: Thomas and Casper | ||
Programming: Daniel and Kaj | Programming: Daniel and Kaj | ||
Mechanical knowledge: Wouter | Mechanical knowledge: Wouter | ||
=Coaching Questions= | =Coaching Questions= | ||
[[Coaching Questions Group 9]] | [[Coaching Questions Group 9]] |
Revision as of 10:56, 18 February 2018
Subject
During this project we will aim to create a concept/demo for an educational game, which will make use of both the concepts of game-based learning and physical learning.
Objectives
The objective of this project is to see whether we can create a new learning experience through game-based and physical learning in which robotics will play a role.
Users
The end users of this project will be students and educational institutes. The educational institutes can take inspiration from this project to try a similar method for teaching and the students are the ones that could be taught by it.
State of the Art
PRE2017 3 Groep9 - State of the Art
Approach
Our approach for this project will be to start with gathering information on currrently existing educational games and theory on physical learning. Based on this information we will formulate a general idea for a game. After that depending on how extensive the game will be we will either create an in depth overview of the game or a demo.
Planning
Because we do not yet have a concrete concept for the game that we will be working on, we cannot yet give a concrete planning for the later weeks.
Week 1: Planning and State of the art
Week 2: Searching further information
Week 3: Analyzing information and creating a general concept for the game.
Week 4-8: Creating the game.
Milestones
Similar to the planning because we do not yet have a concrete game in mind, the milestone will be very general:
- Game concept
- Game completed
Our deliverables are for now the same as these milestones.
Who will do what?
All of our skills are somewhat similar, therefore a lot of the tasks will overlap, however we can give an overview of what people will be the most involved in certain parts:
Documentation: Thomas and Casper
Programming: Daniel and Kaj
Mechanical knowledge: Wouter