Week of 22-26

As a whole, our lab was quite productive this week, we:

• Handed in our reports on functionality and design
  
• Worked on our games and created data bases for our questions.
• Had a few group discussions and followed up on individual organization.
  

Table update - Lab C - March 26

This is what each table completed this week.
C1 - programed a couple of games to get the hang of Game Maker
- Written some of the questions for the program
C3 - They have created their sprites which are moving people
- They have had a couple of team meetings and they are really developing as a team.
C6 - Started their game
- Developed a database for the game questions
C7 - Finished all their questions
- Started programing a 50s racing game
C8 - they have found a way to run Game Maker on their macs
- because their questions are all developed they only have their game left to program
C9 - they have made a simple version of their game that is functioning
- created some of the sprites needed for their game

White Lab - What is Going to be Done Next Week

Here’s a look at what the White lab plans to do next week:

C9

- Choose questions to implement in the game

- Modify the game

C8

• Improve the game
• Continue making content for the game

C7

• Continue making the game

C6

• Make the game
• Finish making questions
• Get Sylvia Harrison to make sure they’re on the right track

C3

• Have the first few levels out of sixteen completed

C1

- Continue to make questions

- Continue working on the game

Graphical Report #3

Here is graphical report # 3 for Lab C on where the lab is, vs. where the lab planned to be.

White Lab A Report, March 26/2010

Lab Accomplishments

- Funtionality reports finished and handed in

- Prototypes started

Lab Goals

- Have working tested prototypes for Tuesday

A1 Accomplishments:
- Defined third game: "Ladies and Gentlemen".
- In mastermind: The comparison of objects has been improved to allow the comparison of 4:4 objects rather than 1:1:
- In mastermind: The comparison of the guess code to the actual code now includes object position as well, instead of just colour.
- In mastermind: Improved the game so there's a total of a maximum of 10 guess codes to compare to the actual code.
- In mastermind: Implemented a "lock" function, that prohibits the user from modifying a guess code after evaluating it, and from skipping guess code lines.

A1 Goals:
- Implement a graphical design for mastermind to match the lab's theme.
- Implement a betting function that allows the user to bet virtual money before the beginning of each game.
- Start working on the creation of the other two games.

A2 Accomplishments:

- Improved program code in driving game to work with trailers and have realistic turning physics

- Searched and studied different attention games for basic ideas to base physical challenge off of or for smaller rule ideas

- Started sprite design for computer driving game to be implemented over the weekend, sprite blocking size finalized at 60x60 px

- Computer rules finalized in pseudocode and discussions started on how to implement the rules as objects into game GUI

- Points system started as a reverse health counter and saving rounds as points sets

A2 Goals:

- Fully integrate new sprites into computer program and tweek movement

- Integrate rules as objects

- Have prototype started for physical challenge

A3 Accomplishments:

- Coded a mini game

- Created all images and sprites

- Created and coded menu for the entire lab to integrate onto

- Disassembled disposable camera for physical challenge

- Made quick quiz

A3 Goals:

- Integrate all other teams computer programs into menu

- Fine tune boat game

- Finish off camera disassembly task

A4 Accomplishments:

- Division of labour for both hands on and computer game finalized

- Tested physical game

- Finished final planning for all games

- Began work on computer based challenge

A4 Goals:

- Finish physical portion

- Complete both source codes for next tuesday's class

- Division of labour for final report

A5 Accomplishments:

- Began game- went through tutorial and created all necessary sprites and objects

- Had a team meeting to discuss work progress and schedule
- Divided tasks for game making and final report
- Finalized design outlook
- Got a better feel for what the end result is going to look like

A5 Goals:

- Complete the game by the end of the weekend and if necessary, use Monday to sort out bugs in the program for Tuesday
- Begin final report
- Have one or two team meetings to make sure we are all on the same page

A6 Accomplishments:

- Using game maker, developed the basic coding for the animal chess game. All sprites are created and can move properly

- Wrote storyline for video clips based on logic and problem solving

- Have blueprints for gear wheel game and how it will be built

- Discussed all the possible characters in the video clips

A6 Goals:

- Figure out how to program the chess pieces to eat each-other

- Start gathering materials for the gear wheel game

- Start thinking how the theme "money" relate to games and can be integrated

