Red Lab C Final Blog

This was the final week for the Mustard Seed project, which meant a lot of work had to be finished.
During the short lab this week, all of the groups had their prototypes finished, and were just finishing up testing reports. The teams presented the prototypes to the lab on Tuesday. All of the prototypes were a success and they were all easily related which was a very important feature. This being the final lab, all of the teams were dividing up the final report.
The representatives for the open house were chosen by the lab on Tuesday. We decided to break the presentation into one hour blocks, for a total of 4 representatives. The Open house went very well, all the Lab coaches and the Mustard Seed representatives were very impressed with the professional look of our prototypes as well as the prototypes themselves.
There are not a great deal of changes that we would have liked to make, but as always it would have been better if we had done more testing on the prototypes which was limited by the time issue.
All in all the project was a success, every member of the lab will leave this class with a new understand of teamwork and what it is to be a real engineer.

Last Post Lab D

This week:

This week was when everything got pulled together. All of the teams finished up their games during short lab. On monday we gave Mitch the games so that he could compile them all into one game (thankyou for that). The long lab was mostly dedicated to tying up loose ends (portfolios, logbooks, open house schedule)with presentations at the end. The presentations went well. All of the groups were ready to go, which was great. Outside of lab time, Jay got the manual and poster printed off after going through some very last minute deadline panics. After switching print companies all turned out well.

Conclusion:

The lab worked very well together on this project. We had no major disputes or missed deadlines. Game maker was difficult to deal with at times and I think that there were a couple people in each group that stepped up to do most of the programming, because it was not feasible for everyone in the group to learn in the time given. Each group had a very different game to suit their theme, but they all fit our city theme. With that in mind, I think our end product was good for the time given. After the close calls on printing the manuals and the poster, I think that next time it would be good to get started on that earlier, but it turned out really well. I would definitely print the poster and manual again. It was expensive, but when divided amongst the group the price was manageable and the end product looked more professional. Overall we had a great lab that worked well together and got things done. All that is left is to finish the final report.

Red Lab A - Status Report #5

As a Lab:

ACCOMPLISHED THIS WEEK

• Assigned who will be included in the poster group
• Discussed poster design, and what materials to use
• Pooled money to acquire GameMaker Pro for import-export feature
• Found out how to create save points in the game once it is compiled
• Came up with a naming system to ensure that sprites and rooms are named intelligently for compilation time
• Assigned quick keys; S = save, Q = quit
• Redesigned quiz room to resemble main room, with separate doors for each subjects quizzes
• Decided who would be in the group to write the design manual
• Read over design manual requirements, and divided responsibilities among group members
• Figured out how to incorporate 8 direction movement into the game, and figured out how to incorporate boundaries into the game
• Figured out how to do multiple choice questions for quizzes
• Worked on game design and quizzes, set due date for all games (Thursday April 8, 2010 in the am)
• Every group recorded testing data for their final report
• Came up with game title – “Math Master”
• Every group discussed outline of final report and divided roles

TO BE DONE NEXT WEEK

• Finish making presentation poster
• Have Open House presentation ready
• Game prototype will be all compiled and will be able to be played
• User/Design Manual to be completed and ready for Open House
• Present final product at the Open House on Thursday April 15th
• Have our last discussion about final report and finish/submit

Lab D Update 5

Accomplished this week:

This week each group finished up their sections of the program. Thanks to Mitch, we now know how to put all of the individual games together to make one game. The project managemnet group met during long lab to discuss the final stages of the project. Work was divided up amongst most of the members, although Jay definitely took on most of the work with the poster and the final touches to the manual. So far everyone seems to be getting along and staying on track going into the last week of the project.

Next Week:

Next week during short lab, the groups will be combining their sections of the game into one game, deciding who is going to be at the open house, and working on the poster. During the long lab final testing on the prototype will occur to make sure it is ready for the open house on thursday. Groups will start working on the final reports in long lab as well.

