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:22] – 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, | ||
+ | |||
Line 9: | Line 10: | ||
For more information on Academic Dishonesty, click [[http:// | For more information on Academic Dishonesty, click [[http:// | ||
+ | |||
+ | ===== Reports ===== | ||
+ | |||
+ | Parts of the material below are taken from the CSE3311 web page on Reports. | ||
+ | |||
+ | 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, | ||
+ | |||
+ | A report is not a puzzle to be solved by the reader. As the designer/ | ||
+ | |||
+ | A copy of the instructor specification is not needed. I already have a copy. For readers of your reports they are uninteresting. Instead summarize, in your introduction, | ||
+ | |||
+ | Do not use point format, except for the occasional list, or unless explicitly asked for. Use correct, grammatical sentences and paragraphs. Word processors have spell checkers. There is a stand alone program, spell, on Prism. Use them. | ||
+ | |||
+ | Judicious use of external sources of material makes for better reports. In your reports be sure to cite the source of any material that you did not create yourself (no citation implicitly implies the work is yours). All information taken from external sources (everything which is not your own work) must be clearly indicated (verbatim items are quoted) and correctly referenced. If you cite references, there should be a reference list at the end of the report. | ||
+ | |||
+ | Even in the "real world" you are expected to cite where and how you obtained the answer so those people needing the report know how much trust to place in it. | ||
+ | |||
+ | Familiarize yourself with the rules and regulations regarding plagiarism. Be sure to read the section " | ||
+ | |||
+ |
policies.1220926935.txt.gz · Last modified: 2008/09/09 02:22 by jonathan