CS 136: Elementary Algorithm Design and Data Abstraction, Winter 2014

Assignments

Assignments will become available as the course progresses. See calendar for more details.


If Marmoset fails to accept submissions for more than two of the six hours immediately prior to the deadline, or is down at the deadline, a 12-hour extension will be granted. For an extension to be granted, Marmoset must fail to accept submissions; failure or delay in displaying results is not grounds for extension. It is bad practice, and risky, to rely on Marmoset as your primary means of testing. The failure must be due to problem with Marmoset or a widespread network failure; your home connection is your own responsibility.

Marmoset Test System

All assignments must be submitted to the Marmoset Submission and Testing Server. Submissions are tested immediately, and results are available on-line.

Procedures and Purpose

The purpose of assignments is to give you exercise in the concepts and skills discussed in lecture. The point is not to earn marks by any means possible; marks are a consequence of the understanding gained through practice. Please read the section below on Plagiarism, including the linked UW Policies. These apply to every course you will take at UW, and you should be familiar with them.

Assignments must be submitted before 11:59 a.m. on the day they are due, unless otherwise specified in the assignment itself. You may submit as often as you wish, and only your best submission counts.

Extensions will only be granted if Marmoset is down for a significant period of time immediately prior to the submission deadline.

Missed work due to illness

With appropriate, authorized documentation, assignment work may be excused. If a missed assignment is excused, its weight is distributed over the remaining un-excused assignments. In the interest of understanding the course material for future assignments and exams, students who miss work are encouraged to do it, submit it request feedback from the tutors.

CS 136 Plagiarism Policy

All work in CS 136 is to be done individually. The penalty for plagiarism is an assigned mark of zero on the assignment or test and a deduction of 5% from the final course grade, consistent with School of Computer Science and Faculty of Mathematics policy. In addition, a letter detailing the offense is sent to the Associate Dean of Undergraduate Studies, meaning that subsequent offenses will carry more severe penalties, up to suspension or expulsion. To avoid inadvertently incurring this penalty, do not copy work from anyone or anyplace. You are not allowed to discuss assignment question implementations, ideas for a solution or code. Only clarification on what an assignment question is asking is permitted. All work submitted must be your own. If you find yourself stuck, contact the tutor or instructor for help, instead of getting the solution from someone else. When trying to deal with difficulties, do not copy from the book or any Web sources, unless explicitly authorized to do so.

University of Waterloo Academic Integrity Policy

The University of Waterloo Senate Undergraduate Council has also approved the following message outlining University of Waterloo policy on academic integrity and associated policies.

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.

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

AccessAbility Services (formerly the Office for Persons with Disabilities or OPD), located in Needles Hall, Room 1132, 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 OPD at the beginning of each academic term.

Valid XHTML 1.0 Strict Valid CSS!

Last modified on Friday, 11 April 2014, at 12:28 hours.