Course: CMSC 10600 Fundamentals of Computer Programming II (C++) Instructor: David Press dmp@cs.uchicago.edu Class URL: http://www.classes.cs.uchicago.edu/archive/2004/summer/10600-1/index.html Lecture: MWF 1:30-3:20 Ry 251 Office Hours: TTH 1:30-2:30 Hinds 026
This course is an introduction to computer programming using the object-oriented language C++. We emphasize design and algorithm construction. Topics include complex types, iteration, recursion, procedural/functional/data abstraction, classes, methods, inheritance and polymorphism.
Title: Absolute C++ Author: Walter Savitch Publisher: Addison Wesley, 2002
Since the best way to learn programming is by doing it, grading for the course will be based on programs assigned each class and on a final project.
Percentage Component 75% Homework assignments 25% Final Project
Date Lecture 07/26 1 07/28 2 07/30 3 08/02 4 08/04 5 08/06 6 08/09 7 08/11 8 08/13 9 08/16 10 08/18 11 08/20 12 08/23 13
Date Homework Due date Solution 07/26 1 07/28 Sol 1 07/28 2 07/30 Sol 2 07/30 3 08/02 Sol 3 08/02 4 08/04 Sol 4 08/04 5 08/06 Sol 5 08/06 6 08/09 Sol 6 08/09 7 08/11 Sol 7 08/11 8 08/13 Sol 8 08/13 9 08/16 Sol 9 08/16 10 08/18 Sol 10
[The following is due to Stuart Kurtz]
The University of Chicago is a scholarly academic community. You need to both understand and internalize the ethics of our community. A good place to start is with the Cadet's Honor Code of the US Military Academy: "A Cadet will not lie, cheat, or steal, or tolerate those who do." It is important to understand that the notion of property that matters most to academics is ideas, and that to pass someone else's ideas off as your own is to lie, cheat, and steal.
The University has a formal policy on Academic Honesty, which is somewhat more verbose than West Point's. Even so, you should read and understand it.
We believe that student interactions are an important and useful means to mastery of the material. We recommend that you discuss the material in this class with other students, and that includes the homework assignments. So what is the boundary between acceptable collaboration and academic misconduct? First, while it is acceptable to discuss homework, it is not acceptable to turn in someone else's work as your own. When the time comes to write down your answer, you should write it down yourself from your own memory. Moreover, you should cite any material discussions, or written sources, e.g.,
Note: I discussed this exercise with Jane Smith.
The University's policy, for its relative length, says less than it should regarding the culpability of those who know of misconduct by others, but do not report it. An all too common case has been where one student has decided to "help" another student by giving them a copy of their assignment, only to have that other student copy it and turn it in. In such cases, we view both students as culpable and pursue disciplinary sanctions against both.
For the student collaborations, it can be a slippery slope that leads from sanctioned collaboration to outright misconduct. But for all the slipperyness, there is a clear line: present only your ideas as yours and attribute all others.
If you have any questions about what is or is not proper academic conduct, please ask your instructors.