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.
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.
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.
- Attendance: At the beginning of each lab, the TA will take role. If you are late, it is your responsibility to inform the TA. If you show up late and do not let the TA know you are present, you will not receive a participation grade. If you are more than 10 minutes late, you will receive partial credit for participation (-1 point per 10 minutes late). If you are in doubt whether the TA has marked you as ‘present’, feel free to ask. If you cannot make it to your lab, let your TA know at least one hour in advance. You may make up the lab at another section during the same week, as long as you get permission from the head TA of the lab you wish to attend. You may only make up labs in this way twice.
- Grading: If you have any questions or concerns about lab grades or about a grade you have received on a programming assignment, ask the head TA. The TA can give input, make changes, or discuss the situation with the appropriate people if necessary.
- Collaboration: Unless specified otherwise, all lab assignments are solo projects. You may ask and answer questions with your peers, but do not share code or give answers. See the course policies on Academic Dishonesty for specifics. Helping your neighbor is encouraged. Doing the work for them will earn you both a 0.
- Persistence: Sometimes writing programs can be difficult. If you hit a dead end, ask for help. The more frustrating a program is to write, the more accomplished you will feel when you figure it out! If you need extra assistance outside of class, our dedicated Freshman Mentors have office hours throughout the week.
Programming projects (25% of total)
- Must be submitted electronically by 11:59 PM on the due date. One of your programs may be submitted up to 48 hours late with no loss of credit, but any subsequent late programs will not be graded. The submission web site can be found at http://engr.oregonstate.edu/teach.
- Must also be copied to your ENGR (or other OSU account) before the deadline. The reason is that many students submit the wrong files. This is not discovered by the TAs until after the deadline. At that point it is too late to get the correct files from the student UNLESS the student has them in his/her ENGR account. If you submit the wrong files and you have not copied your project to your ENGR account (before the project deadline), you will not be given an opportunity to resubmit, and you will get a zero for that assignment. We do NOT accept modification dates on personal computers as proof that the files were done on time.
- Must be implemented in Java. (Exceptions: The last program and any extra-credit programs may be written in C.) We recommend using the Eclipse development environment. Many other (some free) Java development environments are available for your own computers. Tutorial help will be scheduled in the CS Mentors' Lounge. When you submit a programming project, it's OK to submit only the source code files. Just be sure to submit all of the code that is required to run your project. If you wish, you may submit your project as a project file with the affiliated source code files.
- Each problem definition will have an associated set of grading criteria (including documentation standards). Programs are graded on a 50-point scale, typically distributed as follows:
4 Identification, program description, etc.
6 Method documentation
20 Verification (correctness, completeness and robustness)
15* Fulfills system requirements
5 Readability/style of code/output
* Programming assignments include a set of system requirements. These specify certain methods, structures, etc., that must be used in the solution (even if they might not represent the "best" way to solve the problem). Remember that the purpose of these requirements is to reinforce the concepts.
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.
- If you have a conflict for any of these exams, be sure to resolve it by the end of the second week of class
- Students are required to take exams on the date and time scheduled. If you are unable to attend at the scheduled time (for legitimate, verifiable reasons), you must schedule an alternate date and time in advance with the instructor. If you fail to obtain an excused absence for the exam, a makeup test will be given, but your score will be multiplied by the class median as a penalty.
- In serious situations or when the student is unable to contact instructors, the student or family members may contact the Office of the Dean of Students at 541-737-8748 for assistance. The Office of Dean of Students will provide notification of the absence to the student's instructors and the college head advisor. Students are reminded that providing false or misleading information to obtain an excused absence is a violation of student conduct regulations and may result in university student conduct action. See OAR 576-015-0020(6) at website http://oregonstate.edu/admin/stucon/regs.htm
- If your average for the exams is F, your grade for the class will be F, regardless of scores in other categories.
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.
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.
Your term total will be calculated using the weights described above, and converted to a letter grade using the following scale:
|>= 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-|