Project: Pitch

Pitch: Monday, September 4, 2017
Project preference email: Friday, September 8, 2017

Write a pitch, or proposal, for a game that you think would make a good project for CS3540. For purposes of this assignment, assume that a group will be implementing the project, but if you prefer to do an individual project you can do that.

Include the following items in your pitch:

Title: Give your game a name. I will ask students to send me email with their preferences for projects, so please give your game a distinctive and reasonably short title.

Genre: What genre is your game? If it's a combination or a game that doesn't really fit into a genre, explain.

Game Design: What makes your game fun? Explain the most important game mechanics. In particular, explain how it differs from a typical game in the same genre.

Graphics and Sound: Will your game use 2D or 3D graphics? Are there any particular graphics or animation features, such as particles, or programming techniques that your game needs? What will the user interface be like?

Also, what is the general appearance and feel of your game? For this class we will have relatively simple graphics, but please explain how you would like your game to look if you had the necessary art assets. Likewise, for sound effects and music, explain what you would like your game to have.

Game AI: What kind of game AI are required for your game, or would make your game better? This includes computer opponents, NPCs, map/level generation, finite state machines, decision trees, and pathfinding.

Physics: Is a physics model important for your game? If so, explain.

Feature List: Make a list of features that will be in your game. Some of the features will be things that you described in the game design, graphics and sound, game AI, and physics sections of your pitch. Another way to think of the feature list is as a simple form of requirements document. It's basically a list of things that need to be done to make your game.

You don't have to give numbered priorities the features in the list, but the most important features should be near the beginning of the list and the less important ones near the end of the list.

Modules: What are the most important software components of your game? You can think in terms of classes and groups of classes for this. Describe the classes and the most important methods they will need. Keep in mind that it will be much easier to work in a group and use a code repository if the modular organization is clear and there are well-defined interfaces between modules.

Group: What size of group would be best for your game? I expect most groups to have three or four students, but you can have as few as two or as many as six. (For a very ambitious project, I am willing to consider groups of up to ten students, but that depends on the type of project and the members of the group.)


Style points will be awarded to pitches that are well written and organized, are convincing, and are generally well done. If your pitch doesn't demonstrate that you have put thought and effort into it, you will not receive full points in this category. "Average" pitches will likely receive about half of the possible style points.

Discussion and group formation

Read the pitches posted by other students and think about which projects you would like to work on. I encourage you to comment on other students' pitches, including making suggestions and giving constructive criticism.

After the pitches have been posted and discussed, send me an email with the following information:
--Your preference on group size (which would be one for individual projects).
--Your top three choices for projects to work on. You can include the project that you pitched if you want to, but you don't have to. If you definitely want to work on an indidual project, you don't need to list more than one choice.
--Your preference on being a product owner (group projects only). Product owners will decide what features will be included, what their priorities will be, and which features have been satisfactorily implemented. Product owners will receive a small point bonus for each milestone.
--Your experience with Git (GitHub or BitBucket).

We will choose projects and form groups in class, probably on September 13th.


You can see a sample pitch for an educational game here: Magnificent Adventure at the Magnitude Museum

Turn in

Turn in your pitch by posting it in the Pitches discussion in Canvas.


3 Title and genre
4 Graphics and sound
4 Game AI and physics
10 Game design
5 Style
10 Feature list and modules
4 Group
10 Email with project preferences (due Sept. 8)