Day/Time: Thu 2:00pm-3:15pm and 3:15-4:40pm
Credit Hours: 3
Prerequisite: Introduction to Java (MCS3603) or equivalent
Location: S220 (to be changed)
Instructor: ChanJin Chung, Ph.D.

• Office Room: S112
• Phone: (248) 204-3504
• Fax: (248) 204-3518 (this fax number is for the whole building and senders should be sure to place instructor's name on the fax)
• Dept. Secretary: (248) 204-3560
• Math/CS Drop Box: in front of S120 door. Please put instructor's name and time of submission on your work.
• Email: CHUNG@ltu.edu
• LTU webpage at http://www3.ltu.edu/~chung (syllabus, announcements, lecture notes, source codes, etc.)
• LTU BlackBoard
• Office Hours: check out http://www3.ltu.edu/~chung/f01sch.htm

Recommended Text: Professional Java Server Programming J2EE Edition, Wrox, Sep. 2000, ISBN: 1861004656

Internet Resources

• Textbook Author's page: http://www.cecs.csulb.edu/~artg
• http://www.cecs.csulb.edu/~artg/internet/index.html
• Textbook Homepage: http://www.scottjonespub.com/computjava.html
• Recommended book homepage: www.wrox.com/Books/Book_Details.asp?ISBN=1861004656 (source code, book errata)
• Java, Sun Micro Systems (JavaSoft)
• Java Tutorial by Sun | Java course by IBM
• Java Quest | The Sun Certified Java Programmer Examination
• Allaire JRun, JRun Studio, Kawa: http://allaire.com/
• MySQL: http://mysql.com
• ...

1. Advanced topics in Java Programming. (Encouraged to take Sun Certification exam)
2. Practical experience in Web server programming with the Java 2 platform
3. Database access with Java
4. State-of-the-art Java technology for distributed applications
5. Real world (web server and/or device) projects in Java.
6. Software Engineering for Web Applications

Tentative Class Topics (15 weeks)

1. Java Review [1.5 week] - Exception Handling, Event-Driven Programming, I/O, Threads and Concurrent Programming,  etc
2. Web component development with Java [8.5] - Java Beans, Servlets, JDBC, JNDI, JSP, and JSP custom tag libraries
3. Key technologies for distributed applications [2 ] - Network Programming, RMI, JavaMail, JMS, and XML
4. Modeling business logic with EJB [1]
5. Topics [1] - Java Telephony, Java Card, Java for D-TV, etc.

• Homework (programming) assignments - 60 points
• 1 final (everything covered in class) - 60 points
• (Group) Project - 80 points

• By Thu., 10-18-01, Prototype Project Demonstrations
• Thu., 11-15-01, 2nd Project Demonstrations
• Tue., 11-20-01, Last day to withdraw
• Thu., 12-13-01, Final Project Demonstrations
• Thu., 12-20-01, Final (Time 2:00-3:20pm)
• Thu., 12-20-01, Final Project Demonstrations, Last Chance (Time 3:30-4:40pm)

Class Policies

• Attendance is essential to doing well in the course. The final exam will focus primarily (but not exclusively) on material presented in the lectures.
• If you are unable to attend a meeting, it is your responsibility to obtain the material from other students, class webpage, blackboard, or instructor.
• Instructor is providing a web-server account with JRun Application Server and MySQL. The expiration of the account will be decided by the instructor after the class.

Final Exam. Policies

• There will be no makeup final exam will be given
• Closed books, closed notes, and closed neighbors

Lab Environment on Campus

• JBuilder 3: M215 and other labs
• M215: JRun and JRun Studio
• ltu164.ltu.edu: instructor's personal web-server
• ...

Homework Policies

• You may use any Java IDE tools. However, you must provide a way for the instructor to test your program. Instructor has JDK 1.2 and JBuilder 3.
• Homework assignments must be done individually. 
• DO NOT COPY THE WORK OF OTHERS
• Must be submitted at the beginning of the class on the due date.
• Late submission penalty is 30%.
• No submission will be accepted beyond a week after the due date.

Group Project Policies

• Team Size: maximum two
• Must find a real-world project. The instructor will give you some topics. The project requirement specification must be approved by the instructor.
• Must be implemented on a real web-server on the Internet.
• Must follow Software Engineering methodologies. All the documents should be published on the webserver. Students are supposed to put the source codes on the server too. 
• Grades will be based on completeness, consistency, reliability, robustness, reusability, user-friendliness, creativity, documentation, teamwork, scientific finding, educational value, new technologies used, etc.
• Also each team member will evaluate another members in the team.
• Late demo penalty: 30% off

Policy on Academic Misconduct