Introduction to Computer Science II
Spring 2008
Class # 0203-112-01

Time: MWF  9:40 a.m. - 11:25 a.m.

Location: HR 235

Professor: David Galles
Office: HR 542
Office Hours:   T 10-12, R 2-3
                        Though these are my stated office hours, I am in my offices most of the day.
                        If my door is open (and it usually is), I am happy to talk with students.
                   

Phone: 422-5951
Email: galles@usfca.edu

TA: Erli Ling

Textbook:  Java Software Solutions, 5th Edition,  Lewis & Loftus

Prerequisites:
Computer Science 110, Introduction to Computer Science I

Test Dates:

Finals and Midterms:
Both midterms and the final will be closed notes.

Labs and Projects:
You must turn in hardcopy printouts of the source files for your projects, at the beginning of class on the due date. In addition, your source code needs to be in your subversion repository by the due date.

Late Policy:
Late projects will be accepted on the next class meeting after the due date for up to 75% credit. Projects will not be accepted later than one class meeting after the deadline. After 9:40 a.m. is considered late (In other words, do not skip class to finish an assignment.)

Grading:
Grades will be assigned on a straight scale, with Approximately

Students are expected to attend class. Topics that are discussed in class but are not in the text are fair game for the midterms and final.  While I will make an effort to make as much of the class material as possible available online, there will likely be some information that you will only be able receive by attending class.  Also, class time will give your valuable hands-on time to work on labs and projects.

Academic Honesty

(Academic Honesty Requirements adaptad from S. Rollins)

ALL assignments are to be completed individually unless specified, in writing, on the assignment. Academic dishonesty will NOT be tolerated. This is your warning! Students are encouraged to meet with me if they have questions regarding assignments or this policy. Students caught cheating will face severe penalty.

• Receive help from the professor and the TA.
• Discuss the requirements of the assignments, the meaning of programs, or high-level algorithms with other students or outside sources. If you have any doubt with respect to what is acceptable to discuss, speak with the professor first.

• Look at another student's code.
• Look at another student's solutions to homework problems.
• Receive unapproved help from an outside source including a tutor or a family member.
• Submit code which has, in whole or in part, been copied from any other source (including another student, a web page, or another text).
• Submit solutions to problems which have, in whole or in part, been copied from any other source (including another student, a web page, or another text).

• Any help from a source other than the professor, the lab assistant, or a TA must acknowledged. Example sources that must be cited are a parent, a family friend, and an outside tutor.
• If you wish to get a tutor in the course, speak with the professor.
• Any code submitted by a student must be completely original. No portion of a student's code may be copied from any other source (including, but not limited to, another student, a web page, or another text).

• Students caught violating the academic honesty policy will face severe penalty. A first offense will result in a 0 on an assignment and a report to the Dean's office.

1. Inheritance and Polymorphism
   
2. Interfaces
3. Exception Handling
4. Recursion
5. Linked Structures
6. Basic software design patterns, including iterators