A9 Accomplishments:

- Final design idea finalized

- Started programming computer based challenge

- Started integrating theme into game designs

A9 Goals:

- Finalize game sprites and programming

- Integrate game into A3 interface

- Prepare for presentation

White Lab B - Mustard Seed Challenge Week 4

OVERVIEW OF PROGRESS

TABLE B1

What was done this week

• The Functionality report was finished
• Started working on the propoasl and game
• The enemy sprites were designed
  

What is going to be done next week

• Have a game design completely done
• Write questions for the quiz
• Start the Final Report
  

TABLE B2

What was done this week

• The Functionality report was finished
• Started working on the game
• The documents and questions to be placed into the game are partway done
  
• Discussed ideas about the level designs
• Researched designed for the sprites
• Set deadlines for the game next week
  

What is going to be done next week

• Finish the basic design of the game and collaborate with the lab to decide upon common sprite
• Have documents and questions completed
• One team meeting scheduled to discuss progress
  

TABLE B3

What was done this week

• The Functionality report was finished
• The base of the game was completed
• Sketches for the background were done
• Sprites were designed
  

What is going to be done next week

• Have game design done completely
• Finish documents of questions
  

TABLE B4

What was done this week

• The Functionality report was finished
• Designed possible levels
• Explored more with GameMaker
• Drew sketches of possible sprite designs
• Searched for available sprites online
• Tested what has been completed of the game thus far
  

What is going to be done next week

• Have game design completely done
• Complete half of game
• Write introduction to game
• Prepare documents thaat will be placed into the game
• Consider possible questions for game
• Collaborate with lab and decide on common sprites in games
• Start planning design transfer package for our game
  

TABLE B5

What was done this week

• The Functionality report was finished
• Sprites were designed
• Backgrounds were designed
• Documents are being worked on
• Started working on the game
  

What is going to be done next week

• Finish game design
• Start posters and open house presentations
  

TABLE B8

What was done this week

• The Functionality report was finished
• Preliminary debugging of the game continued
• Tested other games for design ideas
• Developed sprites
• Created hints and tips to be implemented in the game
  

What is going to be done next week

• One group meeting scheduled
• Start work on final report
• Input all questions and answers into the game
  

MONITORING AND CONTROL

A linked Gantt Chart is presented to visually demonstrate the expected and actual progress of the lab over the past week.

ADDITIONAL INFORMATION

This week students are still complaining about the Game Maker program. There have been complaints that the trial version supplied by the university, first does not properly work, and secondly the trial version is not adequate to develop a proper game.

Additionally, some members of the lab have noted that time is running out and some teams are still far behind on their game development. Some have attributed this to the Project Management team and their lack of coordination of the lab. Teams aren't sure about the sprites that will be used, and don't know how integration between tables will happen. Team Management, although they are doing a fantastic job, should probably try to address these issues.

Finally, there has been a suggestion that productivity on the project is lacking due to the early morning lab times. It has been suggested that Project Management buy us coffee.... that would make this blogger very, very happy! =D

This week in D white lab:

- ----The PM team laid down the design of the poster for the open house and purchased the materials

- We handed in our Functionality reports and began planning the design Manual

- Work for the design manual and final poster was distributed throughout the lab with due dates assigned

- Individual tables began discussing the final report

- Mark and Bennet dressed the same

To be accomplished next week

-Without a long lab there is only one and a half hours of lab time.

-This lab will be used as a work period as there are no set due dates until the following week.

-It is expected that all groups are well on their way to completing their games as project management has set that they are due tuesday after easter break

White Lab D blog friday march 26

This week in D white lab:

- The PM team laid down the design of the poster for the open house and purchased the materials

- We handed in our Functionality reports and began planning the design Manual

- Work for the design manual and final poster was distributed throughout the lab with due dates assigned

- Individual tables began discussing the final report

- Mark and Bennet dressed the same

To be accomplished next week

-Without a long lab there is only one and a half hours of lab time.

-This lab will be used as a work period as there are no set due dates until the following week.

-It is expected that all groups are well on their way to completing their games as project management has set that they are due tuesday after easter break

This week in D white lab:

- The PM team laid down the design of the poster for the open house and purchased the materials

