Computer Science & Engineering 190L
Object Oriented Programming and Design

Lecture and Section Times

Lecture             MWF 12:30—1:20, MGH 389

Sections           various times on Tuesday

Textbooks

Core Java, Volume I, Horstmann, required

Core Java, Volume II, Horstmann, optional

Course Overview

This course explores in depth the object-oriented features of Java (inheritance, interfaces, polymorphism) and the associated design issues. The course also covers event-driven programming using the standard Java AWT and Swing libraries for constructing Graphical User Interfaces (GUIs). Students will complete a significant programming project at the end of the course working in groups of 3 or 4 students.  Prerequisite: CSE143.

Course Web Page

Information about the course will be kept at:

http://www.cs.washington.edu/education/courses/190l/

(that’s a lowercase “L” after 190).  The web page will include links to useful resources, class handouts, lecture notes and a message board.

Course Administrator

Pim Lustig (pl@cs.washington.edu, 616-3225) is the course administrator and will handle many details including registration and switching sections.

Late Policy

Each assignment will list its due date.  Each student in the class will have a total of three “free” late days (a late day is 24 hours of lateness).  There are no partial days, so assignments are either on time, 1 day late, 2 days late, etc.  Because of this generous late policy, students will not be granted extensions for assignments unless they have some highly extenuating circumstances.  Once a student has used up all of his or her late days, each successive late day will result in a loss of 1 point.  No assignment will be accepted more than 7 days after its due-date.

The group project will have its own late policy.

Grading

In the first half of the course you will be expected to complete a variety of weekly programming assignments.  In  the second half you will be expected to work on a group project.  You will also be asked to take two open-book/open-note exams: a midterm and final.  The resulting scores will be combined according to the following weightings:

25%     programming assignments (first half of the course)

25%     group project (second half of course)

20%     midterm (in class on Wednesday, 5/2/07)

30%     final exam (on Thursday, 6/7/07, 8:30—10:20 am)

Using the weightings above, each student’s scores will be turned into an overall score ranging from 0 to 100 percent.  These will be turned into grades as follows:

90%     at least 3.5

80%     at least 2.5

70%     at least 1.5

60%     at least 0.7

If you need to miss an exam, you must contact Stuart prior to the exam to get permission.  Even if you are sick at home, you should be able to call your instructor’s office phone number to leave a message that you need to be contacted.

Weekly programming assignments will generally be worth 20 points, although the last assignment (just before the midterm) will probably be a two-week assignment worth 40 points.

Policy on Collaboration

You are to complete programming assignments individually.  You may discuss the assignment in general terms with other students including a discussion of how to approach the problem, but the code you write must be your own.  The intent is to allow you to get some help when you are stuck, but this help should be limited and should never involve details of how to code a solution.  You must abide by the following:

• You may not work as a partner with another student on an assignment.
• You may not show another student your solution to an assignment.
• You may not have another person (current student, former student, tutor, friend, anyone) “walk you through” how to solve an assignment.

The group project will have a different collaboration policy that will be included in the project description.