Policies

You and your instructor are bound by the Stevens Honor Code.

Students are responsible for reading and understanding the course policies in these web pages and for announcements made in class and in the course email list.

You will be permitted to use the textbook and course notes for programming assignments. During exams, you are not permitted to use notes, books, computing or communication devices unless a different policy is specifically announced by the instructor.

During lecture/recitation, please refrain from using mobile phones or otherwise being impolite. Use of notebook computers is appropriate at times but can also be disruptive or distracting. The instructor reserves the right to say notebooks (and similar devices like PDAs) must be put away.

Coursework and grading:

Programming is learned by doing. The main focus of your work will be on programming assignments. Assignments will normally be structured in two parts:

• Lab part, to be completed and graded during lab. Sometimes you will be allowed or required to work in groups in the lab (we'll discuss grading for groups later).
• Homework part, to be completed individually, on your own time. Usually the homework will be a program that you started designing and implementing during lab.

There will be short, unannounced quizzes in class: The purpose is to motivate attendance and to help both you and your instructor gauge your progress.

The course score is a weighted average of the following categories, with the additional requirement that to pass the course you must score at least 60 in at least three categories.

• programming assignments 25%
• pop quizzes 10%
• first exam 10% (the registrar calls exams ``quizzes'')
• second exam 15%
• third exam 15%
• final exam 25%

The lowest two quiz scores will be dropped. Letter grades are assigned on the usual basis: at least 90 for A, at least 80 for B, etc.

How to prepare for quizzes and exams: It's obvious--attend class, do the reading, and especially do the programming assignments, carefully and thoughtfully. The purpose of programming assignments is not to turn them in on time--the purpose is to become a skilled programmer and get good grades on the exams. Get help from the TA and instructor and work hard.

There are no make-ups for quizzes or exams. The only possible exceptions are in the case of death in the student's immediate family or near-death experience of the student; advance notice is required.

Policies for programming assignments:

Except when groups are explicitly allowed, work must be done individually. You are encouraged to discuss the problems with your classmates but you must not share details of the solutions. If you are unsure whether you have shared too much, discuss the situation with the TA or instructor; it is your obligation to avoid even the appearance of cheating.

About timeliness. We all have trouble meeting deadlines, and as a near-beginning college student you are confronted with many difficult deadlines. But homework doesn't get easier to do if it's late. Doing it on time helps you avoid falling behind when it comes to subsequent lectures and quizzes. Hence the following strict policy for homework:

how late	points deducted (out of 100)
0	0
up to 1 day	25
up to 3 days	50
3-7	75

For lab grade the policy is simple: no credit for late, no make ups.

Adjustments:

Grades are based on the usual scale (90 for A, 80 for B, 70 for C, etc). The instructor reserves the right to give a higher grade than your course score, if your performance on later assignments and exams is very strong.

Your lowest quiz score will be dropped.

Your lowest assignment score will be dropped.

If after the third exam your preliminary course score is at least 80, you may choose to skip the final exam and keep that course score.