Difference between revisions of "BTP300 Project Requirements 20113"

From CDOT Wiki
Jump to: navigation, search
(Created page with '{{BTP300 Index | 20113}} = Due Dates = {| border="1" |- |Assignment 1 - Line Editing Facility |September 23 |- |Assignment 2 |October 28 |- |Assignment 3 |November 18 |- |Assign…')
 
(→‎Due Dates)
 
(29 intermediate revisions by the same user not shown)
Line 6: Line 6:
 
|September 23
 
|September 23
 
|-
 
|-
−
|Assignment 2
+
|Assignment 2 - Field Classes
−
|October 28
+
|November 3
 
|-
 
|-
−
|Assignment 3
+
|Assignment 3 - More Field Classes
−
|November 18
+
|November 30
 
|-
 
|-
−
|Assignment 4
+
|Assignment 4 - Application
 
|December 9
 
|December 9
 
|-
 
|-
 
|}
 
|}
 +
The official due dates are in [https://open.senecac.on.ca/cms/course/view.php?id=267 Moodle].  If there are any discrepancies, the due dates in [https://open.senecac.on.ca/cms/course/view.php?id=267 Moodle] shall apply.
 
<br />
 
<br />
 
<br />
 
<br />
Line 21: Line 22:
 
= Project Requirements =
 
= 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.
−
Your game involves a real-time audio-visual experience in some sort of 3-D world. The user must be able to control at least some aspects of the game with a controller, and there must be some use of sound, both in the background and in response to some action in your game. The user should have control over which display devices, resolution and input devices are used at any time during the game. Your game may however offer only a subset of the available resolutions and input devices. Finally, your design code must differ significantly from the samples presented in class and you must identify the unique elements of your code in your submission logs. 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. All members should contribute to the design part of the assignment.
 
−
-->
 
  
−
== Phase 1 ==
+
== Stage 1 ==
 +
* [https://cs.senecac.on.ca/~btp300/pages/assignments/a1.html Line Editing Facility] - Coded and Submitted Individually
  
−
<!--
+
== Stage 2 ==
−
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. Include in your illustrations 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 includes all of the "actors" (moving objects) in the world.  Identify the coordinates as realistically as possible, being aware that you may need to scale them up or down as you implement your design.
+
* [https://cs.senecac.on.ca/~btp300/pages/assignments/a2.html Frame Classes] - Coded and Submitted as a Group
  
−
Submit the written proposal on your wiki team-page under '''Proposal''' and '''Map of the World of the Game'''.
+
Before starting 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 under '''Repo Path'''
 +
# Add assignment 1 to the trunk of your team's repository as follows
 +
## Checkout your team's empty repository to a new directory on a local computer
 +
## Create the branches, tags, and trunk subdirectories under this new directory
 +
## Under the branches subdirectory create a sub-subdirectory for each team member using their seneca id
 +
## Under the sub-subdirectory for one of the team members create a new sub-sub-subdirectory named '''assignment_1'''
 +
##* You can do this manually or by creating a new Visual Studio solution named '''assignment_1''' under the team member's sub-sub-directory
 +
## Copy the source files for assignment 1 into this directory, compile it and run it. Once it runs successfully, you are ready to add it to the repository server
 +
## Move to the head of the repository directory and add the new directory structure along with the source code for the assignment by right clicking on '''...SVN/Add''' and checking the folders and files to be added
 +
## Commit the directory structure to the repository server by right clicking on '''SVN Commit'''. Add the comment "Created Directory Structure and added assignment 1"
 +
## Branch the committed assignment to '''trunk'''
 +
# The repository is now ready for each team member to start working on their own version of the code in their own workspace
 +
## Checkout the repository to your own local computer
 +
## Branch trunk to your own workspace
 +
## Checkout your workspace
 +
## Work within your own workspace
 +
## Commit your code at the end of each session
 +
##* Make sure to add descriptive comments to each commit
 +
##* Uncommented commits will not be marked or reviewed
 +
If your team is using Visual Studio as its development platform, mark the '''.sln''', the '''.vcxproj''', the '''.vcxproj.filters''', and the source files as versioned, but not the binaries or executables.
  
−
Before continuing phase 1, please do the following
+
Each team member should have their own successfully compiled version of the assignment 1 in their own workspace under the branch sub-directory of their team's repository.
−
# 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/dpsgam/trunk/Framework 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 Framework sample in their own workspace in the branch sub-directory of their team's repository.
+
Branch submission path: svn://zenit.senecac.on.ca/btp300_113_?/branches/SenecaID/assignment1
−
Branch submission path: svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/Framework
 
  
−
: ''Start doing the above by branching the Framework into svn://zenit.senecac.on.ca/gam666dps901_113??/branches/SenecaID/Framework. 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]''
+
Each team member should add their name to the header comments of the '''consoleplus.h''' and '''consolelineedit.cpp''' files as follows:
 +
# Edit the source code to include your name
 +
# Go to '''trunk'''
 +
# Merge your modified source files with '''trunk''' '''...SVN/Merge'''
 +
# Go to the project page and change the repo status to "being committed by your name"
 +
# Commit to the repository with the comment "name added"
 +
# Go back to the project page and change the repo status to "committed by your name"
  
 +
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 source code for the upgraded Framework sample should include the following updates:
+
== Stage 3 ==
−
* your own name in the caption for the dialog box
+
* [https://cs.senecac.on.ca/~btp300/pages/assignments/a3.html More Field Classes] - Coded and Submitted as a Group
−
* 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
+
== Stage 4 ==
−
 
+
* [https://cs.senecac.on.ca/~btp300/pages/assignments/a4.html Application] - Coded and Submitted as a Group
−
 
 
−
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.
 
−
-->
 
−
 
 
−
== Phase 2 ==
 
  
−
<!--
 
−
The second phase releases a draft of your game without sound or input control. 
 
  
−
This is your last opportunity to amend your original proposal, modify your design, and obtain your instructor's feedback on your progress.
 
−
-->
 
−
 
−
== Phase 3 ==
 
−
 
−
<!--
 
−
The third phase presents your completed game with sound and input control to the class.  Your presentation includes a demonstration of how the game plays along with an explanation of the innovative aspects that your team members have implemented.  Each team has no more than 30 minutes to showcase its game.
 
−
-->
 
−
 
−
== Stage 4 ==
 
 
<br />
 
<br />
 
<br />
 
<br />

Latest revision as of 15:25, 9 November 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 November 3
Assignment 3 - More Field Classes November 30
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

Stage 2

Before starting 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 under Repo Path
  2. Add assignment 1 to the trunk of your team's repository as follows
    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 new directory
    3. Under the branches subdirectory create a sub-subdirectory for each team member using their seneca id
    4. Under the sub-subdirectory for one of the team members create a new sub-sub-subdirectory named assignment_1
      • You can do this manually or by creating a new Visual Studio solution named assignment_1 under the team member's sub-sub-directory
    5. Copy the source files for assignment 1 into this directory, compile it and run it. Once it runs successfully, you are ready to add it to the repository server
    6. Move to the head of the repository directory and add the new directory structure along with the source code for the assignment by right clicking on ...SVN/Add and checking the folders and files to be added
    7. Commit the directory structure to the repository server by right clicking on SVN Commit. Add the comment "Created Directory Structure and added assignment 1"
    8. Branch the committed assignment to trunk
  3. The repository is now ready for each team member to start working on their own version of the code in their own workspace
    1. Checkout the repository to your own local computer
    2. Branch trunk to your own workspace
    3. Checkout your workspace
    4. Work within your own workspace
    5. Commit your code at the end of each session
      • Make sure to add descriptive comments to each commit
      • Uncommented commits will not be marked or reviewed

If your team is using Visual Studio as its development platform, mark the .sln, the .vcxproj, the .vcxproj.filters, and the source files as versioned, but not the binaries or executables.

Each team member should have their own successfully compiled version of the assignment 1 in their own workspace under the branch sub-directory of their team's repository.

Branch submission path: svn://zenit.senecac.on.ca/btp300_113_?/branches/SenecaID/assignment1

Each team member should add their name to the header comments of the consoleplus.h and consolelineedit.cpp files as follows:

  1. Edit the source code to include your name
  2. Go to trunk
  3. Merge your modified source files with trunk ...SVN/Merge
  4. Go to the project page and change the repo status to "being committed by your name"
  5. Commit to the repository with the comment "name added"
  6. Go back to the project page and change the repo status to "committed by your name"

See Merging your work back to trunk for details

Stage 3


Stage 4







Retrieved from "https://wiki.cdot.senecapolytechnic.ca/w/index.php?title=BTP300_Project_Requirements_20113&oldid=73747"