CS 372H: Policies and Grading


Unless stated otherwise, all exams above will be closed book. The midterm and the final exam will cover material from class meetings, labs, readings, and any other assigned material (for example, homeworks).


Your final grade will be determined by the following weights:

Class participation and preparedness

Some (not all) of our class meetings will be discussion days: led discussions of an assigned research paper or other reading. These meetings will be led by the instructor. They will have the following expectations and format:

Turn-in policy, slack days, lateness, etc.

The course permits two kinds of limited slacking:

  1. You can skip at most ONE discussion day during the semester, with no ill effects on the participation and preparedness part of your grade. You do not have to email us to let us know when you are exercising this option. Missed classes beyond one (or showing up without having done the assigned reading) will adversely affect the participation and preparedness part of your grade. However, the effect will be limited to that portion of your grade only (though there may be side-effects; for instance, the missed material might appear on an exam).
  2. Each project team gets a total of 72 late hours to use throughout the semester. Late hours cannot be used on labs 1 and 2, which will be done individually. Beyond this requirement, your team decides how to divide the 72 hours among the various lab assignments. After your late hours are exhausted, each additional day late will incur a full letter grade penalty. The granularity of these hours is just that: hours. Labs that are late by, say, 10 minutes count as having exhausted a late hour.

Exemptions of the lateness rules will be allowed in three cases:

  1. Illness, which has to be documented by a doctor and approved by the university.
  2. Death in the immediate family.
  3. Accommodation for students with disabilities as prescribed by the university.
No extensions will be given for any other reason.

You are required to turn in every lab assignment, late or otherwise. If your lateness results in your getting 0 points on the assignment, you will get a D for that assignment. If, by the end of the semester, you have not turned in all of the assignments, then you will receive an F on the entire lab portion of your final grade. (That is, failing to turn in any one lab assignment will cause 35% of your grade to be an F.)

Code of conduct

Please read the UTCS Code of Conduct. It outlines what is expected of you and what you can expect from classes in the CS department.

Collaboration, source material, and cheating

You can discuss the labs in general terms only with your classmates. Below are a few notes on this policy. If you have a project partner, then you should read the "you" below as referring to your team, since of course you should be discussing code with your project partner (but no one else): Below is more detail. You are responsible for knowing these policies.


You must do the work on your own. What does "on your own" mean? Here are some guidelines to keep you on the right side of the line:
  1. It is never okay to look at the written work of another person or show another person (other than the instructor or TA) your written work until after all grading on an assignment is completed. This includes looking at paper print-outs, sketching solutions on a white board or napkin, or looking at a screen to help debugging. Obviously, copying other people's code or solution sets is prohibited.
  2. Second, after discussing a problem with another student (or the course staff!), go do something else (read a book, watch a movie) for half an hour before going back to work on the assignment. If you can't remember what the person said after a half hour, you didn't really understand it.
  3. Third, everyone in the class is expected to take appropriate measures for protecting their work. For example, you should protect your files and printouts from unauthorized access.

Source material

You are welcome to use existing public libraries in your programming assignments (such as public classes for queues, trees, etc.) You may also look at operating systems code for public domain software such as Linux. Such activities qualify under approved collaboration practices, and you are welcome to take advantage of them. Consistent with normal academic practice, you should cite and give credit to any source that gave you code or an idea.

What you may not do is look at any course material relating to any project or lab similar to this course's assignments. For example, you may not look at the work done by a student in past years' courses, and you may not look at similar course projects at other universities. If you are unsure about whether a particular source of external information is permitted, contact the instructor before looking at it.


Note that the above guidelines are necessarily generalizations and cannot account for all circumstances. Intellectual dishonesty can end your career, and it is your responsibility to stay on the right side of the line. If you are not sure about something, ask.

Students who violate University rules on scholastic dishonesty are subject to disciplinary penalties, including the possibility of failure in the course and/or dismissal from the University. Because such dishonesty harms the individual, all students, and the integrity of the University, policies on scholastic dishonesty will be strictly enforced.

Accommodations for students with disabilities

The University of Texas at Austin provides upon request appropriate academic accommodations for qualified students with disabilities. For more information, contact the Office of the Dean of Students at 512-471-6259, 512-471-6441 TTY.

Last updated: Wed Feb 01 16:24:57 -0600 2012 [validate xhtml]