- We handed in our Functionality reports and began planning the design Manual

- Work for the design manual and final poster was distributed throughout the lab with due dates assigned

- Individual tables began discussing the final report

- Mark and Bennet dressed the same

To be accomplished next week

-Without a long lab there is only one and a half hours of lab time.

-This lab will be used as a work period as there are no set due dates until the following week.

-It is expected that all groups are well on their way to completing their games as project management has set that they are due tuesday after easter break

Lab C Graphical Report # 2

Here is a graphical report #2 for Lab C on where the lab is, vs. where the lab planned to be.

White Lab A, March 19th Update

General Lab Accomplishments

- Presented familiarization presentations

General Lab Goals

- To complete and hand in functionality proposals

A1

This Weeks Accomplishments:
- Finalized idea for second game based challenge
- Created the prototype for an object that randomly chooses a new sprite at the beginning of the game
- Created the prototype for an object that has a sprite that can be changed by the user by clicking on it
- Created the prototype for an object that compares the sprite of the user-defined object against the randomly object, and displays a white colour if both objects have different sprites, or displays a black colour if both objects have the same sprite.

Goals:
- Define what the third game is going to be.
- Improve the mastermind game so that the comparison object not only compares one pair of object but four pairs of objects
- Improve the mastermind game so that the comparison object also compares the object's position

A2

This Weeks Accomplishments:

- Finalized computer challenge idea to be car based challenge with the option of a trailer in order to teach new skills valuable for the workforce

- Considered new physical based ideas for the reality part of challenge

- Started art and sprite concepts for when programming starts for easy integration

- Continued familiarizing with game maker in order to provide smoother integration of pieces and to create a better final product

Goals:

- Start programming the prototype program and integrate concept art

- Finalize physical idea and begin the prototype of physical concept

A3

This Weeks Accomplishments

- Organized tasks and broke project into assignments for members

- Created an effective design proposal for the lab as a whole

- Created an effective design proposal for single team to use as concept

- Communicated with the mustard seed representatives in order to gain insight of requested or required modules to be integrated into final project

Goal:

- Complete design and begin basic testing

- Find an item to disassemble in order to begin second physical based task

A4

This Weeks Accomplishments:

- Divided project into work packages and assigned packages to individual people

- Finished planning to the final product and started building a prototype for the game component of the project

- Identified the needs of the mustard seeds guests that can be addressed through this project

Goal:

- Begin working on the physical portion of the project and complete a functional prototype to begin testing

- Finish computer based component in order to begin testing the product

A5

This Weeks Accomplishments:

- Studied the topic of memory and techniques to improve memory in al types of individuals

- Team meeting on monday

- Brainstormed 3 tasks for the individual components to make up the assigned portion given

- Began testing game maker 8 and developing program based on lessons learned from tutorials and online archives

- Designated work packages for every member of the group in order to streamline component development and report writing

Goals:

- Have a functioning prototype of the program available to begin testing each component

A6

This Weeks Accomplishments:

- Researched ideas for computer games focusing on logic skills

- chess, gears, 3-D puzzles etc

- Continued familiarizing with the game maker 8 program and started creating a program

Goals:

- Finish designing a functional prototype

- Begin testing the prototype

A9

This Weeks Accomplishments:

- Finalized the basic design and game design theme

- Became more familiar with game maker 8 and reviewed tips and tutorials

- Researched and learned the need of the mustard seed in the given area of the project

- Organized work packages and divided project among members in order to make work faster and easier on all members

- Discussed issues with the Mustard Seed and identified people that are strong users of the program to gain future assistance

Goals:

- Finish the programming of the prototype and begin testing

White Lab B - Mustard Seed Challenge Week 3

OVERVIEW OF PROGRESS

TABLE B1

What was done this week

• Worked on the report
• Started using Game Maker
• Functionality presentation

What is going to be done next week

• Finish Functionality and Design Proposal report
• Start working on building the game level

TABLE B2

What was done this week

• Started working on the level
• Split up the work for the report
• Designed the overall look of the stage
• Functionality presentation

What is going to be done next week

• Finish Functionality and Design Proposal report
• Continue with the game development
• Finish level designs

TABLE B3

What was done this week

