CSE 484 / CSE M 584: Computer Security

CSE Home

About Us

Search

Contact Info

Course home  Administrivia  Schedule  Homework  Discussion boards  Labs

Class Mailing List and Archive and Policies Sending Mail The class mailing list is cse484a_sp12@uw.edu. We will use this list to make official class-related announcements. We will assume that all students in the class will be on this list, and furthermore, we will assume that everybody will be checking their mail regularly (at least once a day, during the week). It is conceivable that we will use the mailing list to announce homework assignments, or to make changes/fixes to project assignments. For general discussions, please use one of these forums: https://catalyst.uw.edu/gopost/board/kohno/27219/ (assignments) and https://catalyst.uw.edu/gopost/board/kohno/27218/ (security context). Subscribing If you're enrolled in CSE 484, then your @u.washington.edu email address should be automatically subscribed. If you just enrolled, you may have to wait a day or two before the system is automatically updated. If you are enrolled in CSE M 584, you may need to subscribe yourself. You can verify your enrollment or join the mailing list by going to this page: 484 mailing list. Archives All email sent to the class list is archived here.   Policies (Many of these policies are taken verbatim from previous instances of this and other UW CSE courses.) Late Policy: Please pay careful attention to the due dates of the assignments. For most assignments, if you hand in the assignment late, we will take off 20% for each day it is late. When computing the number of days late, we will round up; so an assignment turned in 25 hours late will be downgraded 40%. as grades. Please note, however, that some assignments cannot be turned in late; we will clearly specify when this is the case. We will not consider granting Incompletes Reasonableness: The "Reasonable Person Principle" applies throughout this course. This principle simply states that a reasonable request made in a reasonable fashion shall be reasonably handled by reasonable persons. Let's all be "reasonable people" working on the same team to make this a great learning experience. Cheating vs. Collaboration: Collaboration is a very good thing. On the other hand, cheating is considered a very serious offense. Please don't do it! Concern about cheating creates an unpleasant environment for everyone. If you cheat, you risk losing your position as a student in the department and the college. The department's policy on cheating is to report any cases to the college cheating committee. What follows afterwards is not fun for anyone. So how do you draw the line between collaboration and cheating? Here's a reasonable set of ground rules. Failure to understand and follow these rules will constitute cheating, and will be dealt with as per university guidelines. The Gilligan's Island Rule: This rule says that you are free to meet with fellow student(s) and discuss assignments with them. Writing on a board or shared piece of paper is acceptable during the meeting; however, you should not take any written (electronic or otherwise) record away from the meeting. This applies when the assignment is supposed to be an individual effort or whenever two teams discuss common problems they are each encountering (inter-group collaboration). After the meeting, engage in a half hour of mind-numbing activity (like watching an episode of Gilligan's Island), before starting to work on the assignment. This will assure that you are able to reconstruct what you learned from the meeting, by yourself, using your own brain. The Freedom of Information Rule: To assure that all collaboration is on the level, you must always write the name(s) of your collaborators on your assignment. These names should be listed in a prominent location at the top of the first page of your assignment.

	Computer Science & Engineering University of Washington Box 352350 Seattle, WA  98195-2350 (206) 543-1695 voice, (206) 543-2969 FAX [comments to Tadayoshi Kohno]