This third course in the TEL (Technology Enhanced Learning) Series on Software Development describes in detail the more common concepts involved in object-oriented programming, using the 2017 standard of the C++ language.  It elaborates on the material introduced in OOP244, covers the Standard Template Library that supports the core C++ language, and describes the components needed to use this library effectively. 

The complete URL of the home page of the subject web site is

The subject web site contains all of the subject matter.  You can obtain the most recent edition of those notes at the Seneca@York Bookstore

  • Szalwinski, Chris. "Object-Oriented Software Development Using C++17" Seneca College.

This course is comprehensive.  You should be able to master all of the material if you:

  • attend the lectures,
  • complete the in-class practice problems,
  • complete the workshop problems, which implement the major concepts introduced in the notes, and
  • complete the assignments, which integrate the major concepts covered in the course.

Keeping up with the lectures, workshops and assignments is crucial to success. 

If you have any suggestions on how this site might be improved, feel free to let your instructor know.  Many student suggestions have been incorporated since its initial publication.


Content

Notes

The subject material is organized into eight modules:

  • Introduction
  • Types
  • Class Relationships
  • Logic
  • Memory Model
  • Standard Template Library
  • Performance
  • Related Topics

Each chapter includes an exercise section.  The exercise section lists any related workshop problem and suggested exercises.  If you need another view of the material, try one of the links on the tutorials page off the resources page. 

Workshops

Each workshop problem applies the concepts introduced in the weekly readings.  For assistance in solving a workshop problem consult the resources section and the forum on the learning management system.

The forum operates asynchronously.  You may post questions or comments at any time. 

Discussion keeps the board interesting and maximizes everyone's learning. 

Any items posted to the discussion board should not go outside, in order to protect the student's privacy.


ACADEMIC POLICY

The Academic Policy of Seneca College applies.  Cheating, plagiarism and breach of copyright are serious offenses under this Policy.  The official version of the Cheating and Plagiarism Section is here.

Cheating

Cheating during a test or exam is construed as talking, peeking at another student?s paper or any other clandestine method of transmitting information.

Plagiarism

Plagiarism is using the work of others without citing it; that is, holding the work of others out as your own work.

Do not submit an assignment that contains material copied from another student, a website, a textbook or any other published source without identifying the material that is not your own.  Rewording someone else's submission or changing the field names in their program and presenting the result as your own may be construed as plagiarism: you are still copying the solution and submitting it as your own.  Plagiarism is not excusable by trivial differences in the code or the wording.

Assignments unless otherwise stated are individual work.  If your instructor notices that you have copied parts of your submission from another student or external source without citation, your instructor may charge you with plagiarism. 

How Not To Plagiarize

Studying and improving others? code is a good way to learn.  You may imitate and dissect the sample code in the subject web site and the printed subject notes.  You may use this code in your submissions, including your assignments.  You need not cite the authours of these two sources.  You may copy the workshop code of your peers provided that you cite them as the authours.  All other code should be entirely your own.

When working with others:

  • If you are the helper, set aside your notes, printouts and similar materials.  Study your peer's screen or printout and work with them on their problem using their approach.  Help them debug their code.  Do not show them how you did it. 
  • If you are the person being helped, try to understand the problem.  Don?t just ask for the answer or look at your peer's solution.  Remember, you will need a good level of understanding to do well on the exam.

Breach of Copyright

If you photocopy a textbook without the copyright holder's permission, you violate copyright law. 







  Designed by Chris Szalwinski   Copying From This Site   
Logo
Creative Commons License