CIS 212 Fall 2005

Introduction to Computer Science III

Class Details

• Class Times
  • Lecture: MWF 1:00 - 1:50, 189 PLC
  • Lab: Lab is in B26 Klamath Computer Lab (basement of Klamath Hall),
    Wednesday 3:00 - 3:50
    Thursday 10:00 - 10:50

• Instructor: David Atkins
  • Office: Deschutes 358, phone 346-4413
  • Office Hours: MWF 11:00 - 12:00 and by appointment
  • Email: datkins@uoregon.edu

• Graduate Assistant:

  Tom Bulatewicz	Phone: 346-3473,   Office: Deschutes 245,   email: tomb@cs.uoregon.edu

• Reference Material

  Required Text: Java Software Solutions, 4th edition, by John Lewis and William Loftus, Addison Wesley, 2004.

  This is the required book for the course and we will refer to it as Lewis and Loftus or just L&L. The authors' book web site has the source code for examples used in the text.

  Another excellent introductory text is An Introduction to Object-Oriented Programming with Java, by Thomas Wu, McGraw Hill, 2006.

• Grading and Policy
  • Approximate grade weighting: Assignments 35%, Quizzes and class/lab participation 10%, Midterm 25%, Final 30%
  • CIS pre-majors must take CIS 212 graded; others may take it graded or P/NP.
  • Review the Do's & Don'ts from CIS 210. They apply to CIS 212 as well.

Course Objectives

• In this course you will continue your development as a computer scientist and programmer. In CIS 212 we will explore in more depth and detail the idea of Object Oriented Design and Programming introduced in CIS 210 and 211. The emphasis is on the concepts, but we will continue to learn more about programming as a useful skill for understanding and implementing those concepts. The course will cover more areas of programming: file and stream I/O, exceptions, inheritance, and programming graphical user interfaces. These topics will be explored in a Java language context, but our focus will be the abstractions that are independent of particular languages.

• CIS 212 is a required core course to become a CIS major.

CIS 212 Academic Honesty Policy

• All assignments turned in for the course must be your own work. Copying from other class members or other sources is not acceptable. If you collaborate with someone else on any assignment, you must indicate such on the work you turn in, and partial credit may be given.
• Academic honesty is expected and cases of suspected dishonesty will be handled according to university policy. In particular, copying someone else's work (including material found on the web) will not be tolerated. If solutions to assignments are obtained from outside sources, the source must be cited.
• You are also responsible for protecting your work. That is, you must take reasonable precautions to prevent your work from being copied. This means that if you store your assignment solutions on gladstone, the file permissions must be set to keep others from accessing your files. If you are working on assignments in the lab, you must remove any of your files on the lab machine before you leave.

Last updated 2005/10/17 18:46:41