Preparation & Submission

1. All programming assignments submitted are to include a printed listing of all source code along with a printed listing of the output from the program and an executable file.
2. Unless test data was provided for the assignment a copy of the test data used should be included in the submission.
3. The source code, output and test data listings should be stapled together with an additional page containing the course number, assignment number, your name and student number attached at the front.
4. All submissions (hardcopy and email) must be received by the assignment due date and time or it will be considered late and will be assigned the late penalty.

Failure to follow these guidelines may result in a lower grade for the assignment.

Late Assignments

1. Assignments will be accepted as late for one week after the original due date the date as specified in class with a penalty of 25%.
2. It is the date of submission (not the date that the work was completed) that is considered with respect to lateness.
3. In the case of sickness, bereavement or other special circumstances and upon the receipt of suitable documentary evidence, the instructor may grant an appropriate extension for the assignment.
4. Only in the event of the unavailability of computing resources (i.e. hardware failure in the lab) for a period of 24 hours or more will an extension of the due date be granted. Extensions will not be granted simply because the lab was busy.

Programming Standards

1. Each program should begin with a block of comments which give the following information: course number, assignment number, author's name and student number, a brief description of the problem.
2. Each function should begin with a block of comments describing: the purpose of the function and the use of each parameter.
3. Each variable declared should have a comment associated with it describing the purpose of the variable.
4. Statements nested within another statement or function should be indented and indentation should be consistent.
5. Each identifier (constant, variable, function and/or type) in the program should be given a meaningful name.

Program Quality

1. Algorithms should be clearly stated, straightforward and not unduly complicated.
2. The solution should be decomposed into a reasonable number of reasonably sized, logical functions.
3. Variables should be declared as locally as is reasonable for the solution.
4. Although efficiency is a concern (i.e. gross inefficiency is not acceptable), in general clarity of expression of the algorithm should take preference over micro-efficiency.
5. The program should handle all reasonable cases (including user errors) except where simplifying assumptions are given in the assignment specification.

Marking Criteria

1. Correctness of solution
2. Adherence to programming standards
3. Quality of the program
4. Handling of erroneous cases
5. Gross efficiency
6. Quality of test data (when not supplied for assignment)
7. Marks will be deducted for failure to adhere to the guidelines described in this document.

The program grading criteria can be found here.

Plagiarism

1. It is expected that each submission is that of an individual student. Collaboration on an individual assignment is not acceptable.
2. Obtaining assistance from course staff (i.e. instructor and general consultants) is acceptable.
3. General discussions about the purpose of the assignment or general (high-level) approaches to the solution between students in the course is acceptable.
4. Plagiarism will be suspected if two submissions are made which are so similar that a mechanical transformation from one to the other is possible. The same is true if parts (e.g. code segments, functions or modules) of the submission are substantially the same.
5. Plagiarism is a serious offense and will be dealt with according to University regulations. Penalties for proven plagiarism range from 0 for the piece of work in question to suspension from the University.