Syllabus

CS 161, Introduction to Computer Science I

Winter 2001

Course Description: Introduction to object-oriented programming and other fundamental computer science concepts using the Java programming language. See also the detailed list of the learning objectives of this course.
Instructor: Dr. Burnett
Dr. Burnett's Office: Dearborn 217
Teaching Assistants: Laura Beckwith and Robin Abraham
Office Hours through March 16 (see announcements page for office hours during finals week): Monday: 8:00-9:00 am (Dr. Burnett's office)
Monday: 3:00-3:30 pm (Dr. Burnett's office)
Tuesday: 10:00-11:00 am (Laura Beckwith, Hovland Computer Lab)
Tuesday: 11:00-noon (Robin Abraham, Hovland Computer Lab)
Wednesday: 8:00-9:00 am (Dr. Burnett's office)
Wednesday: 3:00-3:30 pm (Dr. Burnett's office)
Thursday: 2:30-3:30 pm (Laura Beckwith, Hovland Computer Lab)
Thursday: 8:00-9:00 pm (Laura Beckwith, Hovland Computer Lab)
Thursday: 6:00-8:00 pm (Robin Abraham, Hovland Computer Lab)
Friday: 4:30-5:30 pm (Dr. Burnett's office)
Help in addition to office hours: Many short questions can also be resolved over email to Dr. Burnett, Laura, or Robin. In addition, if you are not able to make regular office hours, it is possible to set up an appointment with Dr. Burnett, Laura, or Robin. (Use email to request such an appointment at least a day in advance, as our schedules tend to be pretty full.) 
E-Mail: Dr. Burnett's email: burnett@cs.orst.edu
Laura Beckwith's email: beckwith@cs.orst.edu Robin Abraham's email: abraharo@cs.orst.edu
Course web site:  http://www.cs.orst.edu/~burnett/CS161/Winter01/
Assignments, announcements, clarifications, and other class materials are available at this site. Check every day for new announcements.
Prerequisites: CS 151, Introduction to C Programming (or equivalent programming experience).
MTH 231, Introduction to Discrete Mathematics (corequisite)
Textbooks: Java, Java, Java, Object-Oriented Problem Solving, Ralph Morelli, Prentice Hall, ISBN 0-13-011332-8, published in 2000. The required text. 
Core Java, Volume I, Cay Horstmann & Gary Cornell, Prentice Hall ISBN 0-13-081933-6, published in 2001. An optional text. Useful as a language and implementation reference. A good companion for this and future Java courses. 

Grading
Homework/Workshops (about 8) 10 %
Programs (about 5) 25 %
Quizzes (about 8, but you can omit 2 scores or absences.) 10 %
Midterm Exam 25 %
Final Exam 30 %
Programs:
  • Instructions will be posted to this web page for how to turn in your programs. 
  • You must have a C- or better average of all programs. Otherwise your course grade will not be higher than your program average. But see also "Quizzes" for the optional ability to omit one of these scores.
  • Programs are individual efforts: Sharing source code will result in an F (course). 
  • No late programs will be accepted. 
Homework/Workshops:
  • Homework/Workshop #1 may be turned in up to 48 hours late without penalty. 
  • No other homework/workshops will be accepted late.
Exams:
  • Closed-Book without notes or computational devices. 
  • Multiple choice and short answer with some programming. 
  • If you have a schedule conflict with the midterm or the final exam, it must be resolved with Dr. Burnett prior to January 22. 
Quizzes:
  • About 8 unscheduled quizzes will be held during recitation and/or lectures. 
  • Your quiz score will be the average of all but 2 of your quizzes. The 2 quizzes you can omit are your budget for sick days, unavoidable conflicts, just getting behind in your work, or etc. It is wise to save these up for genuinely unavoidable conflicts; you don't want to use them up too early. Or instead, if you wish, you may move (only) 1 of this "budget" of droppable scores to drop your worst program instead of your worst quiz.
General:
  • Anything without a name will be disposed of and will not be graded. 
  • You have 1 week from the day an assignment is returned to challenge the grade on any assignment. Do this by contacting your Recitation section's TA. If you cannot resolve it with the TA, contact Dr. Burnett within 2 weeks after the day the assignment was returned. 
  • Multiple pages must be stapled together or suffer a loss of 2n, where n is assignment number for that group. 

Academic Honesty Policy: Compliance with the Department policy on academic honesty is required (see http://www.cs.orst.edu/acad/policies/dishonesty.html for details. You are responsible for reviewing and understanding these restrictions. In general, source code and implementation details may never be shared. The department policy for violating academic honesty policies results in an F for the course.

To help everybody understand that we are very serious about this policy, here is the count of how many people have been reported to the Department Chair for academic honesty action so far in this course: 8