CS 261 University of Puget Sound Spring, 2020
Computer Science II
Abstract Data Types and their Implementations, Some Basic Algorithms,
Object-oriented Problem Solving, and Efficiency

Warning: This course is under development. Although the basic structure of this course is largely established, nothing on this Web site should be considered official or even possibly correct.


 Class Schedule  Supplemental Problems  In-class Materials  Deadlines
 Instructor  Resources  Anticipated Work Load  Java Style Guide
 Course Work  Collaboration  Tutors and Mentors
 Cell Phones  Accommodations  Grading

CSCI 261, Computer Science II, explores object-oriented problem solving, abstract data types and their implementations, some basic algorithms, and efficiency. Topics and themes covered include:

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

  1. Introduction to Object-oriented problem solving and Java
  2. Enumerated Types/Classes
  3. Classes, Subclasses, and Generalization
  4. Generics and interfaces
  5. Introduction to the analysis of algorithms
  6. Software development with assertions and loop invariants
  7. Basic Sorting
  8. Collections and their Implementations
  9. Linked lists
  10. Tree structures
  11. Abstract Data Types: Stacks and Queues
  12. Heaps, Priority Queues, and Heap Sort
  13. Hashing and Hash Tables

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


Henry M. Walker

Office: Thompson 410
Telephone: extension 3562
E-mail: henrywalker@pugetsound.edu and walker@cs.grinnell.edu

Office hours are posted on the bulletin board outside my office, with additional hours possible by appointment. During office hours, I will try accommodate all students who want to talk with me, largely following a first-come, first-served strategy.


Textbook: Elliot B. Koffman and Paul A. T. Wolfgang, Data Structures: Abstraction and Design Using Java, Third Edition, John Wiley and Sons, 2016, ISBN: 978-1-119-23914-7 and 978-1-119-22307-8.

Additional Resources:


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.

Anticipated Work Load

This course incorporates a variety of activities, including class preparation (reading), labs and projects (started in class and finished for homework), and supplemental problems (some required and some available for extra credit), as well as quizzes, tests, and a final exam. From past experience, the time required for these activities will likely vary substantially from student to student and from one part of the course to another. For example, a student may need to devote considerable time and effort when starting a new or different topic, but the workload may drop noticeably when that material is mastered.

Such variation in student experiences complicates any estimation of the time individual students may need to devote to homework for this course. However, from past experience, students working steadily on the course likely should expect to allocate 10-15 hours per week to homework. Some students may require additional time for some weeks; some students may complete work in less time for some weeks. Conversations with computer science faculty and others suggest this time allocation is consistent with expectations for many courses at Grinnell College and the University of Puget Sound.

Course Work

All programming for this course should follow the Java Style Guide—a compendium

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.

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 Wednesday, 6 May 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, quizzes, 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.

For more information, see the Academic Handbook, pages 34-35.

Some Additional University Policies

In addition to course policies identified in this syllabus, the University of Puget Sound has asked instructors to highlight the following university policies:


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%     Quizzes: 15%     Test: 15%     Exam: 20%    

created 24 June 2019
revised Summer-Fall 2019
revised 14-15 January 2020
Valid HTML 4.01! Valid CSS!
For more information, please contact Henry M. Walker at walker@cs.grinnell.edu.