Computer Science 210
Data Structures

Fall 2016, Siena College



Dr. James D. Teresco, Roger Bacon 321, (518) 782-6992
Electronic mail: jteresco AT (best contact method)
Twitter: @JTerescoSienaCS
Class URL: [Link]
Class hour: Monday, Friday 11:30-12:30, Roger Bacon 340
Lab meetings: Wednesday 10:30-12:30 or 3:50-5:50, Roger Bacon 306
Office hours: Tuesday 10:00-11:30, Wednesday 2:00-3:30, Friday 2:00-3:30, or by appointment


Everything on this syllabus is subject to change. Changes will be announced in class and updated in the online version of the syllabus.

School of Science Mission Statement

The School of Science mission statement can be found .

on the School of Science web site.

Course Description and Objectives

From the course catalog: "This course continues the study of algorithm design and implementation with an emphasis on the use and implementation of data structures such as records, stacks, queues, linked lists, trees and graphs. Students will continue development of programming skills using modular and structured programming techniques in a programming language."

This course is required for the Computer Science Major, the Computer Science 3/2 Program, the Computer Science Certificate, the Information Systems Certificate, and the Computer Science Minor.

Our specific learning objectives for CSIS 210 include the following:


CSIS 120, Introduction to Programming, or equivalent, with a grade of C- or better.

Everyone who enrolls in this course should have a solid foundation in the basics of programming in general and programming in Java specifically. This course moves much more quickly than CSIS 120, so the following topics need to be very well understood before enrolling in this course.

A strong mathematical background is also highly recommended. Ideally, students in this course should at least be ready to take Calculus 1.


The primary text for the course is Programming in Java and Data Structures (an online, interactive text from zyBooks) by Lysecky, Lizarraga, Vahid, and McGovern. The supplementary text for the course is Java Structures: Data Structures in Java for the Principled Programmer, "Root 7" Edition (a free online textbook) by Duane Bailey. This traditional text has been made freely available as a PDF by the author. Other readings may also be assigned from freely available sources.


Everyone is expected to attend class and participate in discussions and to complete in-class exercises. Supplemental readings are listed on the lecture and reading schedule. Of course you are encouraged to do the reading, but all important topics will be covered in class.

The notes used to guide in-class presentations are available as PDF files linked from the lecture and reading schedule. (But you should take your own notes anyway.)

Some lectures will include a small assignment due at the start of the next class. These will often include one of more of the "Participation Activity" or "Challenge Activity" tasks in the primary text. No late submissions of these "lecture assignments" will be accepted, as they will often be discussed in class on the due date. Some assignments will be graded for correctness, while others will be graded based on whether an honest effort was made.

Be prompt, prepared, and ready to focus on the day's topics. This should go without saying, but this means your phones and other devices not being used exclusively to follow along with class materials and/or to take notes must be powered off. You may bring food or drink to class (but not lab), as long as you are not a distraction to your classmates or instructor.

Labs and Project Assignments

We have the advantage of weekly meetings in a computer lab. It may be possible to complete some labs during the meeting, but most of the time you will need to continue to work on your own and turn them in later. Some labs will include larger programming projects, some of which will also include a written component. You may develop your programs anywhere (Computers in the labs, your own PC, etc.) but grading will be done using BlueJ on the Siena College systems unless otherwise specified. It is your responsibility to ensure that your program works on the grading platform. Programs will be graded on design, documentation, style, correctness, and efficiency. Unless otherwise specified, you are permitted (and are in fact, encouraged) to get help from the Computer Science tutors and from your instructor. You may discuss the labs with your classmates, but the work you submit must be your own (and that of group members, for work done in groups when permitted).

Your submissions for lab assignments will include several types of items. Different requirements apply to each, as described below. It is important that you adhere to file format and naming requirements to facilitate grading. Submissions that do not meet these requirements will not be accepted.

Lab Questions
The answers to all "lab questions" for a particular lab should be included within a single plain-text or PDF file named labn.txt or labn.pdf, as appropriate, where n is the lab number. The file should start with your name and the lab number. If you use plain text, your file should be appropriately line-wrapped for easy reading in a window or on a printed page with a width of 80 characters.

Note: for lab questions that ask you to draw a memory diagram, you have a few options. You may attempt to represent the memory with plain text, but that is difficult to construct and read. Ideally, you would use a drawing program and submit in your PDF file, but you are also permitted to draw the diagram on paper and submit a scan or photograph, as long as the diagram is legible in that form.

