EECS 340: Algorithms and Data Structures
Spring 2005
Contacts
Instructor
Vincenzo Liberatore
vincenzo.liberatore@case.edu
As
an anti-spam measure, please,
identify
yourself as a student before using the Messenger.
TA
Danielle Liu
Mailing List
You can send an e-mail to the entire mailing list.
Regulations
Exam Dates
Midterm: Friday, March 4, 4-4:50pm, Glennan 716
Final: Tuesday, May 3, 12:30-3:30pm, Location TBA
Midterm Syllabus
TBA.
Final Syllabus
TBA.
Grading Scheme
Midterm: 25%
Final: 35%
Homework: 40%
Homework regulations
Homeworks are to be turned by the start of class on the due date. No
late homeworks will be accepted, but the lowest homework grade will be
dropped. (In other words, turn in what you have by the start of class.
If your schedule is too busy, just drop the homework. But, try your
best to save the dropped homework for the latter half of the semester,
when you will really need it.) In exceptional circumstances (illness,
university business, religious observances) extensions may be granted.
However, all extensions must be approved by me BEFORE the due date.
As a courtesy to the grader, homeworks should be written neatly. Poorly
written work will not be graded. When writing algorithms be sure not
only that your solution is correct, but also that it is easy for the
grader to understand why your solution is correct. Part of your grade
will be based not only on correctness, but also on the clarity,
simplicity, and elegance of your solution.
In EECS 340, assignments tend to differ substantially from
those in other Computer Science courses. Assignments focus for the most
part on algorithm design and have no programming component.
Furthermore, algorithm design is almost always driven by mathematical
requirements, especially in terms of running time.
The best way to address the assignments is to view them as brainy
puzzles.
Lectures will give you the necessary background and a certain amount of
direction, but the really important component of the homework is to
spend time solving challenging puzzles.
Assignments
References
Vincenzo Liberatore
/ vincenzo.liberatore@case.edu