Lab C Status Report #5 April 9th 2010

Accomplished this week

• Finished initial prototypes

• Tested initial prototypes

• Refined Prototypes and Tested again.

• Defined roles for the final report.

• Started and completed certain parts of the final report

• Completed filming (Group 2)

• Completed Survey (Group 2)

• Finished cards for Board Game (Group 5)

• Tested Game with half the game cards (Group 5)

• Completed Transfer Package (Group 8)

To Be accomplished next week

• Finish all testing and finalize any last adjustments

• Present Prototype at Open House

• Finish Final Report

• Complete a professional looking prototype of the game board. (Group 7)

• Test Games and Instructional Packages amongst peers (Group 8)

• Finish editing of film material (Group 4)

Additional Thoughts

The package is coming together nicely and most groups are on schedule to finish the prototypes and final reports on time. Overall the entire lab group has worked together very well with lots of patient discussion amongst various groups to reach a desirable outcome for everyone. The team has met personal expectations despite a challenging task, the final prototype might not be of quality to implement in the real world but within the time frame provided a group of first years students have done very well.

Updated Gantt Chart

Lab B - Week 5 Update

It is almost the end of the year and we are making our final push!

Accomplishments for the week:

The groups have completed their respective games
Regarding the final product:

-Game introduction has been created
-Primary screen in the form of the map of the world is functional
-The games are being merged by a selected group of individuals

Both the poster and manual design team was formed
Some groups are already working towards the final report
The deadlines have been set regarding the above


To be accomplished next week:

Have the final prototype ready for testing by the instructors
-Further testing of prototype to have it ready for open house

The design manual and poster should be ready
Final report should be completed
Prepare an oral presentation!


Some issues:

Initially it was difficult to merge the games together. We were saved by the export/import functions that the GM has which allowed us to compile the games together without doing it manually(IE copy/paste). Still some minor issues with it which shouldn't hold us back.

Good Luck to everyone!

Lab A Accomplished This Week - Week Four

As a lab it was decided that:

• The game must be designed in a more linear fashion; this means that when the user passes a quiz it will unlock one module, instead of opening multiple rooms at once. The order of the rooms is as follows:

1. Simple Math
2. Data Analysis
3. Units and Conversions
4. Geometry
5. Algebra/Patterns
6. Coordinate Systems
7. Trigonometry
8. Functions

• Whose laptops will be used for the demonstration at the open house presentation
• Each main game designer from each individual group will be expected to help the main compiler put the game together after each individual module is complete
• Team management group will put together the User Manual
• One team member from each team (other than PM Members) will be selected to help put together the poster for the open house presentation (group of 7)

D Lab Update 4

Accomplished This Week

This week was focused on programming and developing questions. Each group was building a solid foundation for their program while researching to find questions to incorporate into the game.

Next Week

Next week all of the groups will be finishing their sections of the game. The project management team will have to meet and discuss possible ways to put all of the sections together into one game. By the end of next week our lab should have a completed section of the game from each group and an idea of how they are all going to come together into one final product.

Lab A - March 28

To be accomplished next week:
- Teams are expected to have their sections completed at most by the end of the week of April 9th
- Compilation to begin shortly after all sections have been received
- Testing is to be done individually by every group before submission of sections
- The Poster Team is to begin preparing a layout and theme, as well as preparing colour schemes etc.
- The Design Manual team is yet to be assigned, contributors of which, will begin working on their assigned parts
- A Presentation Team has to be assigned, contributors of which, will also begin working on their assigned parts
- Final polishing of each section’s plot as well as backgrounds, sprites etc.

Lab A Week 4 Gannt Chart

Reb Lab B - Weekly Status Report #4

Due to the long weekend this week, there was only one short lab this week. As a result, most of the teams did not have too much class time to work on the actual game. However, the work that was accomplished this week will be outlined below as well. Also included are the tasks that are to be accomplished next week as well as a graph that outlines the progress of the lab.

