CS246 Object-Oriented Software Development
Spring 2019

Course Description

Introduction to object-oriented programming and to tools and techniques for software development. Designing, coding, debugging, testing, and documenting medium-sized programs: reading specifications and designing software to implement them; selecting appropriate data structures and control structures; writing reusable code; reusing existing code; basic performance issues; debuggers; test suites.

Course Objectives

Course Personnel

Instructor's Name Office Location Contact Office Hours
Nomair Naeem DC 3111 nanaeem@uwaterloo.ca By appointment, Mondays 9:30am-10:30am, or Tuesdays 2:45pm-3:30pm
Caroline Kierstead MC 4009 ctkierst@uwaterloo.ca By appointment, or on Fridays 2:00-4:30pm (on alternate weeks starting May17, or whenever my meeting is cancelled, they'll start at 1:30pm), or whenever my door is open.

ISA Office Location Contact Office Hours
Luke P. J. Fitzpatrick MC 4065 cs246@uwaterloo.ca Tuesday 9:30-11:30am and Friday 11:30am-2:30pm
Josh Rampersad MC 4065 cs246@uwaterloo.ca Thursday 2:00-3:00pm

ISA (Part Time) Office Location Contact Office Hours
Kris Frasheri MC XXXX cs246@uwaterloo.ca N/A

ISC Office Location Contact
Olga Zorin MC 4005 ozorin@uwaterloo.ca

Lecture and Tutorial Schedule

Lecture Section Time/Date Building/Room Instructor Name
LEC 001 11:30am-12:50pm TTh MC 4020 Nomair Naeem
LEC 002 1:00pm-2:20pm TTh MC 4020 Nomair Naeem
LEC 003 2:30pm-3:50am TTh MC 4021 Caroline Kierstead

Tutorial Section Time/Date Building/Room Leading ISA/IA
TUT 101 1:30pm-2:20pm W MC 4060 Josh
TUT 102 4:30pm-5:20pm W MC 4060 Marko
TUT 103 2:30pm-3:20pm W MC 4060 Marko
TUT 104 8:30am-9:20am W MC 4063 Josh
TUT 105 12:30pm-1:20pm W MC 4060 Josh

Resources

Course Topics

All timings are approximate.

Student Assessment

Assignments Number Tentative Due Date Marks Totals
0 May 13th 0*
1 Due Date 1: May 17th
Due Date 2: May 24th
5
2 Due Date 1: May 31st
Due Date 2: Jun. 7th
7
3 Due Date 1: Jun. 14th
Due Date 2: Jun. 21st
7
4 Due Date 1: Jul. 5th
Due Date 2: Jul. 12th
9
5 Due Date 1: Jul. 23rd
Due Date 2: Jul. 30th
12
40 40
TestsMidtermJun. 27th (Thurs.), 4:30-6:20pm
M3 1006, MC 1085, MC 4021
20 20
Final TBA
TBA
40 40
100

Note (*): you cannot get credit for assignments 1-5 until you have achieved 100% on assignment 0.

Note: The weight of the final exam will be increased by 1/3 of the value of the marks lost on the midterm. This provides a "second chance" to earn up to one third of those lost marks back, with good final exam performance. This is the only adjustment to grades that will be made in the middle of the term. All other grade adjustments (if any) will be applied at the discretion of the instructors, at the end of the term.

Note: Most assignments are expected to be due on Friday 5:00pm. However, the listed due dates are tentative, and are subject to change.

Note: The final assignment is a project to be done in groups of at most three. You may do the project in pairs or individually, but you will be expected to produce the same output as a group of three. Be sure to work with people whom you trust; we will not arbitrate disagreements. Part of the evaluation of your project will consist of a live demo in front of a TA. This is mandatory.

Tests

Both the midterm test and the final exam are closed book.

A missed test/exam receives a mark of 0, unless there is a documented reason. If a documented reason is provided for missing the midterm, its weight is applied to the final exam. If a documented reason is provided for missing the final exam, a grade of INC MIGHT be given, and the final exam must be written at the end of the next term the course is offered. A copy of the documented reason must be given to and approved by the instructor.

Assignments

All assignments must be done individually, unless the assignment is explicitly designated as a group assignment. All members of a group receive the same grade (no exceptions). The instructors/staff do not arbitrate group disputes; group members must handle any and all problems. A group assignment may be done individually, but it must be understood that the amount of work is significantly greater and no extra marks are given for this additional work.

Assignment Due Date 1 solutions cannot be discussed until AFTER Assignment Due Date 2. Doing so constitutes an academic integrity offence.

Note: Marmoset is not a compiler! Do not submit C++ code to Marmoset, without first attempting to compile it yourself. For each problem on Marmoset where the deliverable is C++ code, if you have three or more submissions marked "Did not compile", a mark will permanently be deducted from your score on that problem.

Assignment Submissions

Assignments must be submitted using the Marmoset Submission and Testing Server.

The release test for a problem gives you the result of running your program on one basic test case (usually a case that appears in the assignment specification). The remaining test cases are secret tests, the results of which are revealed after the assignment is due. So be sure to test your code thoroughly, so that you pass as many of our secret tests as possible.

Lates

Marking

Remarking Policy

Note: The entire assignment or test is examined when remarking; therefore, the grade could decrease.

Course Communication

The primary form of communication of information outside of lectures will be through Piazza. It is thus very important that you read it daily! Since it is very common for the number of posts to get very large, very quickly, we have posted some guidelines to using Piazza in Piazza to help make everybody's lives easier. Please make sure that you read the guidelines before you post.


Mental Health Resources

Mental Health: If you or anyone you know experiences any academic stress, difficult life events, or feelings like anxiety or depression, we strongly encourage you to seek support.

On-campus Resources

Off-campus Resources

Diversity: It is our intent that students from all diverse backgrounds and perspectives be well served by this course, and that students’ learning needs be addressed both in and out of class. We recognize the immense value of the diversity in identities, perspectives, and contributions that students bring, and the benefit it has on our educational environment. Your suggestions are encouraged and appreciated. Please let us know ways to improve the effectiveness of the course for you personally or for other students or student groups. In particular:

Academic Integrity

In order to maintain a culture of academic integrity, members of the University of Waterloo community are expected to promote honesty, trust, fairness, respect and responsibility. Check the Office of Academic Integrity's website for more information.

All members of the UW community are expected to hold to the highest standard of academic integrity in their studies, teaching, and research. This site explains why academic integrity is important and how students can avoid academic misconduct. It also identifies resources available on campus for students and faculty to help achieve academic integrity in — and out — of the classroom.

MOSS(Measure of Software Similarities) is used in this course as a means of comparing students' assignments to ensure academic integrity.

Excessive collaboration defined

Students in CS 246 are permitted to discuss the assignments with each other in generalities only. Students may not look at each other's code or show their code to others. Any discussions about assignments must take place away from a computer, and without any written (or typed) record of the conversation. The discussion must be limited to what an assignment requires not how to do it. Similarities between students' code submissions, if they lie beyond what the instructors feel may be reasonably explained by chance, will be taken as evidence of excessive collaboration and will be forwarded to the Math Faculty integrity officer.

Special Note on test cases: Sharing test cases, created as part of an assignment submission, is not permitted even after the due date for these test cases has passed.

Please note that if you gain access to someone else's solution to a problem, you have already committed an offence, even if you never actually use that solution. Please protect your work from being seen by others, and please do not put your friends in difficult situations by asking to see their code. Any evidence that you had knowledge of someone else's solution while writing your own solution will be reported as an offence.

Publishing your code online

Posting assignment, project, midterm, and final exam solutions in publicly-accessible locations is not permitted in this course. For more information, and for information on alternatives to posting publicly, see here.

Intellectual Property

Students should be aware that this course contains the intellectual property of their instructor, TA, and/or the University of Waterloo. Intellectual property includes items such as:
  • Lecture content, spoken and written (and any audio/video recording thereof);
  • Lecture handouts, presentations, and other materials prepared for the course (e.g., PowerPoint slides);
  • Questions or solution sets from various types of assessments (e.g., assignments, quizzes, tests, final exams); and
  • Work protected by copyright (e.g., any work authored by the instructor or TA or used by the instructor or TA with permission of the copyright owner).

Course materials and the intellectual property contained therein, are used to enhance a student's educational experience. However, sharing this intellectual property without the intellectual property owner's permission is a violation of intellectual property rights. For this reason, it is necessary to ask the instructor, TA and/or the University of Waterloo for permission before uploading and sharing the intellectual property of others online (e.g., to an online repository).

Permission from an instructor, TA or the University is also necessary before sharing the intellectual property of others from completed courses with students taking the same/similar courses in subsequent terms/years. In many cases, instructors might be happy to allow distribution of certain materials. However, doing so without expressed permission is considered a violation of intellectual property rights.

Please alert the instructor if you become aware of intellectual property belonging to others (past or present) circulating, either through the student body or online. The intellectual property rights owner deserves to know (and may have already given their consent).

Grievance

A student who believes that a decision affecting some aspect of his/her university life has been unfair or unreasonable may have grounds for initiating a grievance. Read Policy 70 — Student Petitions and Grievances, Section 4. When in doubt please be certain to contact the department's administrative assistant who will provide further assistance.

Discipline

A student is expected to know what constitutes academic integrity, to avoid committing academic offenses, and to take responsibility for his/her actions. A student who is unsure whether an action constitutes an offense, or who needs help in learning how to avoid offenses (e.g., plagiarism, cheating) or about "rules" for group work/collaboration should seek guidance from the course professor, academic advisor, or the Undergraduate Associate Dean. For information on categories of offenses and types of penalties, students should refer to Policy 71 — Student Discipline. For typical penalties, check the Guidelines for the Assessment of Penalties.

Avoiding Academic Offenses

Most students are unaware of the line between acceptable and unacceptable academic behaviour, especially when discussing assignments with classmates and using the work of other students. For information on commonly misunderstood academic offenses and how to avoid them, students should refer to the Faculty of Mathematics Cheating and Student Academic Discipline Policy.

Appeals

A decision made or a penalty imposed under Policy 70, Student Petitions and Grievances (other than a petition) or Policy 71, Student Discipline may be appealed if there is a ground. A student who believes he/she has a ground for an appeal should refer to Policy 72 — Student Appeals.

Note for students with disabilities

The AccessAbility Services Office (AAS), located in Needles Hall, Room 1401, collaborates with all academic departments to arrange appropriate accommodations for students with disabilities without compromising the academic integrity of the curriculum. If you require academic accommodations to lessen the impact of your disability, please register with the AAS at the beginning of each academic term.