Assignments & Grading Policy - EE 122 / Fall 2013

Assignments & Grading Policy - EE 122 / Fall 2013

Grade Components | Regrades | Exams | Homework Assignments | Programming Projects | Late Policy | Cheating

Grade Components

Homeworks 15% (3x5%)
Projects 40% (10% + 10% + 20%)
Midterm exam 20%
Final exam 25%

The course will be graded on a curve, with a mean of B (10% A, 15% A-, 15% B+, 20% B, 15% B-, 15% C+, 10% C). A+ is reserved for the best student (or perhaps two) in the class. The curve can shift up for an excellent class, as indicated by strong classroom interaction and outstanding effort; the TAs have significant input into this assessment. Graduate students and reentry students are not included in establishing the curve, but they will receive grades based on where they would fall on the curve. This is EECS Department policy.


For HWs, Midterm and Final exams

Any requests for grade changes or regrading must be made within one week of when the work was returned. To ask for a regrade, attach to your work a page that specifies:  

Without this page, your work will not be regraded. Even if you ask for only one problem to be regraded, your entire work may be regraded, so your score could decrease, stay the same, or increase.

For Projects

Each project would have its own regrade policy defined by the lead GSI for that project. This will be explained when the project is released. Regrade policies across projects may not be consistent.


There will be one midterm and one final. If you have a conflict with any of the exams, let us know as soon as possible to attempt to schedule a makeup. The exams will cover material from lecture, sections, the readings, and projects. In particular, you are likely to do poorly on the exams and in the course if you do not do your share of the homeworks and projects.

Homework Assignments

Homework assignments are due 1 hour before lecture (unless otherwise noted) on the due date.

Programming Projects

Projects will be graded by a script which will run the submitted code under a variety of conditions. These grades will be determined automatically from the results from the script.

Each project will have a core assignment and then a few suggested bells and whistles. The core assignment will be graded with an automated script. Extra credit can boost your project grade by up to 10%; 5% for the first bell/whistle, and 5% for the second. Although you are welcome to do more than two bells and whistles, you will only receive credit for two. Unlike the core assignment, there are no grading scripts for the extra credit; credit is binary (either you get it or you don't) and exclusively the decision of your TA.

Projects are designed to be solved independently, but you may work with a partner if you wish (but at most two people can work together). Grading will remain the same whether you choose to work alone or with a partner; both partners will receive the same grade regardless of the distribution of work between the two partners (so choose a partner wisely!). You may not share code with any classmates other than your partner. You may discuss the assignment requirements or general programming decisions (e.g., what data structures were used to store routing tables) - away from a computer and without sharing code - but you should not discuss the detailed nature of your solution (e.g., what algorithm was used to compute the routing table).

Late Policy

The policy is simple: no slip dates. If assignments are late, they are penalized as follows: < 24 hours late, you lose 10%; < 48 hours, 20%; < 72 hours, 40%. More than three days late, you can no longer hand-in the assignment.


It's OK to ask someone about the concepts, algorithms, or general approaches needed to do the homework and project assignments. We encourage you to do so; both giving and taking advice helps you to learn. However, what you turn in must be your own; copying other people's code, solution sets, Google safaris, or from any other sources is strictly prohibited. If you are unsure, then ask.

Some specifics:

One technique we will use to detect cheating is an automated system that performs comparisons across documents. It flags suspicious similarities, which we then inspect manually.

If elements of two assignments are determined to be clearly very similar (i.e., we believe that they were done together or one was copied from the other), then the course grade for all students involved in the incident will be reduced by one letter grade for the first offense, and to an F for the second offense. (“All” means both the copy-ers and the copy-ees). The grade for that assignment will also be reduced to 0. The reduction in grade may be taken without discussion or warning; the first notice you receive may be a letter indicating the penalty. In addition, for every instance, a letter to the Office of Student Conduct will be attached to your permanent record, and a copy will be placed in the CS division office. More serious cases of cheating (e.g., cheating on exams) will engender accordingly more severe penalties.

Note that you are responsible for not leaving copies of your assignments lying around and for protecting your files from unauthorized reading.