Accomplishments this week:

Individual Teams:

• The final sprites have been implemented into each of the games
• Most teams have completed the first few levels of their game
• The individual game designs and concepts have mostly been finalized and are simply waiting for completion
• Some teams have assigned tasks to team members to work on the game during the long weekend
• Teams have set out testing criteria and will be able to test once their game is complete
• Some teams have actually began to conduct and record some forms of testing
• Some groups have assigned work packages to each team member for the upcoming final report

Lab as a whole:

• The lab nominated four individuals to represent the lab at the Open House Presentation
• A Game Assembly team was formed who will be responsible for compiling the individual games into the final integrated game
• One person from each group has been assigned to be in the Poster team; this team will be responsible for completing the poster that will presented at the Open House
• One person from each team has been assigned to work on designing the 'Instruction Manual' for the final game

To be accomplished next week:

• Each team is expected to have their individual game completed so that the integration process can begin; a date will be set during class as to which date the game is to be completed and sent to the Game Assembly Team
• Testing is to be conducted and finished next week
• Most teams will be starting to work on the Final Report
• The Poster team and Design Manual team will begin to work on their respective parts; a date is to be set during class as to when each of the components should be completed
• Presentation Team will begin writing their presentation for the Open House
• Come up with a catchy name for the final game

NOTES:
Some of the individuals in the lab that are working on creating the actual game for their team have expressed some concern as to having some difficulty with working on certain elements of Game Maker 8.0. There seems to be a lack of instruction on how to utilize the program to accomplish some of the tasks that are required for building the game.

If anyone working on the game in Red Lab B is having any difficulty, please be sure to contact someone in the Game Assembly team for assistance:
Brandon C. (gyrosese@hotmail.com)
Dan S. (dan_the_man_sander@gmail.com)
Mitch W. (yamahaguy_630@hotmail.com)

Lab A Week 3 Gannt Chart

Lab A Status Report 3

ACCOMPLISHED THIS WEEK

LAB ACCOMPLISHMENTS

• lab discussed template-layout of the game
• birds eye view similar to pokemon for gameboy
• maze format, with main boss sprite as well as main user sprite
• messages will appear on bottom third of window
• almost completed games main menu (Jeremy - A1)
• main room design laid out with doors leading to different rooms corresponding to separate subject areas
• each room will contain boss sprite as well as lesson/game sprite
• laid out sequence of subjects (ie: simple math unlocks data analysis which unlocks geometry etc.)
• set standard room size 512x512 pixels
• quizzes will be held in their own separate room
• began to come up with lesson plans for different tables

TO BE ACCOMPLISHED NEXT WEEK

• create lesson portion of the game (have it running)
• begin to work on the actual game portion of our rooms
• have quizzes up and running
• begin to talk about how to compile different modules into one cohesive whole

Lab C Status Report #3

Accomplished this week:

• Finished and handed in functional requirements report.

• Finalized lab plan as well as individual group plans.

• Discussed the integrated design with the entire lab and made modifications where necessary to increase cohesion.

• Set deadlines for both the lab as a whole and the separate groups.

• Split the main concept/prototype in different areas of focus for each group.

• Started the prototype building and modification as per the new design specifications

• Brainstormed possible methods of motivation.

Accomplished next week:

• Continue prototype construction along with starting initial testing.

• Finish the administrative details of the project.

• Implement the integration of all the groups into a functional whole.

Note:

With the short lab week ahead, due to Easter, it will be important to continue work our own and be prepared for Tuesdays section so that when we are together as a whole we can work efficiently.

Lab A Week Two - Additional Information

- It is to be noted that group A1 is not longer incorporating Algebra and Focussing on coordinate systems. Algebra has been given to group A4, as it will be easier to partner with patterns.

- Atleast one member of each group is to complete the tutorial for game maker and experiment with using the program for next week!

