CS 104 (Fall 2004) - Data Structures

Syllabus

• Subjects: Lists, Strings, Arrays, Trees and Graphs. Storage systems and structures. Storage allocation and garbage collection. Searching and sorting techniques. Generalized data management systems. 
• Prerequisites: CS 26, Math 52 or 54.
• Textbooks: 
  • (required text) Data Structures & Algorithm Analysis in JAVA, by Mark Allen Weiss, ISBN 0-201-35754-2. 
  • (optional) Algorithms in JAVA (Parts 1-4), by Robert Sedgewick, ISBN 0-201-36120-5.
• Exams: Two written exams. See schedule.
• Assignments: 8 homework assignments and one final team project assignment. Each assignment will consist of a written part and a programming part. See schedule.
• Grading: 
  • Homework 56%, exams 34%, final team project 10%.
  • The homework with the lowest score is dropped from calculation.
  • Grade distribution per total point (this is an absolute grading system): 40% or higher will give you a base score D-, with each additional 5% giving you a step up (steps being D-, D, D+, C-, C, C+, B-, B, B+, A-, A, A+). Hence, e.g., 60% or higher gives you C, and 95% or higher will you A+. Lower than 40% is a Failure (F). 
• Further requirements:
  • Read this website frequently, especially before exams, and due dates of assignments.
  • Read class emails (sent to your emba account) regularly.
• Honor code: The UVM Honor Code applies to your conduct in this course. In particular, all work submitted for credit must be your own. You may discuss your homework assignments with your classmates, TAs, and the professor. However, you should write up solutions on your own and should not read or copy the solutions written by others in this or previous semesters. For programming part of the assignments, you must write your code for yourself, and are permitted to read code written by classmates only if you are helping them debug their programs after you have completed your own. Team projects are collaborative efforts of the team members. Reading or copying other team's code is not allowed (unless reading for the purpose of debugging after your team's project is done). The UVM policy on sources also applies to this course, which means that all sources must be acknowledged, whether allowed by the professor or not. For example, software provided by someone else must be acknowledged when incorporated into your work, and discussions with classmates should be acknowledged.
• Disabilities: We encourage students with disabilities, including "invisible" disabilities such as chronic diseases and learning disabilities, to discuss with the professor any appropriate accommodations that we could make on their behalf.