Changes

Jump to: navigation, search

GAM666/DPS901 Project requirements 20103

49 bytes added, 07:59, 28 September 2010
Phase 1
The first phase is a 200-300 word informal, written proposal of what you intend to implement in your game: what you imagine your game doing. Your description should identify the objects in your game and include one or more illustrations of your design. The illustrations may be hand-drawn and scanned. Included in your illustrations should be a map of what you envisage the 3D world of your game will look like, with 3-dimensional coordinates of all of the major points in the world. Your map should include all of the "actors" (moving objects) in the world. You should identify the coordinates as realistically as possible, being aware that you may need to scale them up or down as you implement your design in code.
Submit the above written proposal on your wiki team-page under '''Proposal''' and '''Map of the World of the Game'''.
Before continuing phase 1 , please do the following
# Read [[Hints for Using SVN to collaborate on school projects]]
# Update your team's wiki page with your team's repository path information under '''Repo Path'''# Each team member please create Create a direcotry directory with your seneca id under the branch sub-directory of your team's repository. This will be your home directory for development; for details see: [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Directory_Structure Directory Structure]# One of the team members should volunteer to export svn://zenit.senecac.on.ca/dpsgam/trunk/15-Controller into the trunk of the your team's repository;
#: For hints see [[Hints for Using SVN to collaborate on school projects#Start_the_project_by_continuing_an_existing_work | Start the project by continuing an existing work]];
As part of the submission each Each team member should provide have their own successfully compiled version of the 15-Controller sample in their own workspace in branches the branch sub-directory of their team's repository.
Branch submission path: svn://zenit.senecac.on.ca/dps901_103rep??/branches/SenecaID/15C
: ''Start doing the above by branching the 15-Controller into svn://zenit.senecac.on.ca/dps901_103rep??/branches/SenecaID/15C. See here for help: [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Preparing_Branches.2Fworkspace_for_development Preparing Branches/workspace for development]''
The source code for the upgraded 15-Controller sample should include the following updates:
* add your own name to the caption for the dialog box
* change the window title to include the name of the team
You can obtain a copy of this sample from the dpsgam course repository.
Merge all of the team members' 15C workspace workspaces back to trunk so that the caption of the dialog box shows all of the names of the team memebersmembers. See [http://zenit.senecac.on.ca/wiki/index.php/Hints_for_Using_SVN_to_collaborate_on_school_projects#Merging_your_work_back_to_trunk Merging your work back to trunk]for detail
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: whether what you intend is too simple, too complex or about right
* to ensure 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 submission should enable your instructor to give you feedback and to discuss your proposal in some detail.
Your team should decide its own group to individual ratio for grading purposes and post the agreed ratio on its project page.
Your team must arrange a time and date to meet with your instructor to discuss the proposal and to commit the different responsibilities of the team members. This meeting should take place no later than week 6 of the semester, preferably earlier.

Navigation menu