Course Syllabus

810:052

Data Structures

Fall Semester 1997

Basics

Instructor: Eugene Wallingford

• Office: 331 Wright
• Phone: 273-5919
• E-Mail: wallingf@cs.uni.edu
• WWW: http://www.cs.uni.edu/~wallingf/

• Office Hours:
  • 1:00 PM - 3:30 PM Monday
  • 10:00 AM - 3:30 PM Wednesday

Texts

• Data Structures via C++: Objects by Evolution, by Mike Berman
• Data Structures in C++: A Laboratory Course, by James Roberge

Course Web Page

• http://www.cs.uni.edu/~wallingf/teaching/052/

Course Goals

This course has two primary goals. First, as the title indicates, the course introduces you to the study of data structures. Second, it aims to support your ongoing development as a programmer. These goals complement each other: The best way to learn about data structures is to write programs that implement and use them, and the best way that you improve as a programmer is to solve new and more challenging problems. (Ours will deal with data structures.)

Over the course of this term, you will continue to explore how to analyze problems in an object-oriented way, to design object-oriented solutions, and to write computer programs in C++ that choose and implement appropriate data structures. By the end of the term, you should feel comfortable:

• solving a range of problems that require basic data structures and
• writing C++ programs to implement your solutions.

Course Requirements

• Class sessions -- Our class meetings will consist of a mixture of lecture, discussion, and in-class exercises. We will also spend time preparing for and reviewing lab sessions. Much of the material that we cover in class will expand upon what appears in your texts, so attendance is essential. You will be expected to read assigned topics prior to the class session and to participate actively in class.

• Laboratory -- There are fifteen scheduled laboratory sessions, beginning the first week of class. Attendance of lab sessions is required -- you will receive credit for a lab only if you attend. During each lab session, you will do exercises that are designed to complement the topics being covered in class that week.

• Programming assignments -- Over the course of the semester, you will complete somewhere between six and ten outside programming assignments. These assignments will involve applying techniques learned in class and will often involve code originally developed in a prior lab session.

• Exams -- Finally, we will have two fifty-minute examinations during the semester and a comprehensive final exam at the end. The exams will be "closed book", though sample code will usually accompany the exam as a part of the questions.

Course Evaluation

Grades will be determined on the basis of your performance on laboratory exercises, programming assignments, and examinations. Final grades will be based on the following distribution:

Grades will be assigned using an absolute scale:

• 90% or above for an A,
• 80% or above for a B,
• 70% or above for a C,
• 60% or above for a D, and
• below 60% for an F.

This means that there is no curve.

Course Policies

• I try to accommodate student needs whenever possible, but I can only do so if I know about them. If you ever have to make alternate arrangements for a class session, a quiz, or an assignment, contact me in advance. The safest way to make such arrangements is by notifying me via e-mail of your circumstances and of how you can be reached.

• My regularly-scheduled office hours are times when I am committed to provide assistance to you. No matter how busy I may appear when you arrive, the office hours are for you. You are welcome -- and encouraged -- to make use of that time. I am also available by appointment at other times if you cannot make an office hour.

• All assignments are due at their assigned date and time. In order to receive partial credit, always submit your best effort at that time. Late work will not be accepted.

• Working together is encouraged for programming assignments, to help you understand the problems and to encounter different points of view. However, any work you submit must be your own. Additionally, any collaborations should be acknowledged explicitly in the work submitted. Undocumented or unacceptable collaboration, including the sharing of code, will be considered a form of academic dishonesty.

• UNI has an established policy of academic integrity. Plagiarism and other forms of academic dishonesty will not be tolerated in this course. See the UNI catalog for details on the university's policy.

Computing Environment

Most course materials will be made available via the World Wide Web during the semester. I also frequently send e-mail to inform you of breaking news and to answer common questions. E-mail and the web are, of course, accessible from all university computer laboratories.

Our laboratory sessions will be held in 112 Wright Hall, which contains 20 Unix work stations. We will be using GNU C++ as our programming environment, both for labs and for outside assignments. Submission of programs for grading will usually be via e-mail.

You may choose to do programming assignments on other platforms, such as your own PC or Macintosh. To do this, you will need to have access to a C++ compiler. Turbo C++ is available on the PCs in 112 Wright as well as on the machines in all ITS student laboratories across campus. You might also wish to purchase your own compiler. Such programs are typically available to students for proces in the $50-$150 range. Even if you do use another platform, the final version of your program must compile, link, and run under GNU C++.

Tentative Schedule

The schedule on the following page gives a rough sketch of the topics we will cover and the distinguished dates this semester. If we need to re-schedule an exam, I will notify you at least one week prior to the exam date.

The FINAL EXAM is Thursday, December 18, 1997, from 10:00 AM - 11:50 AM.