This document was adapted from DMS Policies, and confirmed at the department meeting on 9/2005.
1. Incomplete Grade
Incomplete (I) will only be given in Computer Science courses in cases where the student has completed the majority (normally all but the last three weeks) of a course with a grade of C or better, but for personal reasons beyond his/her control has been unable to complete the course during the regular term. Negligence or indifference are not acceptable reasons for the granting of an incomplete grade. (Note: this is essentially the old University policy.)
2. Late Withdrawals
A withdrawal after the deadline (currently 9 weeks into the semester) from a CS course will normally be granted only in cases where the student is performing satisfactorily (i.e., C or better) in a course, but has exceptional reasons, beyond his/her control, for being unable to complete the course. These exceptional reasons should be detailed in writing to the instructor, department head and dean.
Note: exceptions to policies 1 and 2 can be made by individual instructors, but should be made only in truly exceptional circumstances.
3. Individual Study Courses
Courses which are regularly scheduled offerings are not generally offered by individual study (i.e., by X97 courses) Exceptions are sometimes made in situations where a lack of a single course prevents a student from graduating.
4. No Early Final Examinations
Final examinations for CS courses shall not be held earlier than the date and time published in the official term schedule. Normally, a student will not be allowed to take a final exam early. Exceptions can be made by individual instructors, but should only be allowed in exceptional circumstances and in a manner which doesn't endanger the security of the exam.
5. Retention of Final Exams
The originals of all final examinations shall be retained by the instructor for at least one year. Students may be allowed to copy their exams.
6. Course Information Sheets
Every instructor of a CS course shall provide each student in that class with a course information sheet (either electronic or in print) which outlines how grades will be calculated (University policy). This information will also inform students of the final exam time as well as the Department's policy on incomplete grades and late withdrawals.
Computer Science courses may not be audited.
8. Announcement of Graduate Exams and Project Defenses
All qualifying exams, comprehensive exams and project defenses should be announced to the entire Department several days prior to the event.
9. Archiving of Graduate Projects and Theses
A final copy of every graduate project and thesis is to be delivered to the Department Head prior to the awarding of a degree. Such projects and theses are to be archived within the Department until the end of time.
10. Interdisciplinary Graduate Programs
All interdisciplinary graduate applicants must be reviewed by the CS
graduate committee if computer science related words (e.g. computer science, software
engineering) are used in the program title OR any CS assistantships are
11. Two-term Limit on Department Head
No individual shall serve more than two consecutive two-year terms as Department Head.
12. Peer Review of Teaching
All new CS faculty members are given a Peer Review of Teaching during their first year with UAF. They are also reviewed prior to standing for tenure. Additional reviews may be scheduled. In particular, a faculty member or the Department head may request a review at any time. These reviews include evaluation of written classroom materials as well as classroom visitations. More details concerning the review are contained in the departmental document, "A Proposal for Peer Review of Teaching" (which should be examined for necessary modifications in the near future).
13. Electronic Communication
The running of the Department depends on communication via e-mail. All faculty members should check their e-mail at least once a day.