CS 145: Designing Functional Programs (Advanced Version)

Assignments

Assignment questions will be posted at the link below. They will not be due each week on the same day, as is common in the other first-year CS courses and the first-year Math courses. Instead, each assignment question will be "released" when students are ready to tackle it (or maybe slightly earlier), with an individual due date between five and ten days later.

Link to index of assignment questions. You must be a registered student to access the assignment questions. Please do not redistribute course materials in any fashion.

Procedures and Purpose

Assignment questions are the main way to reinforce and deepen your understanding of the concepts and skills discussed in lecture. Completing them is a vital part of the learning process.

The marks and, more importantly, marker comments on your assignments serve a diagnostic purpose, allowing you to correct weaknesses you may not have perceived. Completing unfinished or incorrectly-done questions is also important.

Since your final grade in the course is assessment, not diagnosis, and assignments are part of the learning process, it would be rational to leave assignments out of the computation of the final grade. However, too many students would not do the assignments and thus weaken their understanding significantly, probably to the point of endangering their credit. So it is customary to make assignments worth a modest fraction of the final grade.

The assignments for Fall 2020 will altogether be worth 60%. Each question will be weighted equally unless otherwise specified in the question itself.

Please keep in mind that 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. UW Policies apply to every course you will take at UW, and you should be familiar with them. Assignments must be completed individually unless the assignment text explicitly says that collaboration is possible.

Assignment questions must be completed before 10:00pm on the due date, unless otherwise specified in the question itself. You will submit program files electronically to the Marmoset system, which runs tests on your code and informs you of the results fairly rapidly. Late submissions are possible until the last day of lecture, but earn half credit; consequently, you should aim to finish early, to allow for unexpected delays. In particular, the response time of the Marmoset server may become longer if it is heavily loaded, as tends to happen close to deadlines (the system is also used for CS 136 and CS 241). There will be no extensions granted due to server delays.

Some assignments have questions that do not involve code (e.g. proofs). You will submit these as text files to Marmoset, but no tests will be involved. These will be marked by the instructor and the ISA. Once the marking is complete, marked-up files containing comments will be available on markus.

Your assignment submissions should conform to the guidelines laid out in the style guide for assignments. Submission instructions are on the Marmoset page.

Solutions to some assignment questions may be available on this web page, or may be discussed briefly in tutorials.

 

Plagiarism Policy

All work for credit in CS 145 is to be done individually, with the exception of certain assignment questions which may allow a restricted form of collaboration (and will say so explicitly). MOSS (Measure of Software Similarities) is used in this course as a means of comparing students' assignments to ensure academic integrity. The standard 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, you should discuss assignment issues with other students only in a very broad and high-level fashion, and preferably not at all. Do not take notes during such discussions, and avoid looking at anyone else's code, on screen or on paper, or showing your code to others. If you find yourself stuck, contact the instructor or teaching assistants for help, instead of getting the solution from someone else. When trying to deal with difficulties, do not consult books other than the textbooks and do not consult any Web sources, unless explicitly authorized to do so.

 

Senate Undergraduate Council has asked us to post the following paragraphs:

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.

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.

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. When misconduct has been found to have occurred, disciplinary penalties will be imposed under Policy 71 - Student Discipline. For information on categories of offenses and types of penalties, students should refer to Policy 71 - Student Discipline.

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 student may appeal the finding and/or penalty in a decision made under Policy 70 - Student Petitions and Grievances (other than regarding a petition) or Policy 71 - Student Discipline if a ground for an appeal can be established. Read Policy 72 - Student Appeals.

 

Last modified on Tuesday, 08 September 2020, at 14:40 hours.