PRE2018 3 Group10: Difference between revisions
No edit summary |
No edit summary |
||
Line 32: | Line 32: | ||
* Prototype | * Prototype | ||
* Presentation | * Presentation | ||
=Requirements= | |||
==Must Have== | |||
1. Must be able to move forward a certain defined distance. | |||
2. Must be able to turn 45 degrees in place. | |||
3. Must be able to discern between provided gray, white and black tiles underneath it. | |||
4. Must be able to discern the difference between each provided “command block” (forward; backward; turn clockwise; turn counterclockwise; loop2; loop3; loop4; loopend). | |||
5. Must be able to store each command of inputted “command blocks”. | |||
6. 3 blocks for every command block. | |||
7. Must be able to successively execute an entire chain of commands without user intervention. | |||
8. Must be safe to use according to <enter safety standard> | |||
==Should Have== | |||
9. 95% of children aged 9-12 can use the product within 30 minutes. | |||
10. The robot gives visual feedback when it is on a provided black tile. | |||
11. A manual details how to use the robot. | |||
==Could Have== | |||
12.The robot gives auditory feedback when it is on a provided gray tile. | |||
13. The robot discerns between provided red, green and blue tiles in addition to the tiles in requirement 3. | |||
14.There are different storylines with different goals. | |||
==Won't Have== | |||
15. The robot is able to execute a “fire” command. | |||
16. Hexagon shaped puzzle pieces. | |||
17. Loop blocks with variable numbers (switch or holes to put numbers in). | |||
18. The robot detects collisions with enemies on the board. | |||
19. All agents act at the same time based on a synchronized tick system. | |||
= State of the art = | = State of the art = |
Revision as of 16:54, 12 February 2019
Group members
Janneke van Oosterhout - 1248448
Wouter Wolthuis - 0942103
Timo Aerts - 0963375
Dorien Brugman – 1238166
Esther Dommisse – 0930091
Problem
Goal is to teach children in a fun way how to design software (concept of programming). E.g. sandwich robot is too basic and not-cool for older children but too hard to program for very young children. E.g. lego technique is too hard to program (or to boring with too few direct results) for children aged 9-12 although it looks really cool.
Problem Statement
Users
The users are children aged 9-12 and primary school teachers.
Approach
Objectives
- Create a design, to teach children programming
- Software
- Hardware
- Build a prototype
Deliverables
- The Wiki
- Prototype
- Presentation
Requirements
Must Have
1. Must be able to move forward a certain defined distance.
2. Must be able to turn 45 degrees in place.
3. Must be able to discern between provided gray, white and black tiles underneath it.
4. Must be able to discern the difference between each provided “command block” (forward; backward; turn clockwise; turn counterclockwise; loop2; loop3; loop4; loopend).
5. Must be able to store each command of inputted “command blocks”.
6. 3 blocks for every command block.
7. Must be able to successively execute an entire chain of commands without user intervention.
8. Must be safe to use according to <enter safety standard>
Should Have
9. 95% of children aged 9-12 can use the product within 30 minutes.
10. The robot gives visual feedback when it is on a provided black tile.
11. A manual details how to use the robot.
Could Have
12.The robot gives auditory feedback when it is on a provided gray tile.
13. The robot discerns between provided red, green and blue tiles in addition to the tiles in requirement 3.
14.There are different storylines with different goals.
Won't Have
15. The robot is able to execute a “fire” command.
16. Hexagon shaped puzzle pieces.
17. Loop blocks with variable numbers (switch or holes to put numbers in).
18. The robot detects collisions with enemies on the board.
19. All agents act at the same time based on a synchronized tick system.
State of the art
Memorization based on doing instead of learning
Programming at a young age
Interests of children aged 9-12
Sandwich-bot patent
Lego-technik patent
Planning
Who is doing what?
Hardware robot - Wouter
Instructie - Dorien
Software robot - Timo, Esther
Sensors software - Timo, Esther
Sensors - Wouter
Puzzelbord - Janneke
Design - Dorien, Janneke
User manual/scenarios - Dorien
Planning
Week | All | Janneke | Wouter | Timo | Dorien | Esther |
---|---|---|---|---|---|---|
1 | Set up requirements, Read and summarize at least 25 papers | Edit Wiki | Order electronics part 1, design electronics | Divide robot-software in separate modules. | Divide robot-software in separate modules. | |
2 | bare command blocks, Make and sensors MK1 | User manual MK1 | ||||
3 | Board idea finished | Make and sensors MK2 | Command blocks are read correctly, Light sensors read in optimal situations | User manual MK2, Design command blocks | Command blocks are read correctly, Light sensors read in optimal situations | |
4 | Make and sensors MK3 | User manual MK3 | ||||
5 | Board finished | Drive train | Light sensors are able to calculate spectrum and detect within those | Light sensors are able to calculate spectrum and detect within those | ||
6 | Design robot finished | Robot hardware and software testable and working | Robot hardware and software testable and working | Ideal user manual (with won't haves), Design robot finished | Robot hardware and software testable and working | |
7 | Prepare presentation | Test with kids if possible |