Orange Lab C Status Report for the week of March 26th

Orange Lab C Blog Status Report for the week of March 26^th

Lab :

Accomplished:

· Set some basic specifications for programming

· Went over layout of program

· Discussed expectations for how the program should work

To be Accomplished:

· Produce basic program

· Develop and integrate programs

· Decide on which game platform to use

Additional Information:

· Need to work on communication and organization between the lab groups

· While designing the program the lab needs to keep in mind feasibility

C1:

Accomplished:

· Functionality Report written

· Platforms examined

· Getting familiarized with Blender application

· Downloaded Construct to use as a platform if Blender doesn't work out

· Determined how to split up work between ourselves and C9

· Created specific work for weeks work

To be Accomplished:

· Get the base for the program written

· Receive work from research teams and figure out what and how to integrate it into the game

· Make sure that we are getting more than just a list of questions from the research teams

C2:

Accomplished:

l Assigned roles and to-do lists for the Functional Requirements and Design Proposal

l Finished research for the report

l Compiled everyone's work into an 11 page report to be handed in Thursday March. 25, 2010

l Learned what they want for the testing component

To Be Accomplished:

• Start on questions to give to the game design group
• There isn't a set amount of questions, but there needs to be enough to get the point across (>20)
• Make diagrams and pictures to accompany questions in order to keep the game more interesting
• Make settings for each question (ex. the setting in the game, building floors, etc.)
• Compile these questions, settings, and ideas in a well organized manner and give them to the programming groups as soon as possible so that they can begin.

Additional Information:

• Theme is very important and needs to be focused on in developing each of the questions.
• Focus also needs to directly on not boring the users of the game.

C5:

Accomplished:

· Finished the functionality report and design proposal

· Brainstormed ideas for the game

· Found twelve different facial expressions for which we can test on

To be Accomplished:

· Help programming group with anything they need

· Write down questions and answers specifically for our task (conversation and facial expressions)

C6:

Accomplished:

· established general design for educational program

· examined engineering requirements and how to implement them into program

· began grating question bank for program

To be Accomplished:

· meet with programming team and relay what we want accomplished

· continue creating question bank

· communicate with other teams so that our programs do not overlap too much

Additional Information:

· call group meeting to talk about starting programming as soon as possible

C8:

Accomplished:

· Came up with the artificial hand/ circuit prototype

· Thought of ways to incorporate handshakes into the game

· Split up the functionality report and had finished it/handed it in

To be Accomplished:

· Hopefully finish the artificial hand prototype

o Buy and construct materials

· Know exactly what kind of software/program we will be dealing with

· Incorporate out ideas into the program

C9:

Accomplished:

· determined the framework of the project, main project goals, and integration with other lab groups.

· narrowed the potential development platforms down to two choices; construct or blender.

· finished the functionality report prerequisite.

To be Accomplished:

· deciding on which development platform to use (by Monday).

· deciding on precise details of game framework and graphics (Monday).

· Completing the main model or image (by Wednesday).

· Completing the first interrupt sequence (by Thursday).

· Completing a basic working prototype by Thursday's lab.

· Receiving input and suggestions from the lab on Thursday.