3D games are popular today. There are different types of them. In this project, we would like you to create one of them. We encourage you to create one in the category of Motion Sensing such as WII, Kinect and PS move use your motion as the controller to control the character in the games. 

1. In order to keep this large undertaking on track, as well as to provide a simulation of what it is like to work in industry, groups will be strictly held to a series of deadlines.

• This means that there are no late days available for any milestones or the final version of the game.
• You must set up your deadline for me and let me to check the procedure.

The final game will be graded based on the product (i.e. any lacking axis drags the game down) of its performance along three axis:

• Quality (CS) -- the game should play well and be bug-free
• Unity (Design) -- all elements of the game should be coordinated in service of the game's purpose
• Completeness (CS) -- the game should achieve the goals set out by the group
• A word about ambition (CS, Design)
• Beauty and scene setting(Design) -- Fantastic scenes are important to intrigue people's attention
• Smooth and good UI (Design) -- UI is the most important elements in modern computer applications.

There is a tendency in project classes such as this to grade results based on what they aspire to be, rather than what they are. It is important to notice that the grading criteria above are specifically designed to avoid this. You are graded on the quality of the game you make, not the quality of the game you set out to make.

There will be a significant amount of time devoted to working with project groups to set goals, plans, and fall-backs so that the final game is right-sized.

Elevator Pitches: Everyone in the class will have one minute (strictly enforced) to quickly pitch a game concept. The pitch should clearly convey the core of the game and what makes it unique. Illustrations of some sort are encouraged, but complexity is obviously infeasible.

Refined Pitches: Based on voting from the class (and some instructor english), approximately half the pitches will make it to the next round. These will be re-pitched in five-minute slots by groups of two.

Design Document and Prototypes. Once groups are announced, they have two to three weeks to create a specification (design document) outlining their game.

• Design Document slide 
• The document should also break the components of the game into the essential, the useful, and the simply nice-to-have.
• This design document should be backed by prototypes of the core game elements. The design document and prototypes will be discussed by the class as a whole.

The progress of your program: you must set up the check points for me to check your progress. The check points start around mid of April and roughly three to four check points.

The Demo: At some point the teams will be required to muster their resources and create a demo.

• This demo should demonstrate a segment of near-finished gameplay, or at least hide the seams quite well (e.g. Will Wright's early demos of Spore).

• These demos will be played by the class and discussed.

The Final Version and submission:

• The final version of the game will be shown in an epic Final Crit during the exam slot of the class. You will be scored on this version of the game.
• A readme to introduce how to use the program
• A 10 minute video in English to introduce the game.
• A website

The following is the list of your team set up. Each design student must set up his or her own game and CS students support them to create the game.

TBA