GROUP FINAL PROJECT
FINAL DEMO
Game Presentation - to be presented to the instructor for grading by 20 minute appointment on Thursday, 5/14 in CS 2129 between 11:00 am and 6 pm. Project grades will be given based on the games themselves as well as the group presentations.
NOTE: You may reserve a presentation time via the class' Blackboard message board.
Game Programming Contest - teams with outstanding projects will be invited to present their games to a panel of judges on Friday, 5/15 @ 5 pm at the Wang Center, Room 201. This will be for fun and to have your name inscribed on the department plaque, not for grades. All students, in our class or not, are invited to attend.
Requirements: All games should meet the requirements of the 3 previously specified benchmarks, and should now be extended into fuller versions for each level. This is your opportunity to fill in all gaps from previous benchmarks and to further enrich your worlds. Remember, one level per team member.
Submission: When you've completed all the components listed below, post your project to your group page as either a compressed folder or a single .exe file. Also post your design document & storyboards to your site. Please do not post any source code to your Web pages.
GRADING CRITERIA:
- Presentation (10%): For each team, you will have 30 minutes to present your game as though you are proposing it to a game publisher. Each student will be expected to play an equal role in the presentation, and will be asked specific technical questions about the implementation of the game. Teams may use laptops or the podium PC in CS 2129. You may use the following steps to guide your presentation:
- First discuss the game concept and why it should be published, using any storyboards, design documents, or game demos you like to do so.
- Demonstrate how to play the game. This is an opportunity to show-off your best features.
- Discuss good gameplay features and challenges.
- Describe the team's distribution of work on the project.
- Allow the Instructor and Teaching Assistants to play each of the game levels. If the levels are particularly difficult or time consuming, provide an advancing mechanism so we may test each level.
- Answer questions from the Instructor & Teaching Assistant.
Reminder: Part of each student's grade will depend on the presentation given to the instructor, where each student will be asked to answer questions about all the development in the project. Students on the same team may be assigned different grades based on their level of competency in answering questions. - Technical Merit (40%): Each game is required to have all following technical components per previous benchmark instructions including some AI, sound effects, music, scrolling, etc. Try to make sure as best you can that your game is bug free.
- Gameplay (35%): Remember, the game should be fun to play.
- Visual & Audio Artistry (10%): Drawing nice bitmaps recording proper sound effects, and selecting the correct music files will be judged such that they are consistent with the goals of the game.
- Documentation (5%): Your documentation should consist of three components:
- Design document - you started this document in checkpoint 1, but you may change what you wrote if necessary. This document should be professional looking.
- Help Screen - Inside your program, as I mentioned before, you should provide documentation for how to play your game.
Those of you who think you've got game should enter it in the 2006 IGF competition. The entry form will be posted online in June, the submission deadline is September 1st, and the student competition is free! It's a great opportunity, and many of you will make games comparable to the other competitors.
Web page created and maintained
by Richard McKenna