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.