CSE logo University of Washington Computer Science & Engineering
 CSE 373: Data Structures & Algorithms, Autumn 2010
  CSE Home 

Assignments
 Turn-in link
 Homeworks
Administrative
 Home
 Annoucement ArchiveCSE only
 Message Board
 Anonymous Feedback
Lectures
 Calendar & Slides
 Office Hours Calendar
Exams
 Midterm #1
 Midterm #2
 Final Exam
Handouts
 First Day Handout
 First Day Slides
Policies
 General Guidelines
 Grading Policies
 Programming Guidelines
 Written HW Guidelines
Computing
 CSE 143 Info on Java & Eclipse
 Java
 Eclipse IDE for Java
 Programming Lab Info
 Java Links from CSE 143
   

Collaboration Policies

Unless otherwise stated, you are to complete assignments individually. You may discuss the assignment in general terms (see description of Gilliganís Island rule below), but the code you write must be your own. You are encouraged to discuss ideas, approaches, concepts, bugs, etc., in English, but you may not show or give your code to anyone except this courseís TAs and instructor. You are not allowed to write code with another student on an assignment or to show another student your solution to an assignment. Although the work you turn in should be your own, we do encourage you to discuss material with other students provided:
  1. You spend at least 30 minutes on each and every problem (or programming assignment) alone, before discussing it with others,
  2. Cooperation is limited to group discussion and brainstorming. No written or electronic material may be exchanged or leave the brainstorming session,
  3. You write up each and every problem in your own writing, using your own words, and understand the solution fully (similarly you must write code on your own),
  4. You identify each person that you collaborated with at the top of your written homework or in your README file.

One guidline commonly used in the Computer Science department is the Gilliganís Island Rule:
  1. You may discuss problems with your classmates to your heart's content.
  2. After you have solved a problem, discard all written notes about the solution.
  3. Go watch TV for a Ĺ hour (or more). Preferably Gilligan's Island.
  4. Then write your solution.

Copying someone else's homework is cheating (see below), as is copying the homework from another source (the web, other classes, or previous offerings of this class, etc.).


Cheating

Cheating is a very serious offense. If you are caught cheating, you can expect a failing grade and initiation of a cheating case in the University system. Cheating is an insult to the instructor, to the department, and most importantly, to you. If you feel that you are having a problem with the material, or don't have time to finish an assignment, or have any number of other reasons to cheat, then talk with the instructor. Copying others' work is not the solution.

To avoid creating situations where copying can arise, never e-mail or post your solution files. You can post general questions about interpretation and tools but limit your comments to these categories. If in doubt about what might constitute cheating, send the instructor email describing the situation. For more details see the Academic Misconduct web page.


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