CSCI 151: Data Structures

Semester:	Fall 2016
Room:	King 323
Class Time:	Mon/Wed/Fri 9:00pm-9:50am
Office Hours:	Wednesday, 15:00-16:30pm Thursday, 2:30-4:00pm or by appointment

Professor:	Roberto Hoyle
email:	roberto.hoyle AT oberlin edu Please include "cs151" in the subject.
Office:	King 229
Phone:	x58424

Announcements

• Labs are posted below -- prelabs are made available on Friday, full labs on Monday.
• Lab helper information is available below.
• I have made some source code from class demos available in a Dropbox folder at https://www.dropbox.com/sh/jxtolqi075no7i7/AAC4V-omWf2RYejIYtdGC9eMa?dl=0
• You can access the Piazza forum for this class either through BlackBoard ("Discussion Forum" on the left side menu), or through piazza.com/oberlin/fall2016/

Schedule

(Will be updated throughout the semester)

Course Description

From the Oberlin catalog course description:

This course builds upon the principles introduced in CSCI 150 and provides a general background for further study in Computer Science. The course will cover object-oriented programming concepts; the design and implementation of data structures (linked lists, stacks, queues, trees, heaps, hash tables, and graphs) and related algorithmic techniques (searching, sorting, recursion); and algorithm analysis. Students will be expected to complete a number of programming projects illustrating the concepts presented.

Goals and course objectives

My goals and objectives for students taking this course are as follows:

1. Understand Big-O measurements and why it is of great importance to data structures and algorithms
2. Study common algorithms used in computer science
   • Sorting: Bubble, insertion, shell, merge, quick, heap, radix
   • Searching/Selection: Linear, binary, quick
3. Become skilled in common data structures (lists, stacks, queues, trees, heaps, hashtables)
   • Be able to create any of these from scratch -- structure and operations
   • Know the running times for the most common operations
   • Be able to reason about which structure is most appropriate for a given task
4. Become fluent in Java programming including
   • Design and creation of interworking classes
   • Proper use of visibility modifiers
   • Creation and handling of exceptions
   • Regular use of Javadoc
5. Gain experience using various tools in the Java/Linux environment
6. Develop the habits of proper coding and thorough testing

Textbook

The text for the course is Data Structures and Problem Solving Using Java, Fourth Edition by Mark Weiss. All of the code from the text is available on the author's website: http://users.cis.fiu.edu/~weiss/dsj4/code/code.html

Data Structures & Problem Solving Using Java by Weiss

You can use the 3rd edition if you want, but you might want to cross-check the readings.

A copy should be on reserve in the library.

Useful links

• Thinking in Java by Bruce Eckel
• The Java Tutorial from Sun.
• Java 1.5.0 Documentation (java.sun.com) (local copy)
• Java 1.6.0 Documentation (java.sun.com) (local copy)
  • API Specification (java.sun.com) (local copy)
  • java.lang package (java.sun.com) (local copy)
  • java.util package (java.sun.com) (local copy)
  • java.io package (java.sun.com) (local copy)
• Collections (also known as Containers)
• Professor Newhall's Tips on How to Compile, Run and Debug Java Programs
• Common Java Error Messages (also a more humorous version)

---

java.util.* 1.6 Local Copy java.util.Scanner 1.6 Local Copy java.util.Random 1.6 Local Copy java.util.Collection<E> 1.6 Local Copy java.util.List<E> 1.6 Local Copy java.util.AbstractList<E> 1.6 Local Copy java.util.ArrayList<E> 1.6 Local Copy java.util.LinkedList<E> 1.6 Local Copy java.util.Iterator<E> 1.6 Local Copy java.util.ListIterator<E> 1.6 Local Copy java.util.PriorityQueue<E> 1.6 Local Copy java.util.Comparator<E> 1.6 Local Copy java.util.Enumeration<E> 1.6 Local Copy java.util.Set<E> 1.6 Local Copy java.util.AbstractSet<E> 1.6 Local Copy java.util.TreeSet<E> 1.6 Local Copy java.util.HashSet<E> 1.6 Local Copy java.util.HashMap<K,V> 1.6 Local Copy java.util.Hashtable<K,V> 1.6 Local Copy java.util.TreeMap<E> 1.6 Local Copy java.lang.* 1.6 Local Copy java.lang.System 1.6 Local Copy java.lang.Exception 1.6 Local Copy java.lang.Character 1.6 Local Copy java.lang.Integer 1.6 Local Copy java.lang.Math 1.6 Local Copy java.lang.String 1.6 Local Copy java.lang.StringBuffer 1.6 Local Copy

