policies
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
policies [2008/09/09 02:30] – jonathan | policies [2008/09/22 20:52] (current) – jonathan | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Policies ====== | ====== Policies ====== | ||
- | - Grade for a missed Quiz is zero unless | + | - Grade for a missed Quiz is zero unless |
- Projects must be handed in by the deadline. The deadlines are strict. Medical emergencies cannot be taken into account as the deadlines were announced at the beginning of the course long before the hand-in date. Hand in work as is where it could not be completed. Note that you can submit work whenever you like. | - Projects must be handed in by the deadline. The deadlines are strict. Medical emergencies cannot be taken into account as the deadlines were announced at the beginning of the course long before the hand-in date. Hand in work as is where it could not be completed. Note that you can submit work whenever you like. | ||
-Re-evaluation of course work: You may resubmit a piece of work for re-evaluation within 14 days of the return of the work to the class. You may submit the request to the course director by leaving it at the Computer Science office, CSEB 1003, or give it to your instructor in class. For re-evaluation resubmit the work together with a note explaining precisely what parts have been under or over evaluated with supporting rationale. It is insufficient to just ask for a work to be re-evaluated. You should also read any comments and solutions that are made available before submitting your work for reevaluation. The entire work will be re-evaluated, | -Re-evaluation of course work: You may resubmit a piece of work for re-evaluation within 14 days of the return of the work to the class. You may submit the request to the course director by leaving it at the Computer Science office, CSEB 1003, or give it to your instructor in class. For re-evaluation resubmit the work together with a note explaining precisely what parts have been under or over evaluated with supporting rationale. It is insufficient to just ask for a work to be re-evaluated. You should also read any comments and solutions that are made available before submitting your work for reevaluation. The entire work will be re-evaluated, | ||
Line 13: | Line 13: | ||
===== Reports ===== | ===== Reports ===== | ||
- | [Parts taken from 3311 web pages] | + | Parts of the material below are taken from the CSE3311 |
Reports must look professional. Use single line spacing and normal size type with reasonable amount of white space separating different items in the report; for example, diagrams, lists, paragraphs, etc. Reports in computer science are technical in nature, consequently they are partitioned into sections, sub-sections, | Reports must look professional. Use single line spacing and normal size type with reasonable amount of white space separating different items in the report; for example, diagrams, lists, paragraphs, etc. Reports in computer science are technical in nature, consequently they are partitioned into sections, sub-sections, |
policies.1220927443.txt.gz · Last modified: 2008/09/09 02:30 by jonathan