Computer Science 152 has at least four major goals:

1. To build upon the programming knowledge from Computer Science 151 to study the design, analysis, and verification of algorithms,
2. To present problem-solving from an object-oriented programming perspective,
3. To reinforce concepts of object-oriented problem solving by using the Java programming language,
4. To study data abstractions and data structures,
5. To introduce basic elements of large-scale program developed through the use of a large-scale, team project, and
6. To give an overview of the field of computer science.

Henry M. Walker

Office: Science 2420
Telephone: extension 4208
E-mail: walker@cs.grinnell.edu
Office hours are posted weekly on the bulletin board outside my office.
Additional hours can be scheduled by appointment.
If you wish, you may reserve a half hour meeting by signing up on the weekly schedule.

This courses uses two textbooks:

• Rebelsky, Samuel (2000). Experiments in Java. Reading, MA: Addison Wesley Longman. This is the laboratory manual that we will use for the first few weeks of class. It is temporarily available online, but you are expected to purchase copies.

• Bailey, Duane A. (1999). Java Structures: Data Structures in Java^tm for the Principled Programmer. Boston, MA: McGraw-Hill. The primary text for this class. You should expect to read about one chapter each week.

Also, Sun's on-line Java documentation and manual provides useful information about the Java programming language. Two helpful sites follow:

• Documentation: http://www.siteforum.com/sun/jdk12online.html
• Tutorial: http://java.sun.com/docs/books/tutorial/

In addition, students may want to purchase a general reference for the Java Programming Language.

While the schedule for this course is expected to evolve, a Tentative Class Schedule is available in .dvi , postscript and pdf formats.

Also, if you are logged into the departmental network and want a copy printed, click duerer to have a copy printed on the printer duerer, and click pacioli to have a copy printed on the printer pacioli .

Course Work will involve a combination of the following activities.

• Individual Assignments extend the range of problems considered in the course and help sharpen problem-solving skills. Parts of this course may involve individual programming assignments or written exercises.

• Laboratories: While CSC 152 involves fewer labs than CS151, the course does involve directed lab work. This work may be done either in groups (preferred) or individually. Some of these labs may be required, while others will introduce material to be used in other activities.

• Class Project: Participating in a large class project provides a particularly beneficial (if painful) experience. This semester, we'll be working together to build a program to help CSC 151 students test and submit their Scheme programs. Generally, Friday classes will be devoted to this endeavor. A project index provides information about various elements of this project.

• Hour Tests tentatively are scheduled for Monday, February 19, Wednesday, March 14, and Friday, April 20. any changes in these dates will be announced in class at least one week in advance.

• Exam: Following the College's published schedule, the final examination for this class is scheduled for Monday, May 14, at 9:00 am.

Deadlines for specific assignments will be posted on-line at http://www.walker.cs.grinnell.edu/courses/152.sp01/assignments In each case, work is due at the start of each class specified. A penalty of 25% per class meeting will be assessed for any assignment turned in late, even work submitted at the end of a class. However, an extension of at least one class period is automatically granted if department's computer network is down for an unscheduled period for a period of three or more hours during the week preceding the assignment. Normally, a program or laboratory write-up is due every third class meeting.

Absolute Deadline: All homework must be turned in by Friday, December 8 at 5:00 pm;
laboratory reports or programs received after that time will not be counted in the grading of the course.

The work in this course is split between individual and group work. Students are encouraged to work together on all laboratory activities. However, since a primary goal of the course is to enable students to develop their own programs, collaboration is not allowed on supplemental problems or tests. In addition, students should note the department's policy regarding the role of user-consultants for Computer Science 151 .

The final grade will be based upon each student's demonstration of her or his understanding of and facility in programming, not on the performance of the class as a whole nor on a strict percentile basis. While some flexibility may be possible in determining a final semester grade, the following percentages approximate the relative weights attached to various activities in this course.

This document is available on the World Wide Web as

     http://www.walker.cs.grinnell.edu/courses/152.sp01/index.html