java.io.* 1.6 Local Copy java.io.File 1.6 Local Copy java.io.FileInputStream 1.6 Local Copy java.io.Serializable 1.6 Local Copy java.awt.* 1.6 Local Copy java.awt.Color 1.6 Local Copy java.awt.FlowLayout 1.6 Local Copy java.awt.BorderLayout 1.6 Local Copy java.awt.GridLayout 1.6 Local Copy java.awt.GridBagLayout 1.6 Local Copy java.awt.event.ActionListener 1.6 Local Copy javax.swing.* 1.6 Local Copy javax.swing.JFrame 1.6 Local Copy javax.swing.JPanel 1.6 Local Copy javax.swing.JLabel 1.6 Local Copy javax.swing.JButton 1.6 Local Copy javax.swing.JComboBox 1.6 Local Copy javax.swing.JTextField 1.6 Local Copy javax.swing.JTextArea 1.6 Local Copy javax.swing.JEditorPane 1.6 Local Copy

Grading

Course grades will be calculated based on the following distribution:

• 55% - Homework/Labs
• 15% - Midterm exam
• 20% - Final exam (not optional)
• 10% - Participation

The distribution might be adjusted based on the progression of the course.

---

Programming projects will generally consist of two major components:

1. An underlying data structure implementation
2. An application of this data structure

The actual breakdown of points will depend on the individual project, but the plurality of points will be for the data structure implementation. Projects will also be graded on style, documentation, and test cases.

If a portion of your program is not working correctly, please clearly indicate it in the comments at the beginning of the file and in the methods that are not working. Problems that I discover are graded more severely than those you discover.

---

Programming assignments will be graded on both correctness as well as programming style. Good programming style includes the following:

• A descriptive header for each file including author's name and the date e.g.,

  /**
   * A demonstration header used for the class syllabus.  Additional lines
   * give additional information in JavaDoc.
   *
   * @author Roberto Hoyle
   * Spring 2012
   */

• Descriptive and meaningful variable and method names
• Logical organization
• Sufficient comments, but not overly commented
• Appropriate use of white space to separate sections
• Consistent indentation and style

More information on Java style can be found on Sun's Code Conventions web page. There is also an open source tool checkstyle that can be used to check the style used.

Course Policy

Attendance

Regular class and lab attendance and participation is expected. Please talk to me if regular class attendance is going to be a problem.

Homework Assignments

There will be a number of assignments made in this class. I expect every student to attempt each assignment and turn in the results. You are encouraged to complete every assignment as this is one of the most effective ways to learn the material.

If you know that for some reason you will not be able to submit the assignment before the deadline, you should contact me in advance of the deadline. Extensions are only granted in exceptional circumstances, but need to be done in advance.

Late submissions of lab assignments will be penalized up to 50% per day after the deadline. No late prelabs will be accepted. You will be allowed 1 late day in each half of the semester and 1 late day that can be used whenever (total of 3). You must include the fact that you are using one of your late days in the README document for an assignment.

Accommodations for students with disabilities

If you have a disability that might impact your performance in this course, or requires special accommodation, please contact me as soon as possible so that appropriate arrangements can be made. Support is available through Student Academic Services, specifically Jane Boomer. You will need to contact them to get your disability documented before accommodations can be made.

Plagiarism and Academic Dishonesty

I have very low tolerance for academic dishonesty, and will vigorously pursue available remedies for any incidents. All work in this class is to be performed according to the Oberlin Honor Code. Specifically I expect that:

1. Quizzes and exams will be closed book, closed notes, and no communication between students. This includes discussing the same to students who are taking a quiz/exam at another time.
2. Discussion of assignments is expected and encouraged, however all work and code on assignments should be your own without outside assistance.
3. Sources should be cited including the textbook and other web sites when you use them in your work.
4. You are not permitted to share your source code with other students, including future ones.
5. You are not permitted to use other students solutions as your own (even those from a prior semester), nor answer keys, nor instructor versions.

Illustrative examples:

1. Confirming that we had and exam is OK, telling another student in the class who has not taken it that it was easy/hard, what topics, etc. is NOT OK.
2. On a project or homework, discussing what needs to be done and how it can be done is OK, having a student (other than a TA) go over your code is NOT OK, discussing what might be wrong and how to tell is OK (and encouraged).
3. Other than your partner on a given assignment, it is NOT OK to give a student a copy of your code or for them to give you a copy of theirs. As a rule of thumb when discussing the assignments, you should not be writing finished solutions out, and you should be able to independently recreate the material on your own.
4. On an assignment, you base your design off of the textbook's example. This is OK if you cite the source in the code. You don't need to have it be part of the Javadoc. E.g.,

   /* based on insertion sort from Weiss 3rd Ed, p. 306 */

All assignments must include the following signed statement:

"I have adhered to the Honor Code in this assignment."

Electronic submissions should include the honor statement in either the README file or header comments and must include your name.