CISC 470/670  -   Programming Languages  -   Spring 2005

Instructor: Daniel Chester	TA: Xiang Cao
Office: Room 205, 77-79 E. Delaware (The green house next to East Hall)	Office: Room 115B, Pearson Hall
Hours: M 5:00pm-6:00pm, F 4:00pm-5:00pm	Hours: W 1:00pm-3:00pm
Phone: 831-1955
Email: chester@cis.udel.edu	Email: cao@cis.udel.edu

Textbook

Web Page

http://www.cis.udel.edu/~chester/courses/670.html

Course Description

Course Objectives

Prerequisites

Recommended Background

Topics (tentative)

Grading

• two projects 26%


• assignments 26%


• two midterms (March 23, May 18) 48%


• NO FINAL EXAM

Policies

• THE IMPORTANCE OF ATTENDING CLASS: You must attend class if you plan to pass the course. No lecture notes, homework assignments or project assignments will be posted on the class web page. All homework and project assignments will be given only in class; they will not be posted on the class web page and I will not tell what the assignments are in response to an email or telephone call.

  All homeworks and projects must be given to me in class. They will not be accepted if you send them by email, put them in my mailbox or under my door, or email them to the TA, put them in his mailbox or give them to him personally.

  This policy will be strictly enforced unless I announce otherwise, to deal with special situations. Individual exceptions may be made only in extreme and verifiable circumstances.

• Projects and assignments are due at the beginning of class on the due date.
• All work turned in must be your own; it must not be copied from another student's work, nor from a book or other source. YOU ARE EXPRESSLY FORBIDDEN TO SHOW YOUR PROGRAM CODE OR WRITTEN ASSIGNMENTS TO OTHER STUDENTS UNTIL BOTH OF YOU HAVE TURNED IN YOUR RESPECTIVE WORK FOR GRADING. You may consult with others about conceptual problems. If you need someone to look at your code for debugging, see the TA, me, or someone not taking this course. Do not show your code to another student taking this course.
• All programs must be well documented. A program is well documented if it is readable and clear. This usually means that function definitions should be short. Function and variable names should be chosen to make definitions clearer. Insert one comment ahead of a function definition that explains briefly what the function does and what the input parameters are expected to be. Insert other comments only where the definition might not be clear to a person who knows C/C++/JAVA but is not familiar with the algorithm you are using. Note that too many comments can lessen the readability of your program, clumsy algorithms can lessen the readability of your code, and output can be ``correct'' but be produced by a combination of errors that cancel each other out. Points will be taken off for each of these cases.
• Written assignments will not be accepted after their solutions have been presented in class.
• If you can't come to scheduled office hours, please send me email; I'd be happy to schedule a meeting at some other mutually-agreed upon time.