BTP300

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

• BTP300

External Links

• Course Web Site – Lecture Notes
• Course Web Site – Timeline

Wiki-based Learning

Purpose

Collaboration is a growing trend in today's practice of software development. You may visit Wikipedia to read about Ward Cunningham and collaboration in agile software development. IBM has developed 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.

• You are expected to use this wiki when you start working on the course project as a team. In order to develop professional presentation skills, please pay attention to clarity of expression and spelling errors.

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.

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

• How To edit Wiki pages
• How To edit Wiki Cheatsheet
• Subversion (SVN)
• Download Page of TortoiseSVN
• TortoiseSVN Documentation
• SVN book at red-bean.com or downloadthe PDF from here.
• IRC Tutorial
• AnkhSVN - Free Visual Studio SVN Integration Alternative To VisualSVN

Archives

BTP300 Fall 2011