Syllabus
CSCI 3510
Data Structures
Fall 1999

Emergency Numbers

severe weather

http://www.ecu.edu/oehs/emergency/SEVERE.HTM

university emergency notices (included closings)

http://www.ecu.edu/services/weatherpage.html

emergency information hotline

252-328-0062

Prerequisites

Outline

In this course, we will study advanced techniques in computer programming, using the C++ programming language. Topics to be studied include the following.

1. Dynamic memory allocation. Language features for allocating and deallocating memory on-the-fly will be studied.

2. Concrete data structures. This is concerned with how to represent and work with data in the computer, especially using dynamic memory allocation. We will study a variety of data structures.

3. Algorithms and problem solving. Generally, concrete data structures have associated algorithms. We will study a few algorithms and techniques for manipulating data.

4. Abstract data types. This is concerned with how programs should be organized to make working with concrete data structures manageable.

5. Elementary Concepts of Object-oriented Programming. Object-oriented programming can be used to implement and extend the concept of abstract data types.

6. Correctness. You need to have some way to convince yourself that your program is correct. We will discuss informal methods.

7. C++. We will cover the features of the C++ language that are needed.

Grading

You must expect to do a significant amount of work outside of class. If you do not have time to devote to this class, drop the class now. Students who do not put in the work can expect to fail the class.

This is a programming course, and students are expected to complete programming exercises. You may discuss your ideas with other students, but your programs must be your own work. Copying of programs will be considered plagiarism.

Grading will tentatively be as follows. Programming assignments will count 35% of your grade. There will be two midterm exams counting 18% each and a final exam counting 29%. Tentative cutoffs are 90% for an A, 80% for a B, 70% for a C and 60% for a D. Those cutoffs might be adjusted to account for overall class performance and the difficulty of the assignments and questions, but they will not be raised.

Important proviso. It is not possible to learn the material of this course effectively without actually ``getting your hands dirty'' and doing the programming. Accordingly,

in order to pass this course, you must receive at least a 60% grade in the programming assignments and at least a 60% grade in the exams.

Grading of exams

Grading of programs.

-Wall -Wshadow -Wpointer-arith

Programs will be graded according to the following broad criteria.

First, the program must compile without fatal errors.

A program that does not compile automatically receives a score of 0, regardless of how close to correct it might be.

To receive an A (90-100), a program should work on all of the test cases that I use. (You will not be given my test cases.) It should be well indented and well commented. Comments should be clear, correct and complete. It should be broken into fairly short, well-thought-out functions. Variable and function names should be sensible. It should follow all guidelines and requirements that have been set for the program. It should compile without warnings.

To receive a B (80-89), a program should work on typical test cases, though it might fail on more esoteric cases. It should be well commented and well indented, though minor problems might be present. It should be broken into fairly short, well-thought-out functions. It should mostly follow the guidelines and requirements that have been set for the program. The compiler should not report serious warnings that reflect mistakes in the program.

To receive a C, a program should work on at least some test cases. It must be reasonably commented and indented, though some comments might be misleading or incorrect. It should be broken into reasonable functions. It should make some attempt to follow the guidelines and requirements that have been set out for the program.

To receive a D, a program might not work correctly on any test cases, but the basics of the design must be present. The program should be acceptably well indented. I will not read a program that is very poorly indented. It should make some attempt to follow the guidelines and requirements that have been set out for the program.

Attempts on programs

You will be given two opportunities to do each program. After the first attempt, you will receive feedback, and can modify your program. If you miss the deadline for the first attempt, you will have only the second attempt.

Late submissions for the first deadline will not be accepted. Late submissions for the second deadline will be accepted with a 5 point penalty (out of 100) for each 24 hours that the program is late. Programs will not be accepted after the last day of classes unless you are informed otherwise.

I will provide some feedback on anything that is turned in as a first attempt. However, I do not guarantee to find all errors. You should certainly fix all errors that I point out, but that is not necessarily adequate. You are expected to fix those and any additional errors that might exist before turning in the second attempt.

If you turn in a high quality first attempt, then you can expect that the errors that I point out will be fairly complete, and your second attempt will consist mainly of fine-tuning. If you turn in a low quality first attempt, then you can expect that the feedback that I give will be quite incomplete, and you will have major work to do for the second attempt. If you do not turn in the first attempt, then you will have no feedback at all before turning in your second attempt.

Turning in programming assignments

Programs should be submitted by email to karl3510@cs.ecu.edu. Note the email address! All source files that are part of the program, including header files, should be attached to the email message. The body of the message should be empty. The subject of the message should have the following form.

3510 Assn k pass n your name

Include your name in a comment at the top of each file.

Asking questions by email

You are encouraged to ask questions about your programs when you are stumped, especially if you come up against a difficulty with the language. Send questions early, to leave yourself time to make progress after receiving an answer. Send questions to karl@cs.ecu.edu, not to karl3510@cs.ecu.edu.

If you have questions concerning programs, do not use a subject line that makes the inquiry look like a submission. Use a subject that begins

Question about ...