Practice Programs
Your submissions for practice programs are graded primarily on correctness, but you will be required to include your name at the top of the program, and you must use the file name specified. You are of course encouraged to practice good documentation, formatting, and style for these programs, but the grade will depend only on correctness (and having your name in a properly-named file).
Programming Assignments
These are the most formal submissions and will be graded on design, documentation, style, correctness, and efficiency (where appropriate). A good design will use an appropriate algorithm, data structures, and language constructs to solve the problem. A well-documented program will include a comment at the top of each file that includes your name, the assignment, and a description of the contents of the file. There should also be comments for each constructor or method definition (including a brief description of the method's purpose, its parameters, and return value), each variable or group of related variables, and any section of code whose purpose and/or behavior is not obvious from context or the code itself. Style requirements include appropriate formatting (sufficient and consistent indentation, spacing, and punctuation, wrapping long lines of code), good use of named constants, and meaningful and appropriate names for variables, methods, constants, and parameters. Correctness, of course, requires the expected output be produced for a set of test inputs (which will normally not be provided in advance). Efficiency will be more important in some assignments than others, and requires that the program does not do any unnecessary computation or use any more memory than needed. And, of course, you must use the file name(s) specified.

Unless otherwise specified, late lab and project work may be turned in with a penalty computed as 1.08h%, where h is the number of hours late. Extensions will only be granted in serious situations. You can find a Java program that prints out a table of the late penalties here. Work turned in after solutions have been made available cannot receive credit.

All assignments are to be submitted electronically using the procedure specified on each assignment handout. Please submit written work in portable formats (plain text where appropriate and PDF otherwise). If in doubt about a file format, please check before submitting. Keep a copy of all submissions for yourself. For submissions consisting of more than one file, you will normally be required to submit a single archive (.zip, .7z, and .tar.gz files are acceptable) containing all necessary files.


There will be four exams: two in-class exams during the semester, a practical in-lab exam during the semester, and an in-class final during the exam period. Exact exam dates will be announced no less than 7 days in advance. Make-up exams will be administered only in extreme circumstances and arrangements must be made before the date of the scheduled exam.


Grades for individual assignments and exams are not scaled. Any scaling deemed appropriate will take place at the end of the semester by adjusting the thresholds. The following thresholds may be adjusted downward (thereby raising grades) but will never be adjusted upward.


Lecture/In-Class Assignments 10% A >= 93% A- >= 90%
Labs/Projects 40% B+ >= 87% B >= 83% B- >= 80%
Exam 1 10% C+ >= 77% C >= 73% C- >= 70%
Lab Practical Exam 10% D+ >= 67% D >= 63% D- >= 60%
Exam 2 15% F < 60%
Final Exam 15%

Please note the special grading policy in effect for this course: in order to earn a grade of C- or better for this course, you must have an average of C- or better on the examinations, regardless of performance on labs, projects, and other assignments.

Course grades cannot be changed after they are submitted except in very specific cases (such as an error in grading of an assignment or in computation of a grade). Any such errors that slip through must be found and rectified quickly after grades are submitted. In rare circumstances, a student request for an incomplete grade may be approved at the discretion of the instructor. Requests must be made one week prior to the end of the semester, and terms of such arrangements must be mutually agreed upon before grades are submitted. College policy states that the an incomplete must be reconciled within one month of the end of the semester, and that a student cannot be granted a degree with an incomplete grade on his or her record.


Please be sure you are familiar with the Siena College Attendance Policy.

Every college student should be motivated to attend every lecture and lab meeting for all the right reasons (e.g., desire for knowledge, desire to get the most out of every very expensive minute, etc.). As experienced college students, you understand that regular attendance is essential to your ability to master the course material.

Therefore, there is no formal attendance policy. You are expected to attend regularly, and should still see the instructor about any excused absences. An excused absence may be any of the following:

  1. A documented athletic or academic event that conflicts with a class meeting. The required paperwork must be presented in person at least one week prior to the event.
  2. A family emergency. These must be documented through the Office of Academic Affairs (783-2307), who will then contact your instructors.
  3. Personal illness. These must be documented by the Office of Student Affairs (783-2328), who will then contact your instructors.

While there is no formal penalty for unexecused absences, missing class regularly, frequent tardiness, or being distracted in class (e.g., checking your phone or Facebook) will be considered a sign that you are not taking the course seriously. Common sense suggests and experience validates that students who are frequently absent, late, or inattentive perform poorly on graded work. Do not expect compassion when final grades are assigned or extensive extra help if you do not understand a topic that was covered while you were absent without a valid excuse.

Disability Accommodations

In compliance with the Americans with Disabilities Act and with Section 504 of the Rehabilitation Act, Siena College is committed to ensuring educational access and accommodations for all its registered students.

Any student with a documented disability needing academic adjustments or accommodations should provide documentation of such during the first two weeks of class. All discussions will remain confidential. Accommodations must be arranged with Mr. Rob Bahny, Director of Services for Students with Disabilities (Foy 109, 783-4239).

Complaints about services provided or not provided may be brought to the attention of Public Safety at 783-2376 or Ms. Lois Goland, JD, Title IX Coordinator and Equal Opportunity Specialist (SSU 235, 782-6673).

Academic Integrity

You are encouraged to discuss the concepts related to course assignments and exams with your classmates. This is an essential part of a healthy academic environment. However, work submitted for grading must be your own (or the combined work of group members, for group assignments). Any unauthorized copying or collaboration is considered a breach of academic integrity and will not be tolerated. Academic dishonesty cases are unpleasant and uncomfortable for everyone involved. You are responsible for reading and understanding the document Academic Integrity and the Siena Student and the Computer Science Department's Academic Integrity statement. The minimum penalties for a first violation will include failure (0 grade) for the assignment or exam in question and the filing of a Academic Integrity Violation Accusation Form. A second violation will result in failure of the course and a formal letter describing your misconduct will be sent to the head of the Computer Science Department and the Office of Academic Affairs. Students suspected of violating academic integrity will be referred to the Academic Integrity Committee for final determination.

If there is any doubt about the degree of collaboration allowed or the permitted sources for a particular assignment, please ask for clarification before collaborating or consulting the source. Any such collaborations or sources must be cited properly.