From CDOT Wiki
Revision as of 05:53, 30 September 2011 by Chris Szalwinski (talk | contribs) (Created page with '{{BTP300 Index | 20113}} Please help make this page resourceful for all BTP300 students to use! = Object-Oriented Programming I - C++ = *This course continues the study of obje…')
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

BTP300 Fall 2011 | Weekly Schedule | Student List | Project Requirements | Teams and their Projects | Student Resources

Please help make this page resourceful for all BTP300 students to use!

Object-Oriented Programming I - C++

  • This course continues the study of object-oriented programming, which started with BTP200. This course covers details of the C++ language at the intermediate level.

Subject Description and Course Outcome

External Links

The Project

The course project is a four-stage assignment to build a game using the framework as the starting point. Each team consists of up to 4 members. Membership is subject to instructor approval and is open to modification until the end of the week of the drop date for the course. The first stage of the assignment augments the console library that supports the course with a line-editing facility. This stage is completed individually. The next three stages are team stages. Each member is responsible for one aspect of each stage. Details are on the Project Requirements page.


  • Assignment 30%
    • Individual Work - 50%
    • Group Work - 50%
    • Total (Individual + Group) - 100%
  • Workshops 10%
  • Test 30%
  • Exam 30%

Assignment Submission Requirements

Stage 1

Submit your assignment to Moodle as per the instructions on the assignment specifications

Stages 2 through 4

When ready to submit your final project:

  1. Finalize your modifications in trunk.
  2. Create a directory in trunk called: "SubmissionLogs"
  3. For each member of the team create a text file named as "YourSenecaEmailId.txt" in the "SubmissionLogs" directory. In this text file, in a point form, specify in detail, all the tasks you have done for the group project.
  4. Branch (copy) the whole project including the SubmissionLogs directory and its text files into tags directory under "prj1.0".
  5. If final adjustments are needed after these steps, repeat everything from step one but branch the trunk into a new directory in tags as prj1.1, prj1.2, etc.
    (for marking purposes, your instructor will consider your last revision as your submission)


Examples and In-Class Notes