CSE132 Late Policy

Success in CSE132 depends critically on keeping up with the assignments. At the same time, we don't want you to be stressed out over deadlines. With this in mind, the the following late policy has been established. Please read it carefully so that you understand your options. Exceptions to this policy may be granted only in the case of a documented illness or other extenuating circumstances.

Exams and Quizzes Exams and quizzes must be taken at the scheduled time. Quizzes may not be announced in advanced so class attendance is important. If you anticipate that you must be away from campus on the day of an exam, you should notify the instructor by email at least one week in advance of the date of the exam. Include in your email the reason for the anticipated absence and a list of alternative times when you could take the exam. If you are ill on the date of an exam, you should provide the instructor with documentation of the illness and arrange for a make-up exam date as soon as possible. In any case, you must not discuss the contents of an exam with anyone between the time it is given and the time you take the exam.

Lab Assignments

You should complete each lab assignment by the beginning of your lab section on the due date. (If the CEC computer facilities are unavailable for an unusually long period, the deadline or grace period for an assignment may be extended at the discretion of the instructor. However, occasional brief outages are to be expected and will not result in an extension.)

When a lab or design is due, you will have a lab conference with a TA during your lab section. At the design conference, you will present your design and receive feedback from the TA and another team. A grade will be assigned based on the completeness, thoroughness, and quality of your design. Two things happen at the implementation conference: (1) you demonstrate your working program, and (2) you go over a printed copy of your code. The TA will write a demo grade on your lab. Note that the demonstration is a large part of your grade on each assignment, and there are no second chance demos so you should test thoroughly before giving a demo.

If serious deficiencies are found during your conference, you will have one week to improve the implementation before turning it in for grading, with a penalty for lateness determined based on how deficient the design implementation was at the time of the conference. In these cases, both the marked-up version from the conference and the final version of the code must be turned in. The penalty may be different for different team members, depending upon the situation.

If necessary, you can arrange for conferences to be held early during TA consulting hours, but this is not ideal since part of the conference will generally involve interaction with another team.

If your conference occurs late, you will receive a 10 percent late penalty per calendar day. So, if an assignment worth 20 points is due on Friday, you will incur a 6 point penalty if you turn it in on Monday. If you finish an assignment late, a TA will not necessariily be available to hold a conference with you that day. It is your responsibility to schedule conferences for late labs. Nothing will be accepted more than one week after the conference date specified for that assignment.