Accomplishments for this week and for next week will be listed by table, as tasks have begun to diversify significantly. Towards the end of the blog, there is a Gantt Chart displaying the lab's progress as a whole.
The Entire Lab (represented by the Lab Committee)
Accomplished this Week:
- The lab completed all of its Familiarization presentations on Mar. 18
- We were faced with assigning components of the game for each group to complete, which was eventually achieved successfully on Mar. 19, with every table having a distinct task (see individual tables)
- It was decided that for deciding the person responsible for compiling the Blog, we would alternate among the Committee members each week
- To ease management, a Programming sub-committee was determined, consisting of generally two members per table
To be Accomplished Next Week:
- The Programming sub-committee will meet to decide any significant obstacles, especially with regards to implementing the proposed ideas
- We will discuss integration of each component in detail
- Functional Requirements and Design Proposal Reports are due
Table C1
Accomplished this Week:
- Split the responsibilities of the four different headings of the Familiarization presentation (background, key player, scope, and benchmarking) amongst our group
- Each member finished writing their part of presentation three days before deadline
- Sent our parts to other members within our group to look over the entire presentation and suggest any modifications or improvements
- Practiced and improved the presentation
To be Accomplished Next Week:
- Decide on an idea/ design proposal for our group that would be unique from any other group’s within our lab, and confirm that idea with the project management team to ensure our idea is unique
- Begin and finish the Functional Requirements Report and Design Proposal based on our group’s idea
- Split the responsibilities of each part in the report amongst ourselves
- Finish the individual parts that each member was assigned
- Compile the report
- Edit the report
- Finish the final report and be ready to hand it in at least a day before the deadline
Table C2
Accomplished this Week:
- Reviewed and rehearsed the Familiarization presentation on Tuesday, 16th of March, 2010 - The familiarization presentation from each group was helpful in understanding the conceptualization (and concept developmental process) of our design
- Our group began familiarizing with the GAMEMAKER 8 software and downloaded it onto our programmer's computer (Scott)
-
To be Accomplished Next Week:
- The programming committee representative (PCR) will be in charge of initially compiling the functional design pseudocode based on our group's functional requirements overview. This pseudocode should be made available to the lab committee representative by Mar. 25, 2010.
- The individual pseudocode will be compared and merged with other groups to generate a flowchart and pseudocode of a grander scale encompassing the entire lab.
- The actual prototyping of the program to be used in the game design implementation needs to begin no later than Friday, Mar. 26, 2010.
Table C3
Accomplished this Week:
- Started getting familiar with Game Maker 5.3
- Team met before Familiarization presentation to practice
- Roles and responsibilities for the Functional Requirements and Design Proposal report were divided amongst the group
- Team agreed on a design for a portion of the lab game
To be Accomplished Next Week:
- Team hopes to get started on making the software of the game
- Team needs to integrate with the rest of lab for design of the game
- Functionality Requirements and Design Report needs to be done by March, 23
- Team will need to finish a weekly status report by March, 26
- Testing of game will need to be done
- Updates to game will be done according to testing
Table C4
Accomplished this Week:
- Did research for Familiarization Project:
- Background of the Client (i.e. Mustard seed)
- Key Players (i.e. Client and Users)
- Scope (goal for the project)
- Benchmarking
- Practiced Speeches
- Presented Familiarizations
- Got started on the Functional Requirements and Design Proposal
To be Accomplished Next Week:
- Choose whether to do an activity or a computer program
- Delegation of Functional Requirements tasks for groups
- Finalize the content of the activity or computer program (content/skill set/target etc.)
- Research done for Functional Requirements Report
- Finish Functional Requirements Report
Table C5
Accomplished this Week:
- Completed familiarization report: became familiar with the specific effects gender has onthe cognitive functions of homeless people
- From our familiarization we learned ways in which we can incorporate these into a game
- Researched on ways to improve cognitive skills into the format of a grocery game
- Decided upon a theme for our group: we will be interfacing with another group, they will flash a grocery list that we need to go and retrieve the items of
- Decided to incorporate distractions to work on memory retention, and organization skills by organizing the food items into specific groups (food aisles)
- Obtained knowledge from other groups’ familiarization reports
- Split up roles for functionality report
To be Accomplished Next Week:
- Complete functionality report, have it done by Tuesday, then send it to the editor to have it ready by Thursday
- Become familiar with the game designer program and have a base design ready to work on for Thursday
- Have all research completed for the specific things we need to work on for design; i.e. time to receive items
Table C6
Accomplished this Week:
- Background research on the cognitive problems of the homeless population with addictions was completed
- Completed research for the rest of the Familiarization presentation
- The team hopes to begin design of our portion of the game and how it fits into the lab program
- The team has assigned a person to become more familiar with Game Maker 5.3
- The team hopes to begin initial steps to start programming our section
- The team had a meeting on Monday, March 15 to plan the familiarization presentation
- The team had a meeting on Wednesday, March 17 to discuss information regarding the presentation. We also practiced the presentation as a group and timed ourselves to make sure the presentation was under the time limit
To be Accomplished Next Week:
- Each Team member will email their portion of the Functional Requirements report to Michael by midnight on Sunday for him to compile the report
- The Team will have a meeting on Tuesday, March 23. We will discuss and do a final edit of the Functional Requirements report. Any portion of the report that needs to be changed will be done then
- Nemanja and Han will familiarize themselves with Gamemaker 5.3
- The team will hand the Functional Requirements report in to Kia on Thursday, March 26.
- The team will begin organizing the content and progression of the game.
Monitoring and Control
Figure 1. A graphic description of the progress of Lab C(red bars indicate actual progress while brown bars show planned timelines)
No comments:
Post a Comment