• Course Description

  This course teaches the fundamentals of object-oriented programming using Java. Topics to be covered include:

  • Java applets and web pages

  • Java classes and interfaces

  • Data types and control flows

  • Java Abstract Window Toolkit (AWT)

  • Java Foundation Classes (JFC) and Swing

  • Java threading

  • Networking with Java

  • Object oriented design

  • Introduction to design patterns and frameworks

The prerequisite for this course is CSC 416 or equivalent.

• Course Materials
  • Primary Text: Object-oriented Software Development Using Java, by Xiaoping Jia. Addison-Wesley, ISBN 020135084X.
  • Reference Texts:
    
    • The Java Programming Language, Ken Arnold, and James Gosling. 2/ed. Addison-Wesley 1997.
      
      • The defeinitive reference of Java language by the creator of Java. No coverage on class libraries. 
    • The Java Class Libraries --- An Annotated Reference, Patrick Chan, Rosanna Lee. Vol. 1 & 2. 2/ed. Addison-Wesley 1997
      • Comprehensive coverage of all core Java class libraries. More extensive explanations of all classes and methods than the API documentation. Includes examples for every class. 
    • The Java Class Libraries: 1.2 Supplement, Patrick Chan, Rosanna Lee, Douglas Kramer. 2/ed. Addison-Wesley 1999
      • Same as above. Coverage on packages introduced in JDK 1.2 
    • Design Patterns - Elements of Reusable Object-Oriented Software, Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides, Addison-Wesley, 1995. 
      • The book that started it all. The origianl design patterns catalog. Commonly known as the Gang of Four(GoF) book. 
    • Fundamentals of Object-Oriented Design in UML, Meilir Page-Jones, Larry L. Constantine, Addison-Wesley, 1999. 
  • Online References: Note that on-line versions of these texts exist at http://java.sun.com/docs/books, so it is not necessary to purchase them unless you want a hard copy.
    • The Java Tutorial, Second Edition, by Campione and Walrath. Addison Wesley, 1998, ISBN 0-201-31007-4.
    • The JFC Swing Tutorial by Walrath and Campione. Addison-Wesley, 1999, ISBN 0-201-43321-4.
    • The Java Class Libraries, Second Edition, Volumes 1 and 2 by Chan, Lee, and Kramer. Addison Wesley, 1998. ISBN 0-201-31002-3 and 0-201-31003-1.
  • Software: (required) you will need access to:
    • Java 2 SDK Standard Edition (version 1.2.2 or greater), downloaded from Sun (it's free). Note that version 1.3 is the preferred version of the SDK for this class.
    • A Java 2 compatible Web browser is also helpful (preferably not Internet Explorer).

• Coursework
  1. Readings. Readings will be assigned from the primary text.
  2. Assignments. There will be 5 homework assignments.
  3. Midterm and Final Exam.

• Grading

  The grade breakdown will be as follows:

  Programming Assignments 40% Midterm 30% Final Exam 30%

  The grading scale will be determined by a curve. The cutoffs will be no higher than the following: 90-100, A; 80-89.99, B; 70-79.99, C; 60-69.99, D; 0-59.99, F. Plusses and minuses will be given at the high/low ends of each grade range (no A+'s or D-'s).

  Late policy: Absolutely no late assignments accepted.

  Policy on Working Together: You may feel free to discuss assignments with other students at a general level. This may include discussion of general issues, such as the types of data structures and control flow needed for the assignment. However, when it comes to actually writing code, you may not work with others. It has been my experience that if you write code together, you will be caught. Any violations of this policy will be dealt with very seriously.

• Plagiarism/Cheating

  The following paragraphs summarize university and school policy on plagiarism: Students in this course, as well as all courses in which independent research or writing (including writing computer programs) play a vital part in the course requirements, should be aware of the strong sanctions that can be imposed against someone guilty of plagiarism. If proven, a charge of plagiarism could result in an automatic F in the course and possible expulsion. The strongest of sanctions will be imposed on anyone who submits as his/her own work a report, examination paper, computer file, lab report, or other assignment which has been prepared by someone else. If you have any questions or doubts about what plagiarism entails or how to properly acknowledge source materials be sure to consult me. Submitting as one's own work, a computer program written by someone else or directly derived from someone else's program is considered plagiarism. (*A program is directly derived from someone else's program when the program is identical to someone else's program expect for minor changes such as reformatting, change of variable names, etc.) There is no such thing as the innocent submission of another's program. When sufficient proof exists, it merits the strongest of sanctions (course failure with notification of the student's college dean). Copying from another student's examination paper or allowing another student to copy from your examination paper is also a violation of DePaul academic standards. The sanctions described above apply.

• Incompletes

  The following paragraphs summarize university and school policy on incompletes: An incomplete is given only for an exceptional reason for not completing the course (e.g., death in the family, serious illness). Any such reason must be fully documented before an incomplete can be given. Any incomplete request must be approved by the Chairman of Computer Science. In particular, an incomplete is not given for any of the following reasons:

  • The company won't pay for the course if I get _____.
  • My grade point average will suffer if I get _____.
  • It's past the drop date and I'll have to pay for the course if I withdraw now.
  In the unlikely case that an incomplete is given, it must be made up with the original professor of the class. It is not possible to ``sit in'' on another faculty member's course and have that person give the grade to turn in. As a result of university and school rules concerning incompletes, incompletes in the School of Computer Science are rarely given.