You should attend discussion sections and get to know your TA.
TA's will determine the grades of students near the borderline.
The course will be graded on a curve, with a mean of B, and a median of
B+. Graduate students and reentry students are not included in establishing
the curve (to be fairer to undergraduates), but they will receive grades
based on where they would fall on the curve. This is EECS Department policy.
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 will be regraded.
Thus, you are not guaranteed that your score will necessary increase;
your score may decrease, as well.
- The problem(s) you want to be regraded
- For each of these problems specify clearly why do you think the
problem was misgraded.
There will be one midterm and one final. If you have a conflict with
any of the exams, let us know, and we will schedule a makeup. All exams will
be closed book, and will cover material from lecture, sections, the
readings, and the project. In particular, you are likely to do poorly on
the exams and in the course if you do not do your share of the work on the
Homework assignments are due 10 minutes before lecture on the due date.
Submit homeworks to the drop box labeled "ee122" outside of 275 Cory Hall
You will form groups of at most 2 people to do the programming projects.
You can work by yourself, but we do not recommend it because the projects
will be significant work for two people.
The TA for your section or your partner's section will grade all phases
of your project. The TAs have been instructed to grade in part on design
and implementation style and to be increasingly strict about this as the
semester proceeds. In other words, it is not enough to get a working
solution; you must implement the solution in a clean way that would simplify
making further enhancements. (Several employers in the area have said
that many of our graduates don't know how to program well -- it will really
benefit you in the long run to work on your software engineering skills.)
Although we will attempt to ensure that the grading criteria are applied
uniformly, there may be slight variations between sections. However, we
believe that any decrease in fairness will be outweighed by the benefit
of continuity in the sections in teaching the course material.
We will use flexible slip dates for the homework and programming assignments.
Each student is given an automatic extension of 4 calendar days. You can
use the extension on any assignment during the semester (in increments
that are rounded up to the nearest integer). For instance, you can hand
in one assignment 4 days late, or each of four assignments 1 day late.
For project assignments, the slip time will be deducted from each team
member's remaining slip time. This should let you schedule due dates around
the due dates for other courses.
After you have used up your slip time, any assignment handed in late will
be marked off 20% per day. Extensions will absolutely not be granted.
It's OK to ask someone about the concepts, algorithms, or approaches
needed to do the project assignments. We encourage you to do so; both giving
and taking advice will help you to learn. However, what you turn in must
be your own, or for projects, your group's own work; copying other people's
code, solution sets, or from any other sources is strictly prohibited.
The project assignments must be the work of the students turning them
in. We will punish transgressors severely.
The fine print:
We will use an automated system for detecting cheating:
it performs a pairwise comparison of all homework assignments with all
others, and reports any suspicious similarities. The TAs and/or instructor
will check any such similarities. If two assignments are determined to
be obviously very similar (i.e., we believe that they were done together
or one was copied from the other), then the course grade for all the 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-er
and the copy-ee). The letter grade for that assignment will also be reduced
to 0. The reduction in grade will be taken without discussion or warning;
the first notice you will 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, such as copying someone
else’s work without their knowledge, cheating on exams, etc. will probably
result in the person cheating receiving an F, and having a letter placed
in their permanent file in the Office of Student Conduct and in the CS division
office. Note that you are responsible for not leaving copies of your assignments
lying around and for protecting your files. You must set up your files and
directories so that they are protected from anyone other than members of
your group reading them.