[ Online Instructions ] [ Assignments ] [ Syllabus ] [ Online Resources ] [ Examples ] [ Lecture Notes ] [ Class Updates: ] [ Project Format ]

Special Topics in Advanced Java Networking

ELEC 4276/6276 Spring 2000

Instructor: Dr. Russell Deaton, Rm. 214, x3250, rjdeaton@memphis.edu, http://www.ee.memphis.edu.

Office Hours: See my homepage at http://engronline.ee.memphis.edu/rdeaton

Textbook: M. Campione, K. Walrath, and A. Huml, The Java Tutorial Continued: The Rest of the JDK, Addison-Wesley, 1999.

Supplemental Text: David Flanagan, Java in a Nutshell, O’Reilly, 1997.

Goal: The course is designed to introduce Seniors and Graduate Students in Electrical Engineering to distributed object models for network applications.

Prerequisites: ELEC 4275/6275 Introduction to Network Programming

1. Java fundamentals.
2. C Programming (ELEC 1207).
3. OOP Fundamentals.
4. TCP/IP.
5. Sockets.

Topics: (25 Classes with a couple extra for odds and ends)

1. Class Introduction (1 class).
2. Java Beans (5 classes).
3. Java RMI (5 classes).
4. Java/CORBA (5 classes).
5. JDBC or Servlets (5 classes).
6. Report Presentations (4 classes).

Grading:  The course will be graded on a C curve.

Policies and Details:

1. I will grade the course on a C curve.  If I think it is warranted, I may improve this to a B curve.
2. If I cannot read it, I do not grade it.
3. Report: Each person in the class will give a 15 minute presentation on a Java or network topic. This will occur throughout the semester. You can sign up anytime you want, but approve the topic with me.
4. You may also be doing some in-class demos of your projects.
5. Check the Web Site for the Class for Updates. http://engronline.ee.memphis.edu/advjava

Your Programming projects will be graded as follows.   Percentages represent approximate weightings.  The grades you will receive will actually be letter grades with +/- (i.e. A, B+, C...).  The grade will be subjective based on my judgement of overall quality.  I will average on the basis of the following table:

The following should give you and idea of approximate weigthings, as well as the more detailed discussion of report format.

Design and Documentation (30 %). A design document is required for each project. The design should document your plan for the software, including code modularity, requirements analysis, and user interface.  Your programs should be well-documented. At the completion of the project, you should have documented how to operate the software, your debug procedures, what testing was done, and the results of the testing. In addition, your code itself should be well documented.  Template for Report.

Implementation (40 %). You will demo the code for me. The things I am looking for are does it work? and does it work 50 times in a row? You will also turn in your source for me. On the group project, each member of the team will demo the code individually for me.

Knowledge and Originality (30 %). This will be assigned based on the demo and your answers to my questions about the code.

[ Back ] [ Home ] [ Next ]