• Set up the steps for the level
• Split up the work for the report
• Set a personal deadline for the game
• Functionality presentation

What is going to be done next week

• Finish Functionality and Design Proposal report
• Continue working on game development
• Record sound and try to implement into Game Maker

TABLE B4

What was done this week

• Started working on the game design and development of the game
• Researched more about homelessness in Calgary
• Worked on the report
• Redefined the team roles and the game design
• Functionality presentation

What is going to be done next week

• Finish Functionality and Design Proposal report
• Finish design process and start working on the program

TABLE B5

What was done this week

• Split up the work for the report
• Functionality presentation

What is going to be done next week

• Finish Functionality and Design Proposal report
• Continue on game development

TABLE B8

What was done this week

• Split up the work of the report
• Found images for backgrounds and sprites
• Finished first part of the game development (preliminary debugging)
• Finished the level design
• Functionality presentation

What is going to be done next week

• Finish Functionality and Design Proposal report
• Build the designed levels and make questions
• Implement backgrounds, sprites and questions into the game

MONITORING AND CONTROL

A linked Gantt Chart is presented to visually demonstrate the expected and actual progress of the lab over the past week.

ADDITIONAL INFORMATION

Continuing from last week, some frustration by lab members still persists. The majority of frustration is focused on the functionality report, and lack of understanding of what the coaches and lab instructors specifically want. Also, one of the teams has noted that game maker does not work on the virtual machines, as it does not support 3D graphics acceleration.

Additionally, with the game due in just under four weeks, many teams are starting to feel the pressure as games are only just beginning to be started. Many teams have not yet, or are only just beginning their game development. They attribute this to the team contract, familiarization presentation, and functionality report taking precedence over game design over the past couple weeks.

Finally as one team noted, the game design proposed by the Project Management team is unfeasible. Project Management have proposed that as the player progress through each level, they find themselves confronted with a question. An answer (whether right or not), would lead to a different pathway. One lab member thus calculated that if each question has four multiple choice answers, a total of 1,048,576 pathways would have to be made ... an impossible amount for the short time limit. Thus, this idea needs to somehow be revised.

Goals Achieved this week

- Teams successfully delivered 6 presentations about the different end users that our game will be directed towards.

- Each team developed a better understanding of the other end users from the research presented by each team.

- The entire lab has agreed on a hub world theme for the game which will be designed to look like an arcade game.

- William has provided each team with the software to develop our game. The lab is going to use RPG Maker XP to create the game.

- Each team has now decided on a final idea for their game.

- William has almost completed the hub world for the entire lab.

Goals to be accomplished next week:

-A more copious understanding of RPG maker needs to be gained by the software experts of each group.

-Each section needs to finish functionality report for Tuesday.

-Development of the hub world needs to continue linearly, possibly complete.

-Groups should at least have a small start to programming their game.

Comments

We feel the project is going swimingly, all groups have quality ideas and we think it will fit together better than Jenga

Table update - Lab C - March 19

Here is what each table has complete this week
C1 - Broke down their level of the game into work packages
- Divided the report among the group members
C3 - decided on content of the game and how they are going to incorporate the educational component
- Familiarized themselves with game maker
C6 - Finished design proposal
- Communicated with experts regarding GED content.
C7 - Filmed their familiarization presentation over the weekend.
- They started their design proposal and have started looking at game maker
C8 - Finished writing all the test questions for their section of the video game
- Worked on trying to find a Game Maker 8 that is compatible with Mac.
C9 - Brainstormed questions for the initial test
- Explored game maker and split the design proposal into sections

White Lab - What is Going to be Done Next Week

Here’s what the white lab wants to get done next week:

C1
- Get the Functionality Requirements and Design Proposal done
- Begin making the game
- Divide up the work for the final report
C9
- Get the Functionality Report and Design Proposal done
- Begin making the game
- Incorporate components into the game
C8
- Get the Functionality Report and Design Proposal done
- Find a solution for Macbook to make a game
C7
- Get the Functionality Report and Design Proposal done
- Start video game
C6
- Start the game
- Make questions for the game
- Familiarize selves with game
- Talk to experts about the game
C3
- Get the Functionality Report and Design Proposal done
- Get most components done
- Start programming the game
- Go down to the mustard seed and talk to workers

