CS 162  Introduction to Computer Science II  (Home)
Course Policies and Expectations          Spring 2012

Preparation and Attendance

Please be on time for lectures with reading assignments completed.

Please be on time for lab sections with any assigned preparation completed.

Some of the material covered in lectures is not covered in the textbook, and much of the material in the reading assignments will not be covered in lectures.  Most of the information required for completing projects and other assignments will be presented in lecture and/or lab.  All of these sources are covered on exams.  Do not expect a private tutorial if you skip lectures and/or labs.

A student who is absent from class due to illness or family emergency should notify instructors as soon as possible (by phone, e-mail or in person). Notifying instructors and discussing missed work is the responsibility of the student.


You are expected to participate in lecture/lab discussions.  You are encouraged to ask questions in lecture/lab, as this can often benefit the entire group.


Accommodations are collaborative efforts between students, faculty and Disability Access Services (DAS). Students with accommodations approved through DAS are responsible for contacting the faculty member in charge of the course prior to or during the first week of the term to discuss accommodations. Students who believe they are eligible for accommodations but who have not yet obtained approval through DAS should contact DAS immediately at 737-4098.

Academic honesty

Programming assignments present unique challenges for graders.  It is often difficult for a grader to distinguish between legitimate help and plagiarism.  Therefore, it is sometimes possible to get a good score without really understanding what you have handed in.

Honesty is absolutely essential in order for learning to take place.  It will form the foundation of your professional integrity in your career.  In homework and programming assignments,

If you are having trouble with an assignment, you are encouraged to discuss it with other students, TAs, the instructor, or anyone else who will listen, but don't just have someone else tell you how to solve the problem!  If other students ask you for help, don't just let them copy your work!  It is possible to discuss problems without plagiarizing.  One of the best methods of debugging is to explain your solution to someone else.

If you get help from, give help to, or work together with someone, you must (in the program header block) list that person as a collaborator and describe the help.  Programs that are very similar will be subjected to review unless both programs indicate that they were produced collaboratively. We use plagiarism-detection software check your code against the code from other students. It is quite sophisticated and can easily see through variable name changes and formatting differences.

If you get help from printed or online sources, you must cite your references.

If you are found in violation of any of the above policies, whether you are the giver or receiver of help, you will receive a zero on the assignment or fail the course (Instructor's discretion). The academic dishonesty charge will be documented and sent to your school's dean and the Office of Student Conduct. The first offense results in a warning; the second offense results in an academic dishonesty charge on your transcript, a disciplinary hearing, and possible expulsion.

The bottom line is:  Each student is expected to understand all aspects of the programs s/he submits for credit.

Evaluation criteria

Homework/Classwork assignments (10% of total) are graded for completion.  These are assigned to help you prepare for projects, quizzes, and exams.  These assignments are typically given as individual homework assignmnets or as group in-class assignments.  They are often the basis for discussions in lab sections.  10 - 12 assignments will be given, but the lowest one or two of these scores will be dropped.  This is intended to cover all kinds of reasons and excuses for missing an assignment, so missed assignments may not be made up.

Labs (10% of total) Be sure to attend the lab section in which you are enrolled.  The TAs will assign a score for each lab, based mostly on participation.

Lab Policies

Programming projects (25% of total)

Quizzes (15% of total) may be given in class or in lab.  These quizzes are all announced (no surprises), and will usually comprise short-answer type questions.  Four quizzes will be given, but the lowest of these scores will be dropped.  This is intended to cover all kinds of reasons and excuses for missing one quiz, so missed quizzes may not be made up.

Exams, midterms (20% of total) and final (20% of total) will be given as scheduled on the course calendar.  The exams will contain about 80% objective questions.  The remaining questions will involve writing methods or short code fragments.

NOTE: Extra credit may be available in any of the evaluation categories, but excess points in one category can not be transferred to another category.

Score Posting

Scores will be posted as soon as possible after each evaluated activity.   It is the student's responsibility to check the score posting frequently and report any errors. The deadline for reporting an error is 2 weeks after the score is posted.

Grading scale

Your term total will be calculated using the weights described above, and converted to a letter grade using the following scale:

Percentage Grade
>= 92.5 && <= 100.0 A
>= 89.5 && < 92.5 A-
>= 86.5 && < 89.5 B+
>= 82.5 && < 86.5 B
>= 79.5 && < 82.5 B-
>= 76.5 && < 79.5 C+
>= 72.5 && < 76.5 C
>= 69.5 && < 72.5 C-
>= 66.5 && < 69.5 D+
>= 62.5 && < 66.5 D
>= 59.5 && < 62.5 D-
< 59.5 F