Lab A Status Report 2 - March 19

Accomplished this Week

• Completed and presented familiarization
• Tentative lab discussion on the direction the lab wishes to take in the video game design
• Divided functionality report into individual work packages and distributed among group members
• Talked more about the overall feasibility of the ideas the lab wishes to implement into the game
• Groups brainstormed basic ideas for the main game design
• Basis of the overall game layout and theme were brainstormed and decisions were made regarding theme and individual team’s responsibilities
• Some sections were reassigned to different teams in order to establish a balance
• “Minigames” and other reward programs have now been entitled as an extra and are not mandatory

To be Accomplished Next Week

• Begin to prepare foundation of the game, and start to really focus on game design and building
• Compile and hand in functionality report
• Begin looking into teaching and learning strategies, as well as basic quiz-type question structures
• At least one member of each group is to install GameMaker 8.0 and complete the 30 minute tutorial before the next lab

Lab C Status Report #2 March 19 2010

Updated Gantt Chart Showing the completed work

Accomplishments this Week:

• Finalized Familiarization Presentation

• Presented Familiarization Presentation

• Interviewed Mustard Seed representatives which proved to be very helpful. We were able to know more about our clients, allowing us to research solutions that fits their needs

• Took notes during Familiarization Presentation

• Further developed ideas for a project that the entire lab could work on

• Divided work for Functional Requirements Design Proposal

• Worked on Functional Requirements Design Proposal

• Discussed possible themes for the entire group

To Be Accomplished Next Week:

• Finalize and Edit Functional Requirements Design Report

• Decide as a group a lab theme

• Plan the integration of work packages

• Divide up task for work on the prototype

• Start work on prototype

Additional Information:

The additional opportunity to ask the Mustard Seed questions this week did have it's advantages but by then we where ready to do our presentation and additional familiarization was unnecessary, it would have been more beneficial to start work on the functionality report. While the Social area of focus continues to prove challenging there where a number of good ideas for solutions that where presented. Most of the solutions seemed to be along similar lines which should help when the entire project comes together as every group will be able to use some of their ideas they created during the familiarization phase.

Lab A Accomplished this Week - Week Two

Lab

• Finished research for familiarization presentations
• Practiced timing and additional research for familiarization presentations
• Completed and presented familiarization presentations
• Took logbook notes and brainstormed questions related to all familiarization presentations
• Tentative lab discussion on the direction the lab wishes to take related to the theme and overall game design

A1

• Divided functionality report into individual work packages and distributed amongst group members
• Talked more about he overall feasibility of the ideas the lab wishes to implement into the game

A2

• Began to discuss the split functionality report responsibilities
• Set approximate difficulty levels for geometry theme

A3

• Divided up functionality report amongst team members
• Brainstormed rough ideas in the area of conversions and units and how to implement them into the game

A4

• Divided up work for the functionality report
• Started research on the functionality report

A5

• Brainstormed ideas for functionality report
• Divided and distributed responsibilities for functionality report

A6

• Divided and assigned responsibilities for functionality report

A7

• Divided functionality report into individual work packages and distributed amongst group members
• Brainstormed and catalogued ideas for functionality report

Lab D Second Post

Accomplished this week:

Short Lab:
• All of the groups were practicing their familiarisation presentations

Long Lab:
• 40 minutes of practicing familiarisation presentations
• All groups presented
• Groups discussed how to go about finishing the Functional Requirements and

Design Proposal Report

The presentations had some very good information, which will be helpful when designing a product for the Mustard Seed clients.

To be accomplished next week:

Next week the lab will hand in the Functional Requirements and Design proposal report. The groups will work on developing questions for the game and initial programming. By the end of the week each group should have a base of questions to be answered in the game and some rough beginnings of a program.

Lab B Status Report 2

Accomplished This week:

