Difference between revisions of "BTP300 Project Requirements 20113"
(→Stage 2) |
(→Stage 2) |
||
| Line 34: | Line 34: | ||
# Add assignment 1 to your team's repository | # Add assignment 1 to your team's repository | ||
## Checkout your team's empty repository to a new directory on a local computer | ## Checkout your team's empty repository to a new directory on a local computer | ||
| − | ## Create the branches, tags, and trunk subdirectories | + | ## Create the branches, tags, and trunk subdirectories under this directory |
## Under branches create a subdirectory for each team member | ## Under branches create a subdirectory for each team member | ||
| − | ## Under the team | + | ## Under one of the team member's branch create a new subdirectory named '''assignment_1''' |
| − | ## Move | + | ## Move to the head of the repository directory and add this new directory structure by right clicking on '''...SVN/Add''' |
| − | ## Commit the directory structure to the server by right clicking on '''SVN Commit'''. Add the comment "Created Directory Structure" | + | ## Commit the directory structure to the repository server by right clicking on '''SVN Commit'''. Add the comment "Created Directory Structure" |
| − | ## Add assignment 1 to the branches | + | ## 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 |
## Branch the committed assignment to '''trunk''' | ## Branch the committed assignment to '''trunk''' | ||
| − | ## Your team members can now start their own | + | ## Your team members can now checkout the repository to their local computers, branch trunk to their own workspaces, and start working on their own tasks |
<!-- | <!-- | ||
Revision as of 22:43, 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
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:
- Update your team's wiki page with your team's repository path information under Repo Path
- Add assignment 1 to your team's repository
- Checkout your team's empty repository to a new directory on a local computer
- Create the branches, tags, and trunk subdirectories under this directory
- Under branches create a subdirectory for each team member
- Under one of the team member's branch create a new subdirectory named assignment_1
- Move to the head of the repository directory and add this new directory structure by right clicking on ...SVN/Add
- Commit the directory structure to the repository server by right clicking on SVN Commit. Add the comment "Created Directory Structure"
- 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
- Branch the committed assignment to trunk
- Your team members can now checkout the repository to their local computers, branch trunk to their own workspaces, and start working on their own tasks
Stage 3
- More Field Classes - Coded and Submitted as a Group
Stage 4
- Application - Coded and Submitted as a Group
