Criterion B and C

CRITERION B DESIGN

DESIGN THE PRODUCT / SOLUTION: Include at least 3 possible designs

• Provide multiple designs/design variations – attach additional pages if necessary

Using GameCreator to create a board game-style maze

Using Kodu to make an Adventure free World Style Game

Using Kodu to make a quest style game to find and learn business ideas

• Evaluate designs against specifications

Specs:  To create a game, that teaches an idea or Concept

-GameCreater Maze- The board game would only let you through if you had gotten through a maze that conveyed a business idea. This seems difficult considering the layout and game styles of a maze.

-Kodu Free Adventure Style- The game would allow you to involve yourself with characters indirectly and directly but the order would be random and wouldn’t allow for a controlled and focused goal. This idea would be able to teach the topic but would do so with little success.

-Kodu Quest Style-  This version of game layout would allow you to interact with characters and the environment, but only in a way the game would encourage. I think this layout would be most useful due to its ability to focus your efforts.

• Choose best design & justify choice

- I chose to use the business idea, quest style game. This would allow for more effective learning process when it comes to business, due to the ability to make mistakes and learn from them. Also the quest style is a much more effective when using kodu, due to its control style. Also the programming interface lets programmers create a “no-limits” world.

CRITERION C PLAN

PLAN THE PRODUCT / SOLUTION:

                         

Create a timeline showing what you will do. Include people, hardware, and software. 

 

Step One: Thinking of a series of levels that will teach different business techniques

Task: Thinking of a series of levels that will teach different business techniques

                                                                                               

Date due: 2/11/11              

Process:  For this I simply sat down and thought of some simple business ideas. I came up with Supply, Sale, and Market Research. As Far as I have devised the first level will be on supply (most likely gathering materials), the second will be on Market Research (most likely going around the different stores and figuring out at what prices one can sell items and still turn a profit). The Third and final level will be on Sale.

Step Two

Task: To Draw up a sort of “story board” for the first level               Date due:        16/11/11

Process: I am thinking it would Be about a kodu who needs help gathering apples. You have to gather the apples and then bring them back to him.

Step Three:

Task: Program the First Level                                                      Date due:  30/11/11

Process:  Here I have programmed the first level, which has turned out to be as I planned. I am having some troubles making the commands occur in correct sequence.

Step Four

Task:    Trouble shoot Level One, and Design Questions                           Date due:   7/12/11        

Process: Here I am playing the game and fixing any bugs or problems that show up. There are a number of interfacing questions that are a result of the opening and ending texts. I also have designed my questions. They follow the ‘general’ outline we were given, meaning that they are very broad and allow for a large amount of improvement.

Criterion D Create

USE APPROPRIATE TOOLS AND TECHNIQUES: Discuss the tools available and used. What did you do to develop your skills with these tools?

I used kodu to create my game; I chose kodu because my only other option GameCreater is formatted for arcade style games that follow mazes and levels. Kodu on the other hand lets you go a bit freehand. With kodu I can make the worlds customized to the games needs.

FOLLOW THE PLAN:
Evaluate & reflect on your plan. Describe modifications have you made as you proceeded.

            I have to say that my plan went through many stages before it came to what you see today. when i first devised my schedule i did not account for the real time constraints, and the time consuming processes that go into creating a working and interesting game. Also i had to add detail to the plan, to demonstrate what my exact goal was, my original plan did not even include a step for trouble shooting and evalutation. If i had not included those, the game would most likely be filled with bugs and faults. Luckily i had the resources of exemplars and precious planning schedules, this gave me a general idea of what my plan should include.