• Familiarization report was compiled and presented
• Log books were used to record essential information
• Groups discussed the impact of the presentations and how to incorporate the attained information from the Familiarization reports
• Teams continued to study their assigned cognitive abilities and finding ways to incorporate the ideas into a game
• Functionality report has been subdivided and assigned to members
• Members spent many hours familiarizing themselves with the Game maker software

To be Accomplished next week:

• Team meeting will take place Friday March 19^th to finalize the theme of the game
• Functionality report will be compiled and completed right on schedule
• Game design and production will begin
• Begin designing and coding levels
• Team will begin preparing instructions for use as their contribution to the design transfer package
• Tentative: Prepare testing packages

Notes:

• Familiarization Presentations went smooth with minimal repetition of the content
• The team appreciates the due date extension that was given
• Several concerns regarding game maker 8.0 and it's lack of ability to function on UNIX based systems were ignored as the mustard seed computers are equipped with Windows.
• Game maker programing language is not C++ which may prove to be challenging to work with at higher levels

Common questions:

Does anybody know where to find basic instructions on coding for game maker?

Does anybody know how to link rooms in game maker?

Lab A Status Report 1

Accomplished This Week

The lab as a whole accomplished generally the same things:

• Researched information for familiarization presentation and split up End-user Needs
• A1: Dyslexia
• A2: Addictions, Self-confidence (lack)
• A3: ADHD
• A4: Lack of resources due to homelessness
• A5: Autism
• A6: Interpretation differences, Visual Perception issues
• A7: Brain damage/ Maturation lag
• Decided that the default software used to make the game in the lab would be Gamemaker
• Assigned individual mathematical areas to each team in the lab
• Brainstormed components to be included in game
• Decided on a common theme for the labs product (an intern at a new company doing different small jobs for his boss)
• Completed both individual team contracts as well as a lab contract

To Be Accomplished Next Week

• The familiarization presentations are to be prepared, practiced and performed
• The lab is to go into depth about what is to be incorporated in their particular section of the game
• Lab groups are to look deeper into the GED requirements and begin to prepare strategies for setting up questions, etc.
• One or two programmers from each lab group are to begin looking into Gamemaker Tutorials and other resources available to help with the actual game-making process
• Prepare basic algorithms for required tasks and begin working on these tasks
• Prepare a few basic creative ideas on how to approach the creating interesting questions
• Look into techniques to keep user interested
• Ask the lab about any theme or story to be incorporated into the game

Lab B Status Report 1

Accomplished This Week:

-project management team selected
-research areas for familiarization presentation were assigned
-team contract and lab contract completed and signed
-teams began to familiarize themselves with Game Maker
-teams researched both the client, the Mustard Seed, and the end users, and defined their needs


To Be Accomplished Next Week:

-practise familiarization presentation
-present familiarization presentation
-determine lab theme for final product
-begin developing concepts for final product
-begin work on Functional Requirements and Design Proposal
-begin work on final product

Lab D Status Report 1

Accomplished this week:

This week, each team was doing very similar things.

• Tasks were broken down for the “Familiarization Presentation”
• Researched on GED
• Researched facts for “Familiarization Presentation” with the team focus

o D1 mental illness and learning disorders
o D2 crime
o D3 addiction
o D4 present environment
o D5 lack of formal education
o D6 malnutrition
o D7 past environment

• Each team discussed possible themes for the project
• The lab decided on an adventure game theme

To be accomplished next week:

Next week each group will;

• Practice content of “Familiarization Presentation” with the team on Monday, March 15, 2010
• Present the “Familiarization Presentation” and take notes on the other teams’ presentations
• Create work packages for each team member for the “Functionality Report and Design Proposal”
• Research their area of the Math GED

o Number Sequences (D1, D5)
o Geometry (D6)
o Measurement (D2)
o Data analysis, statistics, probability (D3, D7)
o Algebra functions/ problems (D4)

In addition, D6 expects their programmers to make themselves familiar with the content and details on how to operate the software program, Game Maker 5.3.