CSCI 2830-Section 002
Special Topics: Programming in Java
Spring 1998
3 credit hours

January 13, 1998


On the first day (January 13) we will meet in ECCS 128 at 9:30, then move to the "SimLab" in ITLL (bottom floor, NE corner).


The goal of the course || Prerequisite || Instructor || Textbook || Time and location || Grading Policies

The goal of the course

The goal is for you to


Prerequisite

CSCI 1300, or comparable experience.


Instructor

Karl Winklmann, ECOT 720, ph. 492-6380, email address karl@cs.colorado.edu. (Email that might be of general interest should not go to me but to the Hypernews Page of the course, to be established.) My office hours are Tuesdays, 2:30-3:30 and Thursdays, 2-3, and by appointment. You can also catch me usually before and after class in the lab.


Textbook

[This is the 2nd edition of the book. I had posted information about the first edition earlier. The bookstore said they would get the second edition.]

Patrick Niemeyer and Joshua Peck, Exploring Java, 2nd Edition, O'Reilly. ISBN 1-56592-271-9.


Time and location

TTh 9:30-11:20, location a computer lab TBA. Typically there will be a mixture of lecture and lab work, first getting an explanation of a concept and then trying it out.


Grading policies

Your grade will be based on a semester project, which will have its intermediate stages and their due dates. You can earn a maximum of 105 points, broken down into ...

15 points for the quality of a first presentation of the design
15 points for on-time delivery of intermediate stages
15 points for the content of the final product (i.e., what it does)
15 points for the quality of the presentation of the final product
15 points for helpful contributions in class
15 points for the style of the implementation
15 points for how suitable some of your software is for use in other projects

We will freely use each other's software, but you need to spell out what it is that you wrote. When you claim a piece of software as yours, you must have written it by yourself, without copying lines of code from someone else. If you get caught violating this rule you'll get an F. (In real software life you'd get sued.)

A total of 90 points and above will get you an A, 87 an A-, 84 a B+, 80 a B, 77 a B-, 74 a C+, 70 a C, 67 a C-, 64 a D+, 60 a D, below 60 an F.

There will be no extra credit work.


Copyright © 1998 Karl Winklmann

Last edited (or copied to this place) at 8:09 AM, Tuesday, January 13, 1998.