CS 102

Final Project

(Individual and Varied Topics)

Individual project proposals due on Monday (March 24th)
   (explicitly describe the project and how it meets the "must use"s below)

Individual project proposals approved by Monday (March 31st)
Individual project must be presented in class on Thursday (May 8th)
(Specific submission instruction for your project will be given later)

You will be given a sheet to indicate how and where you used the following:

* You must use encapsulation, inheritance, and composition
* You must javadoc all classes, methods, and fields
* You must use appropriate modifiers, access, data types, and control structures
* You must use extends (classes) and implements (listeners)
* You must use one and two dimensional array(s)
* You must use at least one package you create
* You must use event handling for all normal situations
* You must use file I/O (suggest text but you may choose object)
* You must implement a main menu in part of the overall application
* You must use swing GUI(s) in part of the overall application
   (including a variety of Swing components)
* You must use explicit layouts and containers
* You must use normal menus including file and help menus
   (including exit, help and about menu items)
* You must use dialogs
* You must use thread(s)
* You must use MVC (model-view-controller) in part of the overall application
* You must use some form of network programming (sockets, servlets, JSP, or RMI)
* You must use some form of graphics (images, drawing, polygons, etc.)
* You must use utility class(es)
* You must use collection class(es)
* You must use inner class(es)
* You must use webpage(s)

* You may use explicit security manager(s)
* You may use polymorphism
* You may use abstract class(es)
* You may use applet(s)
* You may use animation
* You may use JDBC
* You may use JavaBeans
* You may use audio / video
* You may use synchronization
* You may use advanced Swing components
* You may use 2D or 3D graphics
* You may use XML

Grading will be:
> 80% for required (i.e., "must use") items above (plan their use),
> 10% for appropriate design (use classes, packages, etc. appropriately),
> 10% for creativity (this is hard plan), and
> up to 20% extra for significant use of extras (e.g., "may use")
   (check early if concerned)

A project which doesn't run can get no more than 30%

Your project will be evaluated on Linux system(s) (remember to check on one)

YOU WILL START SMALL, TESTING AS YOU GO (but plan the general idea early) - RIGHT???