Difference between revisions of "BTP300 Project Requirements 20113"
(→Stage 1) |
(→Stage 2) |
||
Line 30: | Line 30: | ||
== Stage 2 == | == Stage 2 == | ||
+ | * [https://cs.senecac.on.ca/~btp300/pages/assignments/a2.html Field Classes] - Coded and Submitted as a Group | ||
<!-- | <!-- | ||
− | + | Before continuing stage 2, 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''' | ||
+ | # Create a 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 your team members should export svn://zenit.senecac.on.ca/btp300_113/trunk into the trunk of your team's repository | ||
+ | #: For detailed steps 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]] | ||
− | + | Each team member should have their own successfully compiled version of the assignment 1 in their own workspace in the branch sub-directory of their team's repository. | |
+ | Branch submission path: svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/assignment1 | ||
+ | |||
+ | : ''Start doing the above by branching the Framework into svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/assignment2. 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 sample should include the following updates: | ||
+ | * your own name in the caption for the dialog box | ||
+ | * your team name in the window title | ||
+ | |||
+ | |||
+ | 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 [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 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. | ||
--> | --> | ||
Revision as of 19:52, 4 October 2011
BTP300 Fall 2011 | Weekly Schedule | Student List | Project Requirements | Teams and their Projects | Student Resources
Due Dates
Assignment 1 - Line Editing Facility | September 23 |
Assignment 2 - Field Classes | October 28 |
Assignment 3 - More Field Classes | November 18 |
Assignment 4 - Application | December 9 |
The official due dates are in Moodle. If there are any discrepancies, the due dates in Moodle shall apply.
Project Requirements
Stage 1
- Line Editing Facility - Coded and Submitted Individually
Stage 2
- Field Classes - Coded and Submitted as a Group
Stage 3
Stage 4