30IT397: Final Project
(4/22/2002: Preliminary, subject to revision)

I firmly believe that the best way to learn is to learn by doing something you like.  Thus, much of the final project is up to you, as long as you meet the general requirements.  You have two options: A Swing-based project, or a Web-based project.  You need not do both, though you certainly can use parts of each, as long as you meet all of the requirements of one.

• Overall Requirements:
• Make preliminary Use Case (20%) and Class Diagrams (60%).  The Use Case diagram should include a written proposal (20%) of what you want to do.  This is due the 8th week of class.  By no means does this have to be perfect or representative of the actual final product, it just has to be a general description.  After all, we won't even cover all of servlets and JSPs until the end of class.
• Requirements for Swing project:
• The project must have at least three independent JFrames: 10
• Use at least one pattern: 10
• Good use of classes and object-oriented design: 10
• Have a JList, JTable, or JTree with a Model of some type that you implement.  10
• Commented: 10
• Use some custom classes, preferably with the JavaBeans standard: 10
• Use a JRadioButton, JCheckbox, or JComboBox: 10
• Have at least one Listener: 10
• Code in good form (proper spelling, graphically appeasing, etc.): 10
• Do something extra, something not listed here: 10
• Requirements for the Web-based project:
• Use at least one servlet: 10
• Use at least one tag: 10
• Use at least one JSP: 10
• Commented: 10
• Use at least one custom class, preferably with the JavaBeans standard: 10
• Use an HTML form: 10
• Exhibit good use of object-oriented principles: 10
• Use cookies, hidden fields, or other session-tracking for page-page navigation: 10
• Code in good form (proper spelling, graphically appeasing, etc.): 10
• Do something extra, something not listed here: 10

Created by:  Brandan Jones December 17, 2001