CS 127: Data Structures, Fall 2002
Syllabus
Instructor Information
- Instructor: Dave Musicant
- Office: CMC 326
- Email: dmusican@carleton.edu
- Office phone: (507)646-4369
- Home phone: (952)882-8571 (before 10 pm, please)
Textbooks
- Data Structures and Program Design in C++, Robert L. Kruse
and Alexander J. Ryba, Prentice Hall, 1999.
- Practical C++ Programming, Steve Oualline, O'Reilly &
Associates, 1995.
Important Dates
- Exam 1: Wednesday, October 16 in class
- Exam 2: Wednesday, November 20 in class
- Last project due: 5 PM of last day of finals
Class Website
- http://www.mathcs.carleton.edu/faculty/dmusican/cs127f02
Your Grade
- Assignments: 45%
- Exam 1: 20%
- Exam 2: 20%
- Final Project: 15%
Working from Home
- We will be programming in C++, using the GNU g++ compiler version
2.96 under Redhat Linux. This will be set up for use in the Computer Science
labs. You may use other compilers at home if you wish, but you are then
responsible for making sure that your programs work under the compiler
that we have installed in the labs. I am glad to informally provide whatever
advice I can to help you get the software running on your own machine, but
home use is technically "unsupported."
Homework Policy
Each assignment will have a specific time for which it will be due, and
your electronic submissions are timestamped. An assignment turned in late
within one day of the due time will be docked 25%. An assignment turned
in later than one day of the due date but within two days will be docked
50%. An assignment turned in any time after this until the last day of
classes will be docked 75%. This policy is to protect the grader, but also
to encourage you to begin your work as early as possible.
Getting Help
- If you need help with a project, you can consult with other students,
talk to the prefector, ask a lab assistant, or come to me. I am happy to
answer your questions either in person or via email.
Collaboration, Cheating, and the Difference Between the Two
There are two different kinds of working together: collaboration and
plagiarism.
Collaboration
- Collaboration is good.
- You are encouraged to collaborate on ideas and program design.
- Programming is often a social effort, and there is much you can
learn by talking out the ideas in this class with each other.
- You are encouraged to talk to each other and share ideas.
- If a piece of your program utilizes someone else's idea, you
must give that person credit in program comments.
Plagiarism
- Plagiarism is bad. DON'T DO IT!
- Any programs that you turn in should be your work.
- Even if you work with someone else and share ideas, you must
still write your own program.
The following are examples of plagiarism.
- Taking someone else's program changing the name of the programmer
at the top, and turning it in.
- Taking someone else's program, changing the variables and comments
around, and turning it in.
- Finding a similar program on the internet, putting your name
at the top, and turning it in.
- Finding a similar program on the internet, changing the variables
and comments around, and turning it in.
I use software to discover plagiarism if it occurs, and will not hesitate
to notify the College if it does. I have prosecuted a number of students
for plagiarism.