PRE2020 4 Group3
Group members
| Name | Student number |
|---|---|
| Eline Boom | 1465872 |
| Luuk van Dorst | 1469789 |
| Robin van de Hoef | 1479679 |
| Kyra Moviat | 1349171 |
| Jeroen Pullen | 1477730 |
| Veerle Uhl | 1462229 |
Introduction
With the rise of technology comes new ways to implement technology into our daily lives. One of these implementations is technology in education. More specifically, we wanted to develop a technological tool that will help young children in their learning process of number sense. Your knowledge of counting and quantities is tested daily throughout your life. Not a day goes by where you do not have to count or decide the quantity of something, which it is such an important skill to learn from an early age. We wanted to make an application that teaches children number sense in a fun and easy way.
Teaching children to count is very important. It helps with their development as well as being used in day-to-day life later on. The current curriculum used in most schools works well, but we feel that implementing technology into this curriculum would improve the learning of small children, both in school and at home. According to Hsin(Hsin, 2014), who studied the influence of children's use of technology on their learning, this technology does have a positive effect on learning. Hsin does provide us with a few conditions in which learning with technology is optimal. When children are allowed to work together and communicate with each other, technologies may not only improve knowledge, but social skills as well. These skills are most important for children, since interaction with others is needed for humans to survive. The second condition that needs to be met, is that adults need to be present to provide a safe climate and to encourage participation. This makes sure children stay motivated to learn and the adult can give guidance when instructions might be unclear. Our product is heavily influenced by these two conditions. What we designed is a web-based application that teaches children how to count and recognize shapes and color. It is targeted at children aged 3-5 that are at an average level of counting and shape / color recognition. It has a level-based design with three main levels. These levels then have several exercises each. The difficulty increases for each level, but stays the same within levels. OUr product is designed to be used in a classroom setting. It can be used on a whiteboard with a stylus or on a computer or laptop. When it is used on a whiteboard, children can interact and discuss with each other about the correct answer to the questions. This way, interaction and collaboration is promoted. When it is used in a classroom setting, the teacher can give extra help and information where needed, although the product is designed to need very little to none additional explanation. This wiki gives an overview of the research done for the project, the design behind the project as well as the website and its layout.
Source: Hsin, C. T., Li, M. C., & Tsai, C. C. (2014). The influence of young children's use of technology on their learning: A review. Journal of Educational Technology & Society, 17(4), 85-99.
USE
User
Society
Enterprise
Research
State Of The Art
There are already a lot of apps on the market that are geared towards educating children. Certainly apps that teach children how to count or how to draw separately. Combining the two is also done, but less frequently. One app and one website that combine learning to count and to draw are found on the internet. The first one is an app made by Bini Bambini and is called “123 tekenen tellen van nummers voor kinderen”. This game gives children very simple descriptions along with visual guides for drawing complex shapes. It then tells the child how many objects there are and lets the child draw the number. It does not have any AI to see what the user draws, it only gives an outline and a field in which to draw. Once the user stops drawing for a few seconds, the app goes on to the next step. The second one, a website, is called Kids Academy. This has the same general layout of the bambini app, only the Kids Academy focuses on more than just learning math. What stands out quite prominently in both apps is the design layout. It is clearly targeted towards kids with simple shapes, bright colors and audio directions instead of text. Our product keeps these general GUI attributes, but it is different in the level design. We combine drawing and counting in a different way. First, we start off with a level where children do not even need to draw and just need to recognize amounts, colors and shapes. Then, children need to draw (simple) shapes themselves, without guidelines, and also need to draw the correct amount eventually. This makes it so the child is more actively working on the amounts of objects, which will promote their learning.
How children learn
In order to develop an application that supports the learning of children aged 3-5, we first need to know how children's learning develops during their early years and what knowledge they already possess or still need to learn. From when they are born to around the age of 5, children develop “everyday mathematics”. These are informal ideas of more and less, taking away, shapes and sizes. These everyday mathematics can be surprisingly broad, complex and sophisticated. Apart from the everyday mathematics that children learn on their own, they also start learning mathematics in school. From the age of 2, children learn the language and grammar of counting. They memorize the first ten or so counting words, and then learn a set of rules to generate the higher numbers. When children are around 4 or 5 years old, they begin to develop metacognitive skills: They become increasingly aware of their own thinking and begin to express it in words. The hardest form of language for children to learn, which they thus only learn at a later date, is the special written symbolism of mathematics, like 5, +, - or =.
Understanding numbers involves more than saying a few counting words. It involves reasoning about numbers, making inferences and developing a mental number line. Children also need to mathematize: to conceive of problems in explicitly mathematical terms. They need to understand that the action of combining one bear with two others can be meaningfully interpreted in the terms of the mathematical principles of addition and the symbolism 1 + 2. This mathematizing is not very important for our product, as this only happens at a later age than the target group we are designing for. This means that we do not yet have to include problems of mathematization in our level design
The Number Worlds Curriculum
This curriculum is one of many out there that learns children what numbers are and how to use them. It provides a good understanding of the process a child goes to in order to learn how to count. Looking at 5-year-olds, there are several points of knowledge they need to know, relating to number sense. Five year olds know:
- that numbers indicate quantity and therefore, that numbers themselves have magnitude
- that the word “bigger” or “more” is sensible in this context
- that the numbers 7 and 9, like every other number from 1 to 10, occupy fixed positions in the counting sequence
- that 7 comes before 9 when you are counting up
- that numbers that come later in the sequence
- that are higher up - indicate larger quantities and therefore, that 9 is bigger (or more) than 7.
- that each counting number up in the sequence corresponds precisely to an increase of one unit in the size of a set. This enables children to use the counting numbers alone, without the need for real objects, to solve quantitative problems involving the joining of two sets. In doing so, it transforms mathematics from something that can only be done out there (e.g. by manipulating real objects) to something that can be done in their own heads, and under their own control.
As children get older, they progress through different knowledge they know: By the age of 4, children have constructed knowledge of counting and quantity. Sometime in kindergarten, children become able to integrate these knowledge networks. Around the age of 6-7, children connect this integrated knowledge network to the world of formal symbols. By the age of 8 or 9, most children become capable of expanding this knowledge network to deal with double-digit numbers and the base-ten system.
In the number worlds curriculum, there are 5 instructional principles that lie at the heart of the program:
1. Build upon children's current knowledge
2. Follow the natural developmental progression when selecting new knowledge to be taught
3. Teach computational fluency as well as conceptual understanding
4. Provide plenty of opportunity for hands-on exploration, problem-solving and communication
5. expose children to the major ways number is represented and talked about in developed societies
Lastly, the core of number sense forms a knowledge network that is called the central conceptual structure for number. This core is important for children for two reasons: 1) it enables children to make sense of quantitative problems across context, 2) it provides the foundation on which children's learning of more complex number concepts is built.
Stakeholders And SLO
Meetings with stakeholders were had in order to figure out what important topics they want to see included in the website design as well as other useful information they have on the learning trajectories of children. This resulted in the following information:
3-4 years old: Easy levels, can count to 10, can manage color comparison, learning pen grip important, learn to count via touch, “which object is blue”? appropriate question, combination of tasks as described in goal level still to hard.
4-5 yeas old: Goal level, know all colors, can count, learn shapes important, number recognition important.
*What makes the software good?
- Rising level of difficulty (3-4 to 4-5 level ?)
- Possible on digital school board
- Possible with pen (learn pen grip)
- Returns performance data to authorized figure
- Test mode
- Feels like a game (reward system)
*What can kids learn from the software?
- Colors, Shapes, Counting & Drawing
- Pen grip
- Vocabulary (if drawing objects)
- Listening skills (if tasks given in audio)
- Number recognition (number on screen)
*Useful purposes
- Being able to use the software collaboratively (class setting, performing tasks together)
- Being able to use the software to test how far children are.
- Being able to have the kid perform tasks on their own, behind computer or tablet.
SLO learning goals:
Colors: “Knows all colors”
Stakeholders
Shapes: “Be able to construct shapes”
https://www.slo.nl/thema/meer/jonge-kind/doelen-jonge-kind/
Counting goals: “Learn to count to 20, can recognize amounts up to 12”
https://www.slo.nl/thema/meer/jonge-kind/doelen-jonge-kind/
Drawing/Motor skills: “Learn pen grip”
Stakeholders
Vocabulary: “Understand instructions, learn new words”
https://www.slo.nl/sectoren/po/inhoudslijnen-po/inhoudslijnen-nederlands/
Number Recognition: “Know, read and write numbers”
https://www.slo.nl/sectoren/po/inhoudslijnen-po/inhoudslijnen-rekenen-wiskunde/
Listening skills: “Learn how to follow a task description”
https://lesintaal.nl/platform_taaldidactiek/1_mondelinge_taalvaardigheid/kennisbasis.htm
Digital skills: “Playfully get acquainted with technology and how to operate them, partially via educative games”
https://www.slo.nl/thema/meer/jonge-kind/doelen-jonge-kind/
How We Use The Research
As a basis, we will use Number worlds curriculum and SLO curriculum. These have been tested and used by many schools and education institutes around the world and are proven to support learning of children.
Number words has 5 principles for learning, we used them as a framework to develop good exercises that cater to the needs of the children that want to learn. Principle 1 talks about building upon children’s current knowledge. We do this by slowly incrementing the difficulty of our levels. First, we ask children to simply move an object into a box, then when they have mastered this, they need to move a specific amount or specific color or shape of object into a box. This way, we slowly add more variables while building onto the knowledge children already have. Principle 2 is about following the natural developmental progression when selecting new knowledge to be taught. With this, we looked at what knowledge young children typically learn at what age. We also took into account the desired age for users and combined this to find what lessons work best. For example, we use squares and circles for objects instead of cars and dogs, since the latter is too far ahead in the developmental progress of knowledge for the small children. Principle 4 talks about providing opportunity for hands- on exploration and communication. We hope to do this by making our product work as well on a digiboard. This way, children and teachers can work together to solve problems and do exercises, promoting communication between them.
The SLO curriculum is one that does not just focus on math, or on younger children. It focuses on all subjects and children of all ages. For our application, we look at their learning materials for young children (ages 4-7) and specifically the math and number sense material. SLO works with "inhoudslijnen" that give an overview of everything the young child (until age 7) needs to be able to do and what knowledge they need to posses. Even though our app focuses on children ages 3-5, we can still use these "inhoudslijnen" to shape our exercises. Learning never stops, and everything we teach children at a young age, they do not need to learn at a higher age still. If we for example look at some of the learning goals of SLO, we can see that, at age 7, they want children to learn how to count to 20 and to also be able to count quantities of at least 20. At age 4 or 5, children using our app probably would not already be able to have knowledge on all these topics, as they are aimed at children aged 7, but we can give them a good push in the right direction. Since we know that children aged 7 need to know at least how to count to 20, then children aged 5 should not only be able to count to 5, but probably to 10 already. In conclusion, using the learning goals of SLO, we can modify them to set our own learning goals for users of the application. Based on these learning goals, we can then shape the levels of the game to teach the children just what we want to know.
SLO has learning goals for children. The learning goals important for our level design are on the drive file. Here is a summary of important findings: What we have now is doable for children aged 3-5 years old. What we might need to test is that it will not be too easy for 5 year olds, seeing as according to SLO, at that age they already learn additional things as well. What we have now as exercises follows the learning lines of children and will support their learning process. Nothing from the levels is too difficult, so it wont be the case that the level difficulty is above the level of the users. Related to language (listening/reading): reading is indeed too difficult for younger children. When you look at phase 1 of OSL, you can see it is mostly simple words and very very short sentences as well as looking at pictures. There is not a whole lot about listening, but according to the prephase (for ages 2-4) then children should be able to listen to and interpret explanations of exercises. We do have to keep in mind to only use very simple words
Software Model
Our website combines learning of shapes and numbers into a fun experience for young children. It is targeted at children aged 3-5 that are starting to learn number sense and shape recognition. It is a web-based design that is intended for use in the classroom, on digiboards or school computers. It is designed to follow the natural learning curve of children and to promote communication between users.
The website itself is designed with the users in mind. Since the main users will be children aged 3-5, the website needs to be exciting and fun for them. This means the use of lots of bright colors and fun shapes or cartoons. The website also has little to no text, with instructions being given through audio. During the levels there is also a story element with small videos to keep the attention of the children. The buttons for the levels as well as those used for the drawing tool are all quite large. This makes it so even children that cannot move the mouse with a lot of accuracy can still click on the interactables with ease.
Level design
The levels are designed in a way to reflect the natural learning of children. There are 3 main levels, each with sub-levels that vary slightly. The first level is mostly about shapes. In this level, users will have to move the correct colored and shaped object into a square box. This will make users get used to the layout of the website as well as teach them about shapes and colors. The shapes will be quite simple, circles, squares and triangles will be used. When this first part is done, users will then get an instruction such as “move the 2 red triangles and 1 blue square into the box”. Here, shapes and colors are combined with a small amount of counting. Level 2 starts to get a bit more difficult. Here, users need to draw the shapes in the instructions. The kinds of shapes and colors are still the same as in level 1, but instead of moving them, they have to draw the shapes on their own. Level 3 then gets a bit more difficult still. Users now have to draw a specific amount of shapes, instead of just 1. This final level will integrate their knowledge learned throughout the earlier 2 levels.
Difficulty
In order to make sure the users will be engaged by the website as well as the website not being too difficult, an index of difficulty was added to the levels. The user will have to successfully move through all difficulties of a level before being able to move on to the next level. The amount of difficulty has influence on the range of colors and amount of shapes that are available in the exercise. The difficulty will go up or down depending on the user's success rate. This is an example of how a child can move trough the stages:
1.1 -> success // 1.2 -> success // 1.3 -> failed // 1.2 -> failed // 1.1 -> success // 1.2 -> success // 1.3 -> success // 1.4 -> failed // 1.3 -> success // 1.4 -> success //
After this, the child has completed level 1 and can move on to level 2.1. By implementing this difficulty factor which makes the user go back to a previous question, it will be sure that when the user moves on to the next level, they understand what is being asked and are likely able to finish the level.
Image Recognition
In order to recognize images drawn by children, a neural network was used. In order to train this network, a couple of useful databases that contain drawings and letters were used:
-MNIST dataset (http://yann.lecun.com/exdb/mnist/)
-Google quick draw dataset (https://github.com/googlecreativelab/quickdraw-dataset)
Some code was also created which can read a database, build a neural network, train a network and test the resulting network. However, at first the results from the neural network
were disappointing. At the start, the success rate of the neural network was 0.0036 which is worse than random guessing (which would be 1/250 = 0.004 with 250 labels). After a week, we decided to use a different dataset for the AI: the google draw dataset. The reason for the switch is because the google dataset has better support for simple shapes like squares and circles, which we will use for our final product. The downside of the google draw dataset is that it comes in 4 different formats, each of which has a different amount of preprocessing done to it, which made it hard to make an informed decision about it. One other downside to the different formats is that if we decided to switch to a different format, the part of the code that reads the input needed to be updated as well. In the end, we decided to look into the pros and cons of all four formats and decided on the 38x38 grayscale bitmap version of the original images. The reason for this choice is that the simple shapes will be easy to recognize even with this heavy downscaling and the low image resolution will result in shorter training times and a less complex neural network. This dataset we chose comes in a .npv format, which means that at the point of implementing it was incompatible with a lot of the code, which meant we had to update that.
After implementing the new dataset, the AI had a significantly improved accuracy. It is currently at 97%. In the end, the AI was implemented on the website. This took some trial and error as the AI and the website did not have the same format (javascript vs python) butit worked in the end by using the tensorflow module from python. Code was also written that converted the drawn images from the users into a good format for the AI, which is a grayscale 28x28 image.
Platform
Designing the website
The website which holds the final product was made using glitch. This platform was chosen as it allowed the whole group to work together at the same time on the code, while also immediately seeing feedback on what the code changes to the website. Below are the links to the website as well as the code for the website:
The website: https://group3use.glitch.me/
The code: https://glitch.com/edit/#!/group3use
Storyline throughout the levels
To make completing all the levels more appealing to children, a storyline will be shown through visuals in the levels and animated videos. This reward system is set up in the following manner. Before starting the drag and drop levels there is an introduction video that introduces the storyline and explains what the children need to do to complete the levels. After every completed level a small reward video plays that shows the children that they are doing something that impacts the storyline. After every few levels a somewhat larger video plays that updates the storyline a bit. If the children complete every drag and drop level a video plays that concludes that part of the storyline. The drawing levels have animated videos in the same places as the drag and drop videos. Testing our product in a classroom proved that the reward system was effective for at least the drag and drop levels.
The subject of helping animals was chosen for the storyline because it is observed to be a timeless subject for children. Things like tv-shows and apps geared towards children use animals very often. Testing our product also confirmed this.
The overarching storyline is about a group of animals (a horse Pleun, a monkey Albert, a bunny Kiki and a tiger Tim) that are going on a summer holiday. The group however, has trouble reaching their destination because of a few obstacles that the children can help them with. The levels designed for 3-4 year olds are about the start of the journey, where all the animals get hungry. In each level the children drag a specific shape with a certain color into a box. If they do it right the video shows the shape transforming in food and one of the animals eating it. The videos updating the storyline show the animals getting less hungry and more energetic. Finally, the concluding video shows the animals having a full stomach and continuing their journey.
During the levels designed for 4-5 year olds the group of animals has almost reached their destination, which is a small house on the beach. But to get there they still have to cross quite a few rivers without bridges, and the children can help them build those bridges. In the levels they draw certain shapes that transform into bridges in the reward videos afterwards. The last concluding video shows the animals standing on the beach next to their holiday home. They thank the children for their help and can finally start their holiday.
Animating the videos
All the videos needed for the reward system of the drag and drop levels have been animated and added to the site. As much of the animated videos for the drawing levels as possible were also added to the website, which sadly was not all the videos, since the drawing levels couldn’t be finished in time. PowerPoint was used to make the animations.
Test plan
In order to make sure our product works as intended, user tests were run on children aged 5-6. Since there was limited time available for the study and design of the product (only 8 weeks), there was no possibility to test whether the product actually supports and improves learning for children. What was able to be tested, however, was whether children engage with the product and whether the product can keep their attention. In order to test this, a test plan was written out:
In total, the experiment will take an hour. This is not an ideal timeframe, but the children are only available for 1 hour. At the start of the experiment, there will be 15 minutes where the experimenter will explain to the children what the study is going to be about. The hypothesis will not be disclosed, but the general plan of the study will be. Somewhere before the study will take place, the teacher(s) present will be given a more thorough explanation as well. We will tell them the research question we want to answer, as they cannot influence the opinion of the children during the study. During these first 15 minutes, the children will also be divided into groups. There will be 3 groups in total, all with an approximately even amount of children in them. An even distribution based on age or math level is not needed.
Then, we move on to the experiment. During this, each group will have 10 minutes in which they will play with the website on the digiboard. When the 10 minutes start, the website is started up and the intro video is played. The children will watch the introduction video and then start playing the levels in the correct order. Whenever there is a question, they are encouraged to search for an answer together before asking the teacher / experimenter for a solution or hints. After the 10 minutes is over, the group of children switches and the experiment gets repeated. This is done once for all groups, so a total of 3 times. When one group is busy with the experiment, the other two groups will (ideally) be in a different room working on other schoolwork (possibly also math?)
In the last 15 minutes, a group discussion will be held with all children present. Here, we can ask the opinions of children and possible ways for improvement. We can also ask about the comparison between our "fun" way of learning and the regular way of learning that they do in schools. Lastly, we want to know whether they liked the website or would change anything about it.
During the whole experiment, it is important to note down all the questions that children have and the points at which the children get stuck. These things will help us find ways in which to improve our website and make it easier to use. The experimenter must also pay close attention to whether the children find it too easy and get easily distracted, or find it too difficult and ask too many questions.
We do this experiment for a number of reasons. First of all, we want to know if our website is engaging enough for young children and if they like working with it. We believe that by adding small stories in between it grabs childrens attention and they want to help the animals in need. Secondly, we want to know if the levels are not too difficult. We based the level design on the natural learning process of children in schools. We think this will mean that the levels are proper support to the regular curriculum and will be neither too easy or too difficult. Lastly, we want to know if there are enough explanation videos on the website and if it is clear enough. This is a very important question, since if the website is too difficult to navigate, then children will not be able to use it without the help of a teacher or guardian.
We believe that with the current testplan, we will be able to answer all the questions named above and we will be able to optimally fine tune our website to match the needs of our target group best.
Project Plan
In order to efficiently work on this project, a project plan was made. First, important topics and an outline of our project was written down. After that, a general planning was made with a timeframe of when what part needed to be finished on the website. Lastly, these broad tasks were divided into subtasks and each task was assigned to a group member. In the end, the tasks had more overlap than what is displayed in the planning made at the beginning of the project, but all the deliverables were finished and handed in on time.
Subjects: Child psychology, learning, image processing, software development.
Objectives: Create software to help children learn
Users: Children (of parents that want to provide a playful learning app)
State-of-the art: Alternative apps that help children either count, draw or learn colors individually. Not in a combined way, we feel the combination might improve the way to learn these things. Additionally, we hypothesize that explaining problems via a childs own drawn elements could improve their understanding.
Approach: Make up a model for how the software should work, make software in which one can draw, program software that can recognize multiple drawn objects/shapes, implement everything in a working framework according to the model.
Milestones: Drawing software, working framework, Working object recognition, implementation in task framework
Deliverables: peer review, wiki, final presentation, the software, the website
Planning
| Task | Week 1 | Week 2 | Week 3 | Week 4 | Week 5 | Week 6 | Week 7 | Week 8 |
|---|---|---|---|---|---|---|---|---|
| 1. Brainstorm Project ideas | X | |||||||
| 2. Investigate Literature | X | X | ||||||
| 3. Create Software Model | X | X | ||||||
| 4. Create Software Framework | X | X | ||||||
| 5. Create Drawing Software | X | X | ||||||
| 6. Create Object Recognition Software | X | X | ||||||
| 7. Implement Recognition Software in Framework | X | X | ||||||
| 8. Work on Wiki | X | X | X | X | X | X | X | X |
| 9. Work on Presentation | X | X | X |
Subtasks
| subtask | Done / to do by who |
|---|---|
| 1.1 Find topics that are of interest and comply with technical skills of the group | Everyone |
| 2.1 Investigate state of the art | Kyra |
| 2.2 Investigate how children learn to count and learn colors and shapes | Veerle/Robin |
| 2.3 Investigate current models or curricula that are used for learning | Veerle |
| 2.4 Investigate the influence of online or "games" learning | Veerle/Robin |
| 3.1 Meet with stakeholders to see what they want to see in an excercise | Jeroen |
| 3.2 Figure out what kind of levels we want to make | Jeroen |
| 3.3 Implement levels in the website | Jeroen / Eline |
| 3.4 Make an instruction video for the levels | Kyra / Eline |
| 4.1 Set up a website | Eline |
| 4.2 Code and make a website layout, make it suitable for young children | Eline |
| 5.1 Set up a canvas where users can draw | Eline |
| 5.2 Find a way to use colors, a drawing tool and an eraser in the canvas | Eline |
| 6.1 Find databases to train a neural network with | Luuk |
| 6.2 Write code for a neural network | Luuk |
| 6.3 Write code that can read a database and train a neural network | Luuk |
| 6.4 Work on improving the accuracy of the neural network | Luuk |
| 7.1 Make the drawing made convert into a png | Eline |
| 7.2 Make the neural network compatible with a png | Luuk |
| 7.3 Convert the drawing png so it cuts out every individual shape and recognizes color | Robin |
| 8.1 Write down as much as we can on the wiki | Everyone |
| 8.2 Transform the summary on the wiki into a good text with logical structure | Veerle |
Time Log
Eline Boom
| Date | Description | Hours |
|---|---|---|
| 22/04/21 | Brainstorm meeting | 1 |
| 29/04/21 | Meeting | 1 |
| 29/04/21 | Setting up the website | 3 |
| 30/04/21 | Design of website | 2 |
| 03/05/21 | Meeting | 1 |
| 03/05/21 | Creating canvas function on website | 1 |
| 03/05/21 | Converting canvas to image | 2 |
| 03/05/21 | Colour pens and eraser | 3 |
| 06/05/21 | Colour pens and eraser | 2 |
| 06/05/21 | Switching between pen colours through button | 2 |
| 06/05/21 | switching between draw and erase through button | 4 |
| 10/05/21 | meeting | 1 |
| 13/05/21 | Researching possible ways to code Jeroen's game ideas | 2 |
| 13/05/21 | Coding different geometric figures in css | 0.5 |
| 14/05/21 | Start working on the actual game | 2 |
| 17/05/21 | Meeting | 1 |
| 17/05/21 | Difficulty level 3, randomization of figures | 3 |
| 19/05/21 | Finishing all level difficulties + reward when correct | 7 |
| 20/05/21 | working together with Kyra on animations | 8 |
| 25/05/21 | changing button text to images | 1 |
| 25/05/21 | adding audio files and play buttons | 3 |
| 25/05/21 | Overall layout | 1.5 |
| 26/05/21 | revisiting code for reward system | 4 |
| 27/05/21 | audio, creating levels, reward system | 8 |
| 31/05/21 | meeting | 1 |
| 02/06/21 | run-through whole website + fixing problems/ mistakes | 8 |
| 03/06/21 | animating videos + adding audio and video material to website | 6 |
| 09/06/21 | run-through whole website+ adding last animations | 1 |
| 10/06/21 | meeting on test results | 1 |
| 11/06/21 | implementing tips from the test on website | 1 |
| Total Hours: | 82 |
Luuk van Dorst
| Date | Description | Hours |
|---|---|---|
| 22/04/21 | Brainstorm meeting | 1 |
| 29/04/21 | Meeting | 0.5 |
| 29/04/21 | Searching for viable datasets | 2 |
| 30/04/21 | Researching neural networks | 3 |
| 02/05/21 | Making a prototype neural network | 4 |
| 03/05/21 | Meeting | 1 |
| 08/05/21 | install and get tenserflow working (took longer than expected) | 1 |
| 08/05/21 | Found some additional datasets | 1 |
| 08/05/21 | Finished neural network code | 4 |
| 09/05/21 | Did some research into how much nodes the neural network should have to increase performance | 2 |
| 09/05/21 | Tested some parameters to increase performance | 4 |
| 10/05/21 | edited wiki | 1 |
| 14/05/21 | Did a couple of tensorflow tutorials to understand the library better | 2 |
| 14/05/21 | Modified neural network to work with a different dataset | 3 |
| 15/05/21 | Adjusted parameters and tested the neural network to see if performance improved | 5 |
| 16/05/21 | Did some research to see how performance can be improved in the neural network | 4 |
| 21/05/21 | Fixed input problems in neural network training code | 3 |
| 22/05/21 | Tried fixing neural network model code | 3 |
| 23/05/21 | Tried fixing neural network model code again | 5 |
| 24/05/21 | Finally got the neural network model code working | 5 |
| 25/05/21 | messed with some parameters to increase accuracy of model | 2 |
| 25/05/21 | Edited the wiki | 1 |
| 27/05/21 | Worked on implementing the AI in the webpage with Eline and Kyra | 5 |
| 28/05/21 | Worked on implementing the AI in the webpage at home | 4 |
| 30/05/21 | Tried converting the current image recognition model to a .JSON file | 3 |
| 30/05/21 | edited the wiki | 1 |
| Total Hours: | 10.5 + 12 + 15 + 16 + 13 = 66.5 |
Kyra Moviat
| Date | Description | Hours |
|---|---|---|
| 22/04/21 | Research topics | 5 |
| 22/04/21 | Brainstorm meeting | 1 |
| 29/04/21 | Meeting | 0.5 |
| 02/05/21 | Add tables to wiki and update layout | 1.5 |
| 02/05/21 | Research state of the art | 1.5 |
| 03/05/21 | Meeting | 1 |
| 09/05/21 | Writing about state of the art | 1.5 |
| 09/05/21 | Updating wiki | 0.5 |
| 09/05/21 | Researching methods children learn counting | 2 |
| 10/05/21 | Meeting | 1 |
| 11/05/21 | Updating the wiki to only have 1 logging system instead of 2 | 0.5 |
| 11/05/21 | Working on script videos that will accompany the levels | 2 |
| 11/05/21 | Thinking of ideas for name of the app | 0.5 |
| 12/05/21 | Working on script and asking for feedback on it | 1 |
| 12/05/21 | Updating wiki | 1 |
| 17/05/21 | Meeting | 1 |
| 20/05/21 | Working together with Eline, animating videos to fit the levels | 8 |
| 20/05/21 | Updating wiki | 1 |
| 22/05/21 | Animating introduction video drag and drop levels | 8 |
| 26/05/21 | Meeting and processing minutes | 1.5 |
| 27/05/21 | Working together with Eline and Luuk, animating videos | 8 |
| 28/05/21 | Animating reward videos | 7 |
| 29/05/21 | Animating reward videos | 5 |
| 31/05/21 | Meeting | 1 |
| 02/06/21 | win video sleeplevels animating and making planning for videos | 6 |
| 03/06/21 | Introductionvideo drawinglevels animeren | 8 |
| 07/06/21 | Meeting | 1 |
| 08/06/21 | rewardvideos tekenlevels animeren en inroductievideo af | 8 |
| 10/06/21 | Demo product voor presentatie opnemen, inspreken en editen | 7 |
| 11/06/21 | demo editen | 6 |
| 14/06/21 | Eindpresentatie geven en bijwonen | 3 |
| 15/06/21 | laatste winvideo animeren | 4 |
| 15/06/21 | meeting for peer review | 1 |
| 15/06/21 | editing wiki | 2 |
| Total Hours: | 107 |
Robin van de Hoef
| Date | Description | Hours |
|---|---|---|
| 22/04/21 | Brainstorm meeting | 1 |
| 29/04/21 | Meeting | 0.5 |
| 03/05/21 | Meeting | 1 |
| 07/05/21 | Searching for suitable literature | 2 |
| 09/05/21 | Searching for and researching literature | 4 |
| 10/05/21 | Meeting | 1 |
| 14/05/21 | Installing and testing python image libraries | 1 |
| 15/05/21 | Color recognition | 2 |
| 16/05/21 | Image separation | 4 |
| 17/05/21 | Meeting | 1 |
| 17/05/21 | Increasing code performance | 2 |
| 21/05/21 | Testing code with front-end output | 3 |
| 22/05/21 | Debugging | 4 |
| 23/05/21 | Rewriting and optimizing code | 3 |
| 24/05/21 | Trying to fix black pixel issue | 4 |
| 11 | . | |
| Total Hours: | 33.5 |
Jeroen Pullen
| Date | Description | Hours |
|---|---|---|
| 21/04/21 | Research project ideas | 1 |
| 22/04/21 | Brainstorm meeting | 1 |
| 26/04/21 | Prepare poject planning | 1 |
| 27/04/21 | Research state of the art | 1 |
| 28/04/21 | Updating Wiki | 1 |
| 29/04/21 | Contacting stakeholders | 1 |
| 29/04/21 | Meeting | 0.5 |
| 29/04/21 | Preparing stakeholder questions | 1 |
| 30/04/21 | Interview first stakeholder | 1.5 |
| 03/05/21 | Meeting | 1 |
| 03/05/21 | Prepare second stakeholder meeting | 1 |
| 03/05/21 | Interview second stakeholder | 1.5 |
| 04/05/21 | Work out model using interview data | 2 |
| 05/05/21 | Work out model by researching learning paths | 3 |
| 05/05/21 | Work on Wiki | 1 |
| 08/05/21 | Work on Wiki | 1 |
| 09/05/21 | Work out complete model based on combined information | 2 |
| 10/05/21 | Meeting | 1 |
| 11/05/21 | Create Level Generator | 3 |
| 12/05/21 | Create Level Generator | 2 |
| 13/05/21 | Create Level Generator | 3 |
| 16/05/21 | Discuss Level Design with new stakeholder | 1 |
| 16/05/21 | Redefine level design according to advice & SLO | 2 |
| 17/05/21 | Finalize Level Generator according to redefined levels | 3 |
| 19/05/21 | Watch HTML tutorials | 2 |
| 20/05/21 | Watch Python to HTML tutorials | 2 |
| 22/05/21 | Turn Python Level Generator into Javascript | 2 |
| 22/05/21 | Update wiki on level design | 1 |
| 24/05/21 | Finish Level 1 & 2 in Javascript | 3 |
| 25/05/21 | Finish Level 3 in Javascript | 1 |
| 26/05/21 | Meeting | 1 |
| 26/05/21 | Contact with stakeholder for possible testing | 1 |
| 27/05/21 | Implement Javascript levels in website | 3 |
| 29/05/21 | Contact with Stakeholder for test | 1 |
| 31/05/21 | Meeting | 1 |
| 01/06/21 | Implement Shape Randomizer in website | 4 |
| 02/06/21 | Final planning with stakeholder for test | 1 |
| 03/06/21 | Work on figure randomizer | 2 |
| 05/06/21 | Finalize figure randomizer | 1 |
| 07/06/21 | Meeting | 1 |
| 07/06/21 | Work on drawing canvas | 2 |
| 08/06/21 | Work on drawing cavnas | 3 |
| 10/06/21 | Testing at school 'de Doelakkers' | 8 |
| 10/06/21 | Meeting | 1 |
| 11/06/21 | Review and summarize test material | 2 |
| 12/06/21 | Work on script video | 2 |
| 12/06/21 | Recorded and edited video test part | 2 |
| 13/06 21 | Finalized editing video | 1 |
| 14/06/21 | Final Presentations | 2 |
| 15/06/21 | Meeting | 1 |
| Total Hours: | 87.5 |
Veerle Uhl
| Date | Description | Hours |
|---|---|---|
| 22/04/21 | Brainstorm meeting | 1 |
| 29/04/21 | Meeting | 1 |
| 29/04/21 | Literary research | 1.5 |
| 30/04/21 | Literary research | 2 |
| 03/05/21 | Meeting | 1 |
| 03/05/21 | Literary research on how children learn | 3 |
| 09/05/21 | Literary research on the Number World model | 3 |
| 09/05/21 | Work on wiki, update the research and timetables | 2 |
| 10/05/21 | Meeting | 1 |
| 10/05/21 | Write a more detailed planning on the wiki | 1 |
| 12/05/21 | Write something about the use of research | 3 |
| 16/05/21 | Write something about our use of OSL and number worlds | 3 |
| 17/05/21 | Meeting | 1 |
| 17/05/21 | Looking into "inhoudslijnen" of OSL and level design | 3 |
| 19/05/21 | Editing wiki texts | 5 |
| 19/05/21 | writing wiki texts: level and website design | 3 |
| 24/05/21 | Editing wiki texts | 2 |
| 27/05/21 | reading through website code / work done by others | 1 |
| 27/05/21 | Begin work on project plan | 3 |
| 27/05/21 | work out testplan | 3 |
| 31/05/21 | meeting | 1 |
| 31/05/21 | Editing and changing testplan | 2 |
| 2/06/21 | testplan, editing wiki | 3 |
| 04/06/21 | finalizing test plan | 1,5 |
| 07/06/21 | meeting | 1 |
| 08/06/21 | work on the presentation | 5 |
| 10/06/21 | discussing user test, recording presentation and editing text | 3 |
| 13/06/21 | Editing video | 3 |
| 14/06/21 | Video presentation meeting | 3 |
| 15/06/21 | meeting | 1 |
| 16/06/21 | Work on wiki texts | 4 |
| Total Hours: | 70 |