Schedule

Students should consult this page regularly to see the most current version of the schedule of topics and readings.

You should complete all assigned readings and attempt to work all the problems at the end of each section as you are reading. Some of these will show up in the regular quizzes during the first five minutes on Friday mornings, and may also appear on the midterm or final.

Lecture	Date	Topic	Code and Handouts
1)	Sep 4	Introduction & OOP	Bicycle Demo
2)	Sep 6	Java Basics	Basic Java Syntax
3)	Sep 9	Inheritance and Interfaces	Mountain bike and inner class example
4)	Sep 11	Java Graphics and GUIs	Code, Swing and Graphics Handouts
5)	Sep 13	Generics, Packages, and JavaDoc
6)	Sep 16	Exceptions, Files, and I/O	Code
7)	Sep 18	ArrayLists	Code
8)	Sep 20	ArrayLists implementation
9)	Sep 23	Singly Linked Lists	Code
10)	Sep 25	Doubly Linked Lists	Code
11)	Sep 27	Doubly Linked Lists cont'
12)	Sep 30	Stacks, Queues, and Iterators
13)	Oct 2	Analysis of Algorithms
14)	Oct 4	Analysis of Algorithms II
15)	Oct 7	Midterm I review
16)	Oct 9	Sorting Basics (Midterm I in lab)
17)	Oct 11	Sorting Basics
18)	Oct 14	Mergesort
19)	Oct 16	Quicksort
20)	Oct 18	Comparators	Code
21)	Oct 21	Fall Recess
22)	Oct 23	Binary Trees	Code
23)	Oct 25	Priority Queues
24)	Oct 28	Symbol Tables and Binary Search
25)	Oct 30	Binary Search Trees
26)	Nov 1	Binary Search Trees
27)	Nov 4	2-3 search trees
28)	Nov 6	Red-black trees
29)	Nov 8	Red-black trees
30)	Nov 11	Midterm II review
31)	Nov 13	Hash tables (Midterm II in lab)
32)	Nov 15	Hash tables
33)	Nov 18	Intro to Undirected Graphs
34)	Nov 20	Undirected Graphs
35)	Nov 22	Directed Graphs
36)	Nov 25	Directed Graphs
37)	Nov 27	Thanksgiving
38)	Nov 29	Thanksgiving
39)	Dec 2	Shortest Paths
40)	Dec 4	Shortest Paths II
41)	Dec 6	Shortest Paths II
42)	Dec 9	Minimum Spanning Trees
43)	Dec 11	Summary

Assignments & Labs

Labs for this course will be held on Wednesday afternoons from 1:15 p.m to 2:30 p.m. and from 2:45 p.m. to 4 p.m. in 229 Edmunds. The room is equipped with iMac computers.
Attendance at these lab sessions is mandatory. Please arrive well prepared for the lab, having read the description thoroughly.

Unlike in CS 51 at Pomona, lab work will be distinct from the weekly programming assignments, though the lab work will generally be relevant to the longer assignments. Instead, we will often use lab time to introduce you to new software tools and techniques that require more hands-on experience to understand. You will usually need to submit your results from the lab by end of the lab day.

There will be two types of weekly programming assignments: individual programs and team programs. All programs assigned during the semester should be completed following the guidelines in the Academic Honesty Policy.
There will be 10 to 12 weekly programs due. All programs will be graded on design, documentation and style, correctness, and efficiency. The elements of a good program are very much like the elements of a good paper. It must be correct, but it should also be written in a style that is clear and elegant. Most programs will be tested using automated tools, so it is essential that your program meet all of the specifications provided in the project handout. You will also receive written comments on all of your programs by the TAs.

Weekly assignments will generally be due on Tuesday evenings at 11:59 p.m. There will be a penalty assessed of 3ⁿ % for a program that is n days late. Programs will not be accepted more than four days late. It is usually better to turn in a correct and well-documented program one or two days late than a non-functioning or non-documented program on time.
All projects should be submitted electronically. The procedure will be explained in lab.

Lab Date	Lab	Assignment Due	Assignment
Sep 10	Introduction	Sep 10	Introduction
Sep 11	Silver Dollar Game	Sep 17	Graphic Silver Dollar Game
Sep 18	Debugger		Darwin
Sep 25	Arraylist implementation	Oct 1	Darwin, cont.
Oct 2	Timing	Oct 8	Calculator
Oct 9	Midterm I		Compression
Oct 16	Linked Lists implementation	Oct 23	Compression, cont.
Oct 23	Mergesort	Oct 29	On-disk sort
Oct 30	Binary Trees	Nov 5	Autocomplete
Nov 6	Git	Nov 12	Hex-A-Pawn
Nov 13	Midterm II	Nov 19	Hashtables
Nov 20	Profiling	Dec 3	Maps
Dec 4	Concurrency	Dec 6	Maps, cont.

Documentation & Handouts

The following documents provide information on the standard Java libraries and the additional libraries we have developed for this course:

• Submission Instructions
• CS 62 Style Guide
• Algorithms 4 materials
• Textbook website
• source code
• Java materials
• Java Tutorial from Oracle
• Java 9 Libraries
• Programming with Assertions
• Moti Ben-Ari's Guide to Compile and Runtime errors in Java
• Iterating over collections in Java 8
• Streams
• Java Graphics
• Standard Java Graphics
• Swing Handout
• GUI Cheat Sheet
• Handling Mouse Events in Java
• JUnit materials
• Testing with JUnit
• JUnit cookbook
• JUnit documentation for Eclipse

