CMPS 109: Advanced Programming - Winter 2000

Java

This course will teach objected-oriented programming using, Java.

Instructor Information

Office: AS 239

Hours: Tu/Th 10-11am, Wed 3-4pm

E-mail: charlie@cs.ucsc.edu

Latest grades

I believe I'm all up to date. Let me know if you see something missing.

current database as of 3-8-00

General Lab Information

This section contains general information about how to run the tools you will need for this class.

TA's and Tutors

This section contains information about the lab times and when the TA is available.

Lecture Supplements

This section contains additional information from the instructor to supplement the lectures. Materials will be added here as they become necessary.

FAQ's (Frequently Asked Questions): See if your question is here!

This section contains questions pertaining to programming which students frequently ask.

Required Text:

Java by Dissection, by Ira Pohl and Charlie McDowell.

Evaluation:

Weekly programming assignments (20%).
Bi-Weekly quizzes (40%).
Final (40%).

A minimum of 50% on all three aspects of the grade is necessary but not sufficient to pass this class. This means, if you receive less than 50% on any one of the three parts (hw, quizzes, final), you will not pass, however, just because you score at least 50% on each part does not imply that you will necessarily pass. For example, someone that scored 51% on each of the three parts would almost certainly, NOT pass. The policy is intended primariliy to prevent students from "blowing off" the homework because it only counts 20% of the grade. You cannot pass this class if you do not do the homework.

Working Together: I am trying something different this quarter. It has been observed that in the "real world" programmers rarely work alone. In fact some recent studies suggest that the most productive work arrangment is for two programmers to work side-by-side, with one literally looking over the shoulder of the other at all times. Consequently, I am going to allow you to work either individually or in pairs. You may make your selection (a pair or alone) for each assignment, however, you must announce your decision to me and then stick with it for that assignment.

Either as an individual or as a pair, you should treat the programs as take home exams. You may freely give and receive help (from outside your pair) with the computer facilities, editors, UNIX, debugging techniques, the meaning and proper use of Java constructs, etc.. It is also perfectly permissible to discuss general approaches and algorithms with your classmates. However, copying any part of another person or team's program, or allowing your program to be copied is not permitted. A program will be in use to detect copying. If you have any questions on this important point, please see me.

Academic Dishonesty: Any confirmed academic dishonesty including but not limited to copying programs or cheating on exams, will constitute a failure of the computer ethics portion of this class and result in a no-pass or failing grade.

Homework: Turn in homework by using the submit procedures. It will not allow late work. Late work will not be accepted or graded. The program should be submitted in whatever form it is in - grading is done not only on working code. Homework is graded in terms of it being done in a good style, being correct, being concise, being readable, and being efficient.

Quizzes: There will be a quiz every other Thursday.

Syllabus

Date	Topic	Reading
January 4	Basic Java Syntax	Chapters 2-4
January 6, 11, 13	Objects	Chapter 6
January 18, 20	Arrays	Chapter 5
January 25, 27	Inheritance	Chapter 7
February 1, 3	GUIs Part I	Chapter 8
February 8, 10	GUIs Part II	Chapter 9
February 15, 17	Reading and Writing Files	Chapter 10
February 22	Exceptions	Chapter 11
February 29, March 2	Concurrent programming I	Chapter 13 (13.1-13.4)
March 7, 9	Concurrent programming II	Chapter 13 (13.5-13.8)
March 14	TBA	TBA

This page maintained by Charlie McDowell. Email regarding this site.