CSE 481: Capstone Software Design - Spring 2005

About Us

Search

Contact Info

Assignment Overview

Contribute to the success of a 3D, multiplayer game. (We will outline "success" during the first class.)

Leave a buildable code base behind.

Game Requirements

Here are the usual requirements, which continue to be requirements:

• Real-time
• (Interesting) single-player version
• Multi-player capable
• Distributed (when multi-player)
• 3(or more)D

In addition, we want to aim for the following:

• Fun
• Deployment through the CSE 481 game server.
• "No documentation read" launch and (basic) play
• Coherent build procedure
• Coherenet distribution procedure via games.cs.

Code Base

• Each team should have a project named Readme (case-significant) in their CVS repository.

• A cvs co of that project should produce files that tell the course staff how to build your game. You could, for instance, provide a readme.txt file describing the names of the cvs projects that need to be checked out, the names of and links to any tools/software required (that wouldn't be installed oan CSE basement instructional lab machine, say), and how to build them (e.g., build configurations, if using Visual Studio).

• The documentation should be written for someone reasonably familiar with common build strategies.

• The Readme project should provide the name and email of a team member to be contacted in case there are questions and/or build problems.

• Regular attempts will be made to build your project, and the results reported to the contact person.