Exams

There will be two in-class midterm exams plus a scheduled final exam. There will also be quizzes every Friday except the first week of classes. The quizzes will be during the first five minutes of class. No make-ups will be allowed, but the lowest score will be dropped to make up for illness or other absences.

• Midterm examination 1: Wednesday, Oct 9, in lab.
• Midterm examination 2: Wednesday, Nov 13, in lab.
• Final examination: Friday, Dec 20, 9:00 a.m. - 12:00 p.m., in class.

The midterms will be given during your lab period in order to allow 75 minutes to work on the exam rather than the 50 minutes available during a class period. We will place sample midterm exams on-line approximately a week before each exam.

Grading Summary

Component	Weight
Weekly Programming Assignments	35%
Midterm 1	15%
Midterm 2	15%
Final Exam	25%
Labs	5%
Quizzes	5%
Total	100%

Collaboration & Academic Honesty

The Computer Science Department seeks to create a friendly and supportive learning environment. We encourage students to work in groups to review material from the lectures and readings, to work practice problems from the text, to study for exams, and to discuss the general ideas and approaches to assignments. However, work submitted for a course must be done independently, unless collaboration on a particular assignment is explicitly permitted. Effective learning is compromised when this principle is violated. As explained in the Pomona College Student Handbook, this means that the work you turn in must represent only your own work. It must not be based on help from others or information obtained from sources other than those approved by the instructors.

The following discussion reflects our general understanding of academic honesty in the Computer Science Department. Any exceptions or differences will appear in the course syllabus or the instructions for an assignment. Ask an instructor if you are ever unsure about what constitutes acceptable behavior.

Collaboration policies

The types of work and the level of expected collaboration vary from course to course and assignment to assignment. In this section, we describe some typical expectations. Instructors will often indicate that an assignment falls into a particular category, occasionally with additional remarks about the use of specific materials or sources. Students may freely use any resource that is provided by the instructor for an assignment.

Individual work

Most work in our courses is to be completed individually. In general, the work that is submitted for an assignment must be the student's own. Students may not submit work under their own name that is done by, or in collaboration with, someone else. Copying solutions from any source, including the web or students in previous offerings of the course, is not allowed.

Students should not read or possess copies in any form--physical or electronic--of another student's work. There is no legitimate reason for a student to possess a copy of another student's assignment, to send a copy of student work from one computer account to another, or to be logged-on to another student's account. Providing one's own work to another student is also a violation of these policies.

We routinely use software and other tools to detect similarities between submissions. Identical, or nearly identical, submissions will be considered conclusive evidence of plagiarism.

For programming assignments, students may normally discuss general approaches to assignments, and they may give or receive "consulting" help for specific problems with software or computer programs. A student may look at another student's work only when help is requested. In that situation, the student takes on the role of mentor, and the interaction must be limited to the immediate problem. Two students sitting side-by-side and working through a program step-by-step will certainly produce work that will be considered evidence of illegal collaboration.

On problem sets, group discussion of the general ideas and approaches is permitted, provided the group members are noted on the submitted solutions. However, each student must write the solutions apart from the group, without consulting notes or other artifacts from the discussion. Although papers are less common in computer science classes, when they are assigned they must adhere to the usual levels of academic integrity. The prose must be the student's own, and all external sources must be properly cited.

Group assignments

Sometimes assignments are to be done by small teams of students. In these situations, the team takes on the role of an individual in the preceding discussion. The members of a team may communicate with one another, but collaboration with members of a different team is not permitted.

Exams and test programs

As stated in the Pomona College Student Handbook, "Students neither give nor receive assistance with examinations." Each examination will have a clear statement of what resources are permitted. Any use of material beyond those limits is not allowed. Take-home examinations will have time limits and similarly explicit rules; they are subject to the same policies. During examinations students may ask the instructor questions of clarification. The instructor will decide how complete an answer can be given. Some courses have "test programs" which are programming assignments that are to be treated in the same way as take-home examinations.

Practice exercises

Some assignments are intended to give students comfort with a programming language feature or software environment. On these, any kind of assistance is permitted. The point is to get the work done.

Use of course materials

Course materials that are distributed in class, on Github, on the web, or by other means are provided solely for students in the class. Students are encouraged to use them to the fullest extent, but they are not to publish or distribute them to other people or organizations.

Responsibility of mentors and graders

Course assistants are routinely provided with solution sets to assignments. The solutions are intended to be an aid to effective mentoring and grading. Course assistants are not to distribute the solutions, in whole or in part, at any time. Graders who encounter suspicious similarities between submissions must report those instances to the instructor in the course.

Penalties

Failure to abide by our rules will be considered a violation of the college's academic honesty policy and will result in severe penalties. Instances of plagiarism are easy to identify and will be handled promptly. The first offense typically results in failure in the course and is always reported to the Dean of Students Office. A second offense is automatically referred to the College's Board of Academic Discipline. See the Academic Honesty Policy in the Pomona College Student Handbook for further information. Students from other Claremont Colleges will be treated according to the procedures of their home campus. Please do not put us, yourself, or anyone else in an unpleasant situation.

In this class, the default penalty for any sort of academic dishonesty shall be failure in the course. Please do not put yourself or any of your classmates in this position.