This syllabus is subject to change; check weekly for new information.

Professor: Terry Harvey

Email: tharvey at udel.edu

Office: room 408 Smith Hall

Office Hours: (Subject to change) Tues 11:00 - 1:00, Fri 11 - 1
Appointments: if you can't make office hours, email me for an appt.

Phone: don't call, email!

Email will get a faster response for questions, appts, etc. Only use the phone for emergencies when you have no access to email (e.g., "I am in Mesopotamia and will miss today's exam.").

Teaching Assistants:

TA office hours are held in Smith 103.

Rich Burns email: burns at udel

Useful Links

Important dates, subject to change:

? See wiki calendar!
?5/21? Final Software Demonstrations

Grade Breakdown

  Percent of grade
Journal 15
Quizzes 10
Semester Project (all parts) 55
Participation 20
Total 100

Grade Scale

Number

100-93

93-90

90-87

87-83

83-80

80-77

77-73

73-70

70-67

67-63

63-60

<60

Letter

A

A-

B+

B

B-

C+

C

C-

D+

D

D-

F

If you have a disability that requires special accommodation, please contact me by email (tharvey at udel.edu) during the first week of class.


Field trips and work with CCCS are an important part of this course. If for any reson you are unable to make one or more field trips assigned, you must get the professor's permission to do an alternate assignment.


NOTE: Students are required to attend ALL lectures. I may make announcements in class that I do not post on the website. I may put lecture slides on the web, but these are not a substitute for class notes. Many classes will have no lecture slides because we will be coding. It is your responsibility to get the notes from any lecture you miss from another student (not your instructor, and not your TA). Lecture material is critical for projects and exams, and useful everywhere else.

Your participation grade is based (surprise!) on your participation in lecture and on field trips. If you show up to every lecture and sit quietly and attentively, you can expect to get ONE out of 20 possible points. To get all points, participate in discussions and answer at least one question in every class. If you are unable to do this because of extreme shyness, see me during office hours in the first two weeks of the semester.

A Note About Programming Conventions


Every organization that writes code (and does it well) subscribes to a set of conventions for naming variables, commenting, formatting, etc. 

Our class will follow the Python style guide. You must adhere to the specifications of the style sheet to receive full credit for an assignment.

"What happens if we don't do this?"

Horrible things happen. A program that works perfectly but does not have the features described in the style guide cannot receive a grade higher than 60%, even assuming it is flawless in every other way.

Your Right to See and Question Your Grades

Students have a right to receive their graded assignments in a timely fashion. That said, remember that your TAs are students too, and have deadlines in other courses. The instructor and TAs will endeavor to get all assignments back to students within ten days of the submission date. If this date is not met, please bring it to the attention of the instructor.

All students have the right to know how their grades are calculated, and if any student believes a mistake has been made, it is up to the student to contact the grader to discuss it within ONE WEEK of the return of the assignment. Contact the TA first for labs and projects. If you are not satisfied after discussing the grade with the TA, then you may bring it to the instructor. Bring exams directly to the instructor.

The grade percentages are on this syllabus. Please use them to calculate estimates of your semester grade. This class typically has little or no curve.

Academic Honesty

I expect you to observe the highest ethical standards, avoiding even the appearance of ethical compromise.  You are expected to do your own work unless explicitly instructed otherwise.  This includes programming projects, labs, quizzes, and examinations.  All violations of academic honesty will be handled according to University policy.

In addition, copying another person's work without proper acknowledgment is plagiarism, a serious offense, and the one most common to computer science courses.  Anyone that aids another student with work that is expected to be done without collaboration is as guilty as the person who seeks help. Both will be prosecuted. It is strongly recommended that you familiarize yourself with the University's Policy of Academic Dishonesty found in The Student Guide to University Policies.

Any student who in any way facilitates another student's access to someone else's classwork is cheating, whether the classwork is written, electronic, verbal, or any other form.

Furthermore, there have been rare instances of people claiming that their work was stolen. In these cases it is very hard to determine if the person gave their work to someone else, or if it was taken without their permission. If there is any doubt, I will always assume that the work was deliberately shared. It is thus your responsibility to safeguard your papers, your passwords, your computers, and any other means by which your work can be copied.

All students are required to be familiar with these examples: Academic Honesty Examples