HCC bookstore on-line

1. Understand and build applications and applets using advanced object-oriented programming concepts (such as design patterns and basic UML)
2. Understand and use advanced Java features including reflection, annotations, weak references, enums, and autoboxing and unboxing
3. Understanding Exceptions, Assertions, and testing (JUnit)
4. Understanding and using generic collections
5. Understand how to construct internationalized applications and applets
6. Understand and build advanced graphic user interfaces (including 2-d graphics and advanced layout techniques)
7. Understand multithreading concepts and build multithreaded applets and applications
8. Work with files and I/O, including XML files (including DOM, SAX, and XSLT)
9. Understand how to digitally sign an applet and applications, and how to grant extra privileges to an applet, and other features of JAR files
10. Understanding deployment issues and the use of Java WebStart
11. Describe J2ME concepts and components
12. Understand how to use databases from a Java program
13. Printing from a Java application
14. Understand basic networking concepts and building client-server (web based) applications with servlets and Java Server Pages (JSPs), JavaBeans, and Remote Method Invocation (RMI)
15. Understand issues and basic design of enterprise applications using Java EE (including such concepts as web-, business-, and EIS- tiers, fat and thin clients, grids and clusters, WARs and EARs, etc.)
16. Understand and describe enterprise technologies and related services and protocols, including JNDI, JMS, JavaMail, and Web Services ( UDDI, SOAP, and WSDL)

Grading scale:  A=90-100,   B=80-89,   C=70-79,   D=65-69,   F=0-64
(Or you can elect to audit the class during the add/drop period.)

• No makeup exams will be offered without the prior approval of the instructor.
• Exams will be closed book and closed note multiple choice exams.  While the exams are non-cumulative, each does build upon knowledge acquired earlier.  Exams are based mostly upon material presented in class however some questions may be from assigned readings (the textbook and on-line resources).
• Exams will never cover material not yet discussed in class.  Should the class fall behind the course schedule some topics shown on the syllabus due for an earlier exam will be tested on the following exam instead.
• Regular attendance is imperative for the successful completion of this class.  The textbook and on-line resources should be considered as required course supplements; in other words the course is not based on the text.
• All phones, pagers, and beepers must be turned off during class time, except with prior permission of the instructor.  No food or drink is permitted in HCC classrooms.
• Attendance will be taken within 5 minutes of the start of class; after 4 absences and/or lateness, the student will lose 2 points off the final grade for each additional occurrence.
• If you miss a class you are still responsible for the material covered in that class.  All students should exchange contact information (name, email address, phone number) with at least one other student in the class.  If you must miss a class, you should then contact another student and request they take class notes for you.  (Note Campus Cruiser has email and discussion board areas for our course.)
• Credit for class participation includes attendance, preparedness, and adding to class discussions by asking questions and participating in discussions.  Playing computer games, surfing the Internet, or working on assignments for this or other classes during class time will lose you credit.
• Additional time outside of class will be required.  For typical students an average of between 6 and 10 hours each week outside of class are required for preparation, practice, and projects.
• Students are expected to prepare for each class by completing all reading assignments, reviewing examples and model solutions provided, and practicing outside of class.  This is important — you can't learn a skill such as Unix only by attending class and reading books.  You must practice several hours a few days each week!  If you won't have enough time available, consider auditing the course.
• Students are expected to check the class website regularly.  Any syllabus changes, class cancellations, project assignments, and homework assignments are announced in class and posted to the website and the RSS feed for this class.
• Working together on individual assignments is considered as cheating!  Turning in someone else's work without giving them credit is also considered cheating (plagiarism).  Cheating will result in an automatic F (zero) for the project for all parties.  Note that some projects may be group projects, where each member of a small group works together on a project.  It is also OK to ask a fellow student for class notes (in the event you miss a class) or for help in understanding the text or material given to the class (e.g., examples on the class website).  It is encouraged to study together as well.
• You must follow the academic honesty policy for HCC.  A second cheating offense will result in an F for the course, and your name will be turned over to the dean for further handling.  I take these matters very seriously.  You have been warned!
• Communications Policy:  I will respond to your emails within 48 hours or two business days.  HCC policy is that grades can only be discussed in person during office hours, or via email only if you use your assigned HCC HawkNet (or Campus Cruiser) email account.
• Every effort will be made to stick to the weekly schedule for our course.  However it may happen that we will fall behind the schedule at some point.  If so no topics will be skipped.  Instead we will attempt to catch up over the following weeks.
• Please be aware that if we fall behind on the weekly schedule, the topics discussed may not match what shows on the syllabus.  The weekly schedule may (but probably won't be) updated in this case.
• In the case we fall behind, any homework assignments are automatically postponed until we do discuss that topic in class (i.e., the next class).  Projects and in-class exams will not be automatically postponed.  Should your instructor deem it necessary, projects and exams may be rescheduled; this will be announced in class.
• Late Policies:  Late assignments ( homework assignments, projects, or exams) generally will not be accepted.  An assignment is late if not turned in by the start of class on the day it is due.

  Late assignments will be accepted late only if you obtain the instructor's permission prior to the due date of the assignment, or for a documented serious medical reason.  All late assignments are subject to a late penalty of at least one letter grade (10%) regardless of the reason for the delay.

  Projects and homework assignments later than one week will receive a more severe late penalty; very late assignments without adequate excuses will receive a grade of F (0).  However if you have a very good reason your instructor may waive any or all of the late penalty.  (Examples of good reasons include extended illness that prevents working, or being out of town for work reasons.  Remember documentation will be required.)

Projects are graded on the following scale:

A = 95% (Excellent: Good design with good comments, style, and extras)
B = 85% (Good: Good design, some comments, readable style, and it works)
C = 75% (Acceptable: Project objectives are met or are close to being met)
D = 65% (Unacceptable)
E = 10-64% (Variable credit: At least you tried)
F = 0% (Didn't hand in the project)

Minor extras worth +5 points, minor omissions or poor design worth -5.

Projects are graded according to their design (25%), how well they compile and run (20%), how well your project meets the requirements specifications (20%), the coding style (15%), the amount (and quality) of your comments (10%), and your creativity in extending the project usefully or an innovative design that uses the features taught in class well (10%).

Projects are not graded when turned in.  They are graded all at once, sometime after the project deadline has passed (usually the next weekend).  Further details will be provided with your first project.  (See also submitting assignments below.)