GPU610/DPS915 Project Requirements 20123

GPU610/DPS915 | Student List | Group and Project Index | Student Resources | Glossary

Project Requirements

Start doing the above by branching the Framework and the Resources into svn://zenit.senecac.on.ca/dps901_113rep?/branches/SenecaID/.... See here for help: Preparing Branches/Workspace for development

The source code for the upgraded Framework sample should include the following updates:

• your own name in the caption for the dialog box
• your team name in the window title
• your own name in the copyright information in the dialog box

Merge all of the team members' Framework workspaces back to trunk so that the caption of the dialog box shows all of the names of the team members. See Merging your work back to trunk for details

The purpose of this first phase of the project is twofold:

• to define your game in both scope and detail and thereby to give your instructor some idea of your design, so that your instructor can give you some feedback whether what you intend is too simple, too complex, or about right
• to show your instructor that you are ready to work with your own branch of your team's repository and ready to start modifying the framework to suit your team's design.

Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page.

Your team should arrange a time and date to meet with your instructor to review your proposal and to identify the different responsibilities of the team members. This meeting should take place during week 6 of the semester.

Phase 2

The second phase releases a draft of your game without sound or input control.

This is your last opportunity to amend your original proposal, modify your design, and obtain your instructor's feedback on your progress.

Phase 3

The third phase presents your completed game with sound and input control to the class. Your presentation includes a demonstration of how the game plays along with an explanation of the innovative aspects that your team members have implemented. Each team has no more than 30 minutes to showcase its game.


-->