CSC 207 Grinnell College Fall, 2014
Algorithms and Object-Oriented Design

  Class Schedule    Supplemental Problems   Instructor   Textbooks   Course Work
  Deadlines   Collaboration   Cell Phones   Accommodations   Grading   Tutors and Mentors

CSC 207, Algorithms and Object-Oriented Design, explores object-oriented problem solving using the Java programming language (a language widely used for large-scale applications and systems). Topics and themes covered include:

To cover this material, the course is roughly divided into 14 units:

  1. Introduction to Object-oriented problem solving and Java
  2. OO Case Study: Volleyball or Racquetball
  3. Objects and classes
  4. Utilizing objects and classes
  5. Generics and interfaces
  6. Introduction to the analysis of algorithms
  7. Collections
  8. Sorting
  9. Software development with assertions and loop invariants
  10. Implementing collections
  11. Linked lists
  12. Tree structures
  13. Hashing and hash tables
  14. Heaps and heap sort

Blended through the course, several discussions will highlights approaches for effective and efficient software development.


Henry M. Walker

Office: Science 3811
Telephone: extension 4208

Office hours are posted weekly on the bulletin board outside Science 3811, with additional hours possible by appointment. You may reserve a half hour meeting by signing up on the weekly schedule, but please sign up at least a day in advance.


Although a textbook is not required for this course, many students appreciate a tutorial and reference book that coordinates well with the topics and organization of the course. For these students, the following text is recommended:

In addition, the following on-line references may be useful:


While the schedule for this course is expected to evolve, a detailed Tentative Class Schedule is posted with readings, labs, assignments, examples, etc. This schedule will be updated as the course evolves.

Course Work

All programming for this course must meet reasonable standards for clarity, readability, maintainability, and efficiency. Also, submitted programs must compile appropriately, tests should demonstrate program correctness, and some commentary is needed to explain why programs produce correct answers. See Notes on Program Standards for details on writing and testing programs according to basic standards.

Course Work will involve a combination of the following activities.


Deadlines are shown on the Tentative Class Schedule, and 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 the department's Linux network is down for an unscheduled 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.

Although dates for labs, programming assignments, tests, and the final exam are firm, I understand that circumstances arise when you are not able to attend class.

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


Collaboration often will be allowed on laboratory exercises, but collaboration normally will NOT be allowed on supplemental problems and tests. To avoid confusion, the rules for collaboration on homework are included in the specification of each assignment.

Cell Phones, Text Messaging, and E-Community Devices

Cell phones, text-messaging devices, and other social-networking connections may not be used in this class. If you bring such equipment to the classroom, it must be turned off before the class starts and stay off throughout the class period. Use of such equipment is distracting to those nearby and will not be tolerated.


If you have specific physical, psychiatric, or learning disabilities and require accommodations, please let me know early in the semester so that your learning needs may be appropriately met. You will need to provide documentation of your disability to the Director of Academic Advising. Feel free to talk to me if you have questions or want more information.


This instructor's grading philosophy dictates that the final grade should ultimately be based upon each student's demonstration of her or his understanding of the material, not on the performance of the class as a whole nor on a strict percentile basis. The following scheme is proposed as a base for how the various assignments and tests will be counted in the final grade.

Lab Write-ups: 30%     Supplemental Problems: 20%     Tests: 30%     Exam: 20%    

This document is available on the World Wide Web as

created 10 May 2011
revised 7 April 2012
updated 2 May 2013
updated 12 July 2014
updated 26 August 2014
updated 25 September 2014
Valid HTML 4.01! Valid CSS!
For more information, please contact Henry M. Walker at

Copyright © 2011-2014 Henry M. Walker.
This work is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License .