White Lab B - Mustard Seed Challenge Week 2

OVERVIEW OF PROGRESS

TABLE B1

What was done this week

• Starting the familiarization presentation
• Decided on roles of team members
• Looked over the Game Maker program

What is going to be done next week

• Finish familiarization presentation
• Will begin making their game

TABLE B2

What was done this week

• Started the familiarization presentation
• Decided on roles of the team members
• Looked over the program Game Maker
• Brainstormed game concepts

What is going to be done next week

• Prepare for presentation
• Finish familiarization presentation
• Start on design and programming of their game
• Start on functionality report

TABLE B3

What was done this week

• Decided on roles of the team members
• About 2/3 of the familiarization presentation was completed
• Finished research for the mustard seed
• Looked over the Game Maker software

What is going to be done next week

• Phone-in to mustard seed to ask questions about the client's and users' needs
• Finish familiarization presentation
• Start on the functionality report

TABLE B4

What was done this week

• Decided on roles of team members
• Experimented with Game Maker
• Started familiarization presentation
• Started some research for the presentation

What is going to be done next week

• Finish familiarization presentation
• Start programming their game
• Start on functionality report

TABLE B5

What was done this week

• Came up with concepts for the game
• Decided on the team roles
• Started on the familiarization presentation
• Looked over the Game Maker program

What is going to be done next week

• Finish familiarization presentation
• Start programming their game
• Start on functionality report

TABLE B8

What was done this week

• Learned how to use the Game Maker program
• Decided on the team roles
• Started on the familiarization presentation

What is going to be done next week

• Finish familiarization presentation
• Going to start creating their game
• Create documents for the game stage

MONITORING AND CONTROL

A linked Gantt Chart is presented to visually demonstrate the expected and actual progress of the lab over the past week.

ADDITIONAL INFORMATION

First of all, I would like to acknowledge Brenna Philley for finding a report on homelessness, in Calgary. As some lab members have noted difficulty in finding information, I hope that somewhere in this long report someone can find some relevant information. The report can be found at the following link: http://www.calgary.ca/docgallery/bu/cns/homelessness/2008_count_full_report.pdf

Speaking with the students in the lab has revealed that some are unhappy with the current project. Some feel that it is difficult to reflect an application of engineering. Others feel that using computer games as the means to relay the information to the end user is inappropriate, and likely unappealing to those middle aged persons who will be using the software. Finally, as the lab focuses on social cues, some lab members are finding it difficult to incorporate the teaching of social interaction skills via computer games. A suggestion by this blogger would be to have the Team Management assess and attempt to remedy these issues, so as to curtail the possibility of rising dissent by lab members.

Here is a general idea of what the C lab hopes to accomplish next week:

C1

• Familiarization
• Get a better grasp of game maker
• Divide the components for educational aspects of probability and statistics

C8

• Familiarization presentation
• Getting the game started (starting/ setting up)

C7

• Start video game

C6

• Group meeting is need be
• Need to create an idea
• Want to clarify and make a solid plan
• Realize what the project is asking ( what the client is asking for )

C3

• Get started on the game
• Basic game design

C9

• Plan to create and practice familiarization presentation
• Start game design process
• Finish presentation
• Research mustard seed ( see what programs they have that relate to the project )

White Lab D thus far..

This is a Gantt chart of the expected times required for each step and the percentages of each done.

Accomplished This week:

Designated/volunteered members of the project management team.

Assigned tables a topic each for the familiarization presentation.

Discussed several possible designs/layouts of the project.

Decided on general layout and the use of RPG Maker to create it.

Will educated us all on the basic use of RPG Maker.

Brainstormed individual game ideas within table groups.

To be accomplished next week:

· Gather data/information from other groups VIA the familiarization presentation.

· Better understand the client, and what exact issues the homeless are facing and how to address them.

· From our new understandings form an idea of what our program should “do” and how it can accomplish these goals.

· Get these ideas on paper and form them into a well thought rough thoughts paper.

· As we start to work with our new groups, bring the best everyone has to the table by recognizing strengths in the team.

· Start to learn the software so when it comes to programming its not a huge shock!

· To make the world a better place

Lab C Graphical Report

Here is a graphical report for Lab C on where the lab is, vs. where the lab planned to be.