Assignments

• Assignment #1: PDF. Assigned January 13, 2012. Due January 23, 2012 at 11:59pm.
• Assignment #2: PDF. Assigned January 26, 2012. Due February 6, 2012 at 11:59pm.
• Starter file for question 1: cra.mpl
• Starter file for question 3: newton.mpl
• Assignment #3: PDF. Assigned February 17, 2012. Due February 28, 2012 at 11:59pm.
• Modular GCD algorithm: modularGcd.mpl
• Examples of useful Maple functions: primer.mpl
• Assignment #4: PDF. Assigned March 22, 2012. Updated due date: April 2, 2012 at 11:59pm. Due March 27, 2012 at 11:59pm.
• Polynomial in Maple format for question 1: a4q1.mpl
• Polynomial in Maple format for question 4: a4q4.mpl

Following directions

The penalty for not following directions (i.e. submitting late, no hardcopy or no softcopy when needed, etc.) will be a 20% deduction, which might be applied to individual problems or the whole assignment, depending on the offence.  Please read assignments carefully and follow the instructions.  If in doubt, ask!

Submission Logistics

All assignments are due at the date and time indicated (or 11:59pm on the given date if no time is specified). Assignments must be submitted in two places:

1. Printed solutions to all questions including code should be placed in the pink assignment box on the third floor of MC (near the walkway to DC) in the slot marked for this course.
2. Solutions to programming questions (i.e. code) should additionally be e-mailed to cs487@cs.uwaterloo.ca with a subject containing (at least) "CS 487", the assignment number, and your UW username.
   Maple code should be attached as a single plain-text file with the extension ".mpl". Comments should clearly indicate where the solution to each question or part begins and ends.
   C/C++ code should be submitted as a single tarball, gzipped and with the extension ".tar.gz". (To create such a file, in a Unix or Unix-like environment, descend to the parent directory of that in which your code resides, and then type

   tar cvf outfile.tar codedir/
   gzip outfile.tar

   to collect everything in the codedir directory and put it in the archive outfile.tar.gz which you then send to the course account).
   Sufficient comments should always be included to make the code clear and understandable; at the very least, you must document each function with a brief purpose and a description of the input and output.

Plagiarism Policy

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

"Students are expected to know what constitutes academic integrity, to avoid committing academic offenses, and to take responsibility for their actions. Students who are unsure whether an action constitutes an offense, or who need 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, TA, academic advisor, or the Undergraduate Associate Dean. For information on categories of offenses and types of penalties, students should refer to Policy #71, Student Academic Discipline, http://www.adm.uwaterloo.ca/infosec/Policies/policy71.htm. Students who believe that they have been wrongfully or unjustly penalized have the right to grieve; refer to Policy #70, Student Grievance, http://www.adm.uwaterloo.ca/infosec/Policies/policy70.htm."

All work in CS 487/687 is to be done individually. The penalty for plagiarism is an assigned mark of negative 100 percent of the value of the assignment or test, consistent with School of Computer Science 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. Do not take notes during such discussions, and avoid looking at anyone else's code, on screen or on paper. If you find yourself stuck, contact the teaching assistant or instructor for help.