Difference between revisions of "BTP300"

From CDOT Wiki
Jump to: navigation, search
(→‎Archives)
(→‎The Project)
Line 11: Line 11:
 
* [https://cs.senecac.on.ca/~btp300/pages/content/index.html Course Web Site – Lecture Notes]
 
* [https://cs.senecac.on.ca/~btp300/pages/content/index.html Course Web Site – Lecture Notes]
 
* [https://cs.senecac.on.ca/~btp300/pages/timeline.html Course Web Site – Timeline]
 
* [https://cs.senecac.on.ca/~btp300/pages/timeline.html Course Web Site – Timeline]
 +
 +
== Wiki-based Learning ==
 +
 +
=== Purpose ===
 +
 +
Collaboration is a growing trend in today's practice of software development.
 +
You may visit Wikipedia and read about [http://en.wikipedia.org/wiki/Ward_Cunningham Ward Cunningham] and collaboration in [http://en.wikipedia.org/wiki/Extreme_programming software development]. IBM is developing a wiki-based product for [http://www.itworldcanada.com/a/IT-Workplace/16508059-35d0-424f-a3b2-4d5e17840058.html corporate learning]. During this semester, you will use a wiki to learn how to '''collaborate''' with your fellow classmates when you are building up your C++ programming skills in this course. The students will take an active role in creating useful contents. The professor will play the role of an observer and a facilitator.
 +
 +
=== Benefits ===
 +
 +
* You will be better prepared to enter the IT workforce and pursue courses on open source software development such as [http://zenit.senecac.on.ca/wiki/index.php/OSD600_Fall_2008 OSD600] or [http://zenit.senecac.on.ca/wiki/index.php/DPS909_Fall_2008 DPS908].
 +
 +
* Your ''regular'' contributions to the discussions on this wiki will be worth 3% of your final grade. It will be calculated under the categories of Assignments and Lab Assignments in the course outline of BTP400. This means that you should regularly update the ''time line of contributions'' in your personal wiki page. Also clarity of expression and minimal spelling errors are essential. (Hint: You and your classmates can help each other to edit your English writing.)
 +
 +
=== Guidelines of Community Practice ===
 +
 +
The key ingredient in fostering a spirit of collaboration is that everyone is a
 +
CONTRIBUTOR to the learning community. We will respect each other and interact with
 +
each other in a professional way. You will discover your ''artistic potentials'' when you
 +
use your favorite formats and styles in creating wiki pages. As a matter of courtesy,
 +
please ask for comments before you want to make a ''major'' change to a wiki page that is
 +
''shared'' by the learning community.
  
 
== The Project  ==
 
== The Project  ==

Revision as of 15:31, 31 August 2012


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 Software Development 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

Wiki-based Learning

Purpose

Collaboration is a growing trend in today's practice of software development. You may visit Wikipedia and read about Ward Cunningham and collaboration in software development. IBM is developing a wiki-based product for corporate learning. During this semester, you will use a wiki to learn how to collaborate with your fellow classmates when you are building up your C++ programming skills in this course. The students will take an active role in creating useful contents. The professor will play the role of an observer and a facilitator.

Benefits

  • You will be better prepared to enter the IT workforce and pursue courses on open source software development such as OSD600 or DPS908.
  • Your regular contributions to the discussions on this wiki will be worth 3% of your final grade. It will be calculated under the categories of Assignments and Lab Assignments in the course outline of BTP400. This means that you should regularly update the time line of contributions in your personal wiki page. Also clarity of expression and minimal spelling errors are essential. (Hint: You and your classmates can help each other to edit your English writing.)

Guidelines of Community Practice

The key ingredient in fostering a spirit of collaboration is that everyone is a CONTRIBUTOR to the learning community. We will respect each other and interact with each other in a professional way. You will discover your artistic potentials when you use your favorite formats and styles in creating wiki pages. As a matter of courtesy, please ask for comments before you want to make a major change to a wiki page that is shared by the learning community.

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.

Evaluation

  • 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)

Resources

Examples and In-Class Notes

Archives

BTP300 Fall 2011

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