Difference between revisions of "BTP300 Project Requirements 20113"
(→Stage 2) |
(→Stage 2) |
||
| Line 44: | Line 44: | ||
## Your team members can now start their own work | ## Your team members can now start their own work | ||
| − | + | <!-- | |
## Create an Visual Studio Project named '''assignment_1''' in '''trunk''' | ## Create an Visual Studio Project named '''assignment_1''' in '''trunk''' | ||
Your team members should checkout your team's empty repository, | Your team members should checkout your team's empty repository, | ||
| Line 96: | Line 96: | ||
* '''trunk''' should never hold non-compiled code. Usually trunk is an exact copy (or better than) the latest version in '''tags'''. | * '''trunk''' should never hold non-compiled code. Usually trunk is an exact copy (or better than) the latest version in '''tags'''. | ||
* Since only one project is within the repository, trunk has no project level sub-directory and is the root of the project. | * Since only one project is within the repository, trunk has no project level sub-directory and is the root of the project. | ||
| − | + | --> | |
<!-- | <!-- | ||
# One of your team members should export svn://zenit.senecac.on.ca/btp300_113/trunk into the trunk of your team's repository | # One of your team members should export svn://zenit.senecac.on.ca/btp300_113/trunk into the trunk of your team's repository | ||
Revision as of 23:34, 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, 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
- 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 branches create a subdirectory for each team member
- Under the team leader's branch create a new subdirectory named assignment_1
- Move up to the head of the repository directory and add this 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"
- Add assignment 1 to the branches sub-directory, compile it, and run it. If the assignment runs successfully add it and commit it to the repository
- Branch the committed assignment to trunk
- Your team members can now start their own work
Stage 3
- More Field Classes - Coded and Submitted as a Group
Stage 4
- Application - Coded and Submitted as a Group
