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

Professor: Chandra Kambhamettu

Email: chandrak at udel.edu

Office: room 420 Smith Hall

Office Hours: T (3:30pm-4:45PM), R(3:30-4:45PM)

Appointments: if you can't make to office hours, email me for an appt.

Phone: 831-8235

Teaching Assistants:

TA office hours are held in Smith 103.

name

email

lab sections

office hours


      Matthew Howard


     mdhoward@udel.edu


    020

11-12PM (T,Th)


      Timothy Armstrong


     timarmst@udel.edu


    021

4:30-5:30PM (M,W)


      Brett Bugglin-Borer


     bbborer@udel.edu


    030

10-11AM (M), 12-1PM (F)


      Mustafa Zengin


     zengin@udel.edu


    031

(xy)XYPM

Textbook: Python for Software Design: How to Think Like a Computer Scientist by Allen B. Downey.

Text Book link for pdf and html

Grade Breakdown

 

Percent of grade

Two midterms

10 + 10

Final

15

HWs/Quizzes + Participation

5+5

Labs

33

Project

11 + 11

Total

100

Final letter grade rule: Your final grade cannot be more than one letter grade higher than your exam average. This is to ensure mastery of fundamental skills.

If you have a disability that requires special accommodation, please contact me by email (chandrak at udel.edu).


NOTE:  Students are required to attend ALL lab sessions.  Assignments that are late are assessed a 10% per day late penalty, and after seven days they will not be accepted. Saturday and Sunday are each days. This policy is necessary because late assignments are burdensome for the TAs, both in terms of separate handling and separate time grading.

Participation grade will include lab attendance grade. This grade is marked by your TA based on each lab. Marks will be either P,A,E, or L for present, absent, excused (by the professor and in advance), and late. Students who depart early will also be marked L for "left early" for missing part of lab. More than 15 minutes late constitutes absence. Participation grade also constitutes your participation in the end of semester course evaluation. Homework3 will constitute a 1-page write-up of what you learned in the class, and this is the time to do Evaluations.


NOTE: Students are required to attend ALL lectures. I may make announcements in class that I do not post on the website. I will 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. If you show up to every lecture and sit quietly and attentively, you can expect to get ONE out of five possible points. To get five points, politely ask 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.

Your clicker grade is based on the number of times you respond out of the number of opportunities. It is not based on the quality of your answers, just the number, so please click.

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 have a style sheet posted on the class website. 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 sheet 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, homework, 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 perception 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 Official Student Handbook.

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.

Group or pair work is subject to the same rules, applied between groups or pairs.

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