University of Washington <br>
CSE 326, Data Structures <br>
Course Organization <br>

Winter 2001 <br>
Donald Chinn <br>
<br>
<b>Instructor:</b>
<br>Donald Chinn
<br>Sieg 226C, (206) 616-2405
<br>dci@cs.washington.edu
<br>Office hours:
<br>Tu 11:30am-1:00pm, W 2:30-4:00pm.
<br>Also, for a half hour after each lecture (MF), or by appointment.
<br>

<b>TA:</b>
<br>Jeremy Baer
<br>Sieg 226B
<br>jbaer@cs.washington.edu
<br>Office hours:
<br>Tu 2:00-3:00pm
<br>W 12:30-1:30pm
<br>


<b>Class Time and Place:</b> MWF 1:30-2:20pm, EE1 037
<br>
<b>Sections:</b>
<br>AA4  Th 1:30-2:20pm, Lowe 117
<br>AB4  Th 2:30-3:20pm, MEB 237
<br>
<br>

<b>Prerequisites:</b> CSE 143 and 321 (Discrete Math).
<br>

<b>Text:</b> <i>Data Structures & Algorithm Analysis in C++</i>,
Second edition, Weiss, Addison-Wesley, 1999.
<br>

<b>Reading Assignments:</b> Keep up.  Your ability to grasp the
material and get the most out of lectures and section will depend
largely on how much preparation you do before class.  This course will
cover most of Chapters 1 through 9 and possibly some material from the
later chapters in the book.
<br>

<b>Grading:</b> There will be written homework assignments (30%),
programming assignments (30%), a midterm exam (15%), and a final
exam (25%).
<br>

<b>Collaboration on Homework and Labs:</b> In this class, homework and
programming assignments are designed to reinforce learning and are an
important part of the learning process.  I know there are many
situations where collaborative solution to problems is an effective
aid to learning.  I encourage you to work with your classmates if you
find that helpful.  Some guidelines are necessary, however.  Here are
mine (collectively, these are called the <i>Gilligan's Island</i> rule):
<br>
+ You may discuss problems with your classmates to your heart's content.
<br>
+ After you have solved a problem, discard all written notes about the
solution.
<br>
+ Go watch TV for an hour (for programming assignments, 15 minutes).
Preferably <i>Gilligan's Island</i>.
<br>
+ Then write your solution.  (If you can't write your solution at this
point, you didn't really understand it.)
<br>
<br>
In addition, for each problem, you are expected to acknowledge those
individuals with whom you discussed the problem (by writing something
like "I discussed this problem with XXX").  Whether you collaborate
or not, what you turn in is expected to be your original work.
<br>
<br>
I think the spirit and intent of the <i>Gilligan's Island</i> rule is
pretty clear, but in case it isn't, here are some examples of
unethical behavior:
<br>
- Copying someone else's homework assignment answer.
<br>
- Discussing the problem with others without discarding all written
notes.
<br>
- Discussing the problem with others and then not waiting at least an
hour after your discussion before starting to write down your answers.
<br>
- Cutting and pasting code from someone else's lab assignment.
<br>
- Having someone write code for you in the programming assignment.
<br>
<br>
On the other hand, here are some acceptable ways of completing
your assignments:
<br>
+ Working entirely alone on your assignments.
<br>
+ Following the <i>Gilligan's Island</i> rule above.
<br>
+ Having someone look at your code to help you find a syntax error
or to find out why your program keeps printing a stream of
unintended 0's in your output.
<br>
+ Explaining to someone else how you have organized your code, and
discussing whether it's a good organization.  Then following the
<i>Gilligan's Island</i> rule above.

<br>
<br>
<b>Cheating:</b> Cheating, either on an exam or in the abuse of the
<i>Gilligan's Island</i> rule, will not be tolerated.  Cheating is
not only a misrepresentation of your abilities, but it is also
unfair to your classmates.  It also violates the mutual trust
between student and teacher.  You owe it to yourself and your
education to hold a high ethical standard at all times.