SlideShare a Scribd company logo
1 of 1
project review

In this kodu project we were asked to design and visual programing tool. We had options like to
designing a cycle with a computer code. In this project we learn to develop the skill of problem
solving. We had a design cycle which told us what to do and at what stage we were on, it also
told us how much was left to complete this.

The first thing i did was to do a plan of my game. This plan consisted in how I was going to do
my game and the design of the land. I had very clear how i wanted to do the land. The game
was firstly a racing game but then I realised that it was too complicated so I did a adventure
game. There was different types of characters and objects. For example there was cycles and a
rover for character and for objects you could selects balls, coins and more.

The final game was very interesting, i changed a lot of this from the first planning it stared as if it
was going to be a racing game but it ended of a game that you need to bring the balls to the
glowing point and then destroy the big ball. I think that the design cycle was very useful because
i didn't know how to start my game. In some parts i didn't know what to do or at what stage I
was.I had technical problems. Firstly my computer didn't work and then kodu stopped working
for one week so I had to do other things that wasn't relationated with my game. I wanted to do a
more complicated game but kodu didn't have what I wanted so I couldn't do it and that changed
all my plans of the game. Or i did have the things I wanted but in a different way and i couldn't
figure out how to win the game or how to get my cycle to eat the apple. I had enough time to
finish my land and the design but not to get the game work properly.

This project develop not the way i wanted but I knew how to arrange it without having to start it
again. I would do do better the land of my game, maybe do more holes and more uneven land
to make the travelling of the ball more difficult. I could make more enemies so that I makes the
game more difficult. The controls were easy just that sometimes the game froze and it didnt let
me work properly. More testing would make easier the game because there we could know
what we needed to change and what we needed to get better at. with this visual programing we
are preparing for a more difficult program and so that we don't get lost so easy..

More Related Content

What's hot

7. evaluation
7. evaluation 7. evaluation
7. evaluation KaiTodd
 
6. production reflection (interactive)
6. production reflection (interactive)6. production reflection (interactive)
6. production reflection (interactive)LouisDoddsRodgers
 
4. pre production(1)
4. pre production(1)4. pre production(1)
4. pre production(1)AllanGodin
 
7. evaluation(2)
7. evaluation(2)7. evaluation(2)
7. evaluation(2)AllanGodin
 
The design cycle
The design cycleThe design cycle
The design cyclegqalo
 
6. production reflection
6. production reflection6. production reflection
6. production reflectionjoe manship
 

What's hot (9)

7. evaluation
7. evaluation 7. evaluation
7. evaluation
 
6. production reflection (interactive)
6. production reflection (interactive)6. production reflection (interactive)
6. production reflection (interactive)
 
4. pre production(1)
4. pre production(1)4. pre production(1)
4. pre production(1)
 
7. evaluation (3)
7. evaluation (3)7. evaluation (3)
7. evaluation (3)
 
5. proposal
5. proposal5. proposal
5. proposal
 
B
BB
B
 
7. evaluation(2)
7. evaluation(2)7. evaluation(2)
7. evaluation(2)
 
The design cycle
The design cycleThe design cycle
The design cycle
 
6. production reflection
6. production reflection6. production reflection
6. production reflection
 

Similar to review

Similar to review (20)

Project Review
Project ReviewProject Review
Project Review
 
Evaluation
 Evaluation Evaluation
Evaluation
 
8. Evaluation
8. Evaluation8. Evaluation
8. Evaluation
 
7. evaluation done
7. evaluation   done7. evaluation   done
7. evaluation done
 
Evaluation of fmp
Evaluation of fmpEvaluation of fmp
Evaluation of fmp
 
Evaluation of fmp
Evaluation of fmpEvaluation of fmp
Evaluation of fmp
 
Evaluation of fmp
Evaluation of fmpEvaluation of fmp
Evaluation of fmp
 
Evaluation of fmp
Evaluation of fmpEvaluation of fmp
Evaluation of fmp
 
Evaluation of fmp
Evaluation of fmpEvaluation of fmp
Evaluation of fmp
 
Evaluation
 Evaluation Evaluation
Evaluation
 
8. evaluation
8. evaluation8. evaluation
8. evaluation
 
Blog powerpoint
Blog powerpointBlog powerpoint
Blog powerpoint
 
Unit 4 Game Evaluation
Unit 4 Game EvaluationUnit 4 Game Evaluation
Unit 4 Game Evaluation
 
Jump Step Hop Game Evaluation
Jump Step Hop Game EvaluationJump Step Hop Game Evaluation
Jump Step Hop Game Evaluation
 
7. evaluation
7. evaluation7. evaluation
7. evaluation
 
7. evaluation (interactive)
7. evaluation (interactive)7. evaluation (interactive)
7. evaluation (interactive)
 
8. evaluation
8. evaluation8. evaluation
8. evaluation
 
7. evaluation done
7. evaluation   done7. evaluation   done
7. evaluation done
 
7. evaluation done
7. evaluation   done7. evaluation   done
7. evaluation done
 
7. evaluation(gaming)
7. evaluation(gaming)7. evaluation(gaming)
7. evaluation(gaming)
 

review

  • 1. project review In this kodu project we were asked to design and visual programing tool. We had options like to designing a cycle with a computer code. In this project we learn to develop the skill of problem solving. We had a design cycle which told us what to do and at what stage we were on, it also told us how much was left to complete this. The first thing i did was to do a plan of my game. This plan consisted in how I was going to do my game and the design of the land. I had very clear how i wanted to do the land. The game was firstly a racing game but then I realised that it was too complicated so I did a adventure game. There was different types of characters and objects. For example there was cycles and a rover for character and for objects you could selects balls, coins and more. The final game was very interesting, i changed a lot of this from the first planning it stared as if it was going to be a racing game but it ended of a game that you need to bring the balls to the glowing point and then destroy the big ball. I think that the design cycle was very useful because i didn't know how to start my game. In some parts i didn't know what to do or at what stage I was.I had technical problems. Firstly my computer didn't work and then kodu stopped working for one week so I had to do other things that wasn't relationated with my game. I wanted to do a more complicated game but kodu didn't have what I wanted so I couldn't do it and that changed all my plans of the game. Or i did have the things I wanted but in a different way and i couldn't figure out how to win the game or how to get my cycle to eat the apple. I had enough time to finish my land and the design but not to get the game work properly. This project develop not the way i wanted but I knew how to arrange it without having to start it again. I would do do better the land of my game, maybe do more holes and more uneven land to make the travelling of the ball more difficult. I could make more enemies so that I makes the game more difficult. The controls were easy just that sometimes the game froze and it didnt let me work properly. More testing would make easier the game because there we could know what we needed to change and what we needed to get better at. with this visual programing we are preparing for a more difficult program and so that we don't get lost so easy..