Final Project
CIS 410/510 Game Development
Spring, 2008
Proposal
-
Form a group of 1-4 students. Groups may not contain both 410 and 510 students.
-
Prepare a proposal containing the following:
-
A group or game name.
-
The names of all group members.
-
A specific overview of your game, including objectives and conditions for starting, winning, and losing the game. Your game should contain at least three levels which increase in difficulty.
-
A description of each group member's contribution to the game. These contributions should be in addition to the basic gameplay elements and be based on one of the topics covered in class. Possible contributions are: particles, shadows, water, per-pixel lighting, bump mapping, bloom lighting, HDR rendering, physics, audio, etc.
-
Descriptions of what will be accomplished by each milestone (5/9 and 5/23).
-
Email your proposal to eric <at> cs <dot> uoregon <dot> edu by 5 PM on Wednesday, 4/30.
Milestones
-
Email a description of the group's progress towards completion of the game to eric <at> cs <dot> uoregon <dot> edu by 5PM on Friday and 5/9 and Friday 5/23.
Grading
-
Personal grading will be based on (100 points total):
-
Timely delivery of the proposal, milestone, and final documents (20 points).
-
How well the game meets the expectations defined in the proposal document (10 points).
-
The overall presentation of the game (e.g., cohesiveness of the game, game stability, flashiness) (40 points).
-
Completion and quality of your personal contribution (30 points).
Submission
-
Zip your final project directory and email it to "eric <at> cs <dot> uoregon <dot> edu" by 5 PM on Friday, 6/6. Please remove any intermediate files not necessary for compiling and running the application (i.e., a "Clean Solution" operation). Please include all source and header files. Also include a document containing: a description of the game, a list of each group member's contribution to the game (i.e., in addition to basic gameplay elements), and how well you feel that the game meets the expectations defined in the project proposal document.
copyright 2008, Eric David Wills, University of Oregon
back to main