Project

This is intended to be the only team assignment of the term. Teams of size one or two are acceptable, although larger teams can be used if you convince me of the complexity. In general, I would like larger teams when two distinct approaches are taken to the same problem. Of course, I will expect a careful analysis of how the methods compared.

You will need to produce a manual that goes with this project. I want this to be a professional job.

Tier1: A browser-only client (if you want to include applets or JavaScript, you must sell me on using these features)

Tier2: A server that uses JSP to provide the user interface seen back on Tier 1, and Servlets and Beans to provide the logic associated with the problem being modeled. This is typically the business logic.

Tier3: A database server that is accessed through JDBC and stores the persistent data associated with your services.

Some examples of such a project are:

1. The MeasureMe front-end
2. A class scheduling system
3. A conference registration site
4. A book dealership (well the text already has one)
5. A scheduling system for a physician's office
6. A software module archival service
7. etc., etc., etc.

Key features are the multiple tiers, the dynamic nature of the web content and the effective use of beans to provide business logic.

Milestones and Deadlines:

October 23 -- Initial proposal. This must describe the problem being solved, the technologies to be used, a design that shows what is being done at each layer, and the team member's names and contact information. I expect this document to be about two to four pages long. A good diagram takes up space and conveys lots of information. Oh, and let us know the name of your project. Choose a meaningful, short and non-obscene name. We will exercise some editorial power to avoid duplicate names.

November 4 -- Turn in a prototype that uses JSP to create at least two screens of your application. Probably this will be an introductory screen and your first data collection or service choice screen.

November 18 -- Turn in a prototype that is sufficiently complete that we can test your services (at least the majority of them). This must include a Beta version of your manual. The manual has a user's guide and a deatialed implementation description including a reference part that describes all classes, their services and the realtions to other classes (is-a, has-a, uses)..

December 4 -- Turn in the completed project with final documentation.

Rules for Submittals:

Each submission must be in a single zip file sent to Mat. The subject field must include "COP4610" and the name of your project. The zip file must preserve the directory structure of your project. The main directory must be your project name. We will place this in our webapp folder as your context root. The primary subdirectory (WEB-INF) contains your web.xml deployment descriptor and a subdirectory called classes with all your classes (servlets, beans). A second subdirectory (doc) must contain your documentation. A third (jsp) contains your jsp files (often divided into one subdirectory per jsp file with an assocaited html). A fourth (src) contains your java source. An optional fifth (lib) contains your jars. An optional sixth (servlets) contains the html files that start your servlets.