BTP300 Project Requirements 20113

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

Each game is a team effort. The structure of each team is up to the team members. Each member must contribute their own work in a selected area or areas of their choosing.

Stage 1

• Line Editing Facility - Coded and Submitted Individually

Stage 2

• Field Classes - Coded and Submitted as a Group

Before starting the coding for stage 2, read Hints for Using SVN to collaborate on school projects and do the following:

1. Update your team's wiki page with your team's repository path information under Repo Path
2. Add assignment 1 to the trunk of your team's repository
   1. Checkout your team's empty repository to a new directory on a local computer
   2. Create the branches, tags, and trunk subdirectories under this directory
   3. Under branches create a subdirectory for each team member
   4. Under one of the team member's branch create a new subdirectory named assignment_1
   5. Move to the head of the repository directory and add this new directory structure by right clicking on ...SVN/Add
   6. Commit the directory structure to the repository server by right clicking on SVN Commit. Add the comment "Created Directory Structure"
   7. Add the code for assignment 1 to the assignment_1 subdirectory under branches, compile it, and run it. Once the assignment runs successfully, add it and then commit it to the repository server
   8. Branch the committed assignment to trunk
3. Each team member can now start working on their own task
   1. Checkout the repository to a local computer
   2. Branch trunk to their own workspace
   3. Checkout their workspace
   4. Start working within that workspace
   5. Commit code at the end of each session

Stage 3

• More Field Classes - Coded and Submitted as a Group

Stage 4

• Application - Coded and Submitted as a Group