CSE 373, Spring 2004: Projects

Projects -- CSE 373, Spring 2004: Version 1.0 (May 13)

Work Mode

There are two options: partnership work and individual work. The partnership projects are more ambitious than the individual projects.

In all cases, the project should result in an applet that can be run in both I.E. and Mozilla. The applet should follow the style of the other applets assigned in this class. In the case of the web spider, there may be a non-applet component of the project that crawls the web.

Partnership project options


a. Web spider and search engine
  (One student builds the spider and the other does the query processor)
  This program is the one exception to the applet rule.  The
  spider should run as an application program, ideally on the server.
  The query processor can run as an applet, but it must then download
    the web index from the server, possibly as a precompiled object.

b. Graph Layout
  One student handles the algorithm, and the other handles the 
    input formats, graphics, and interaction.
  This program should produce nice layouts with relatively few
    crossovers in the case of nonplanar graphs.

c. Graph shortest path finding with Dijkstra's algorithm. (Applet).
  Use a simple layout method, or allow the user to enter the layout info
   as part of the input text.

d. Image segmentation using Disjoint sets...

Individual Project Options

  Disjoint sets implementation without application to image segmentation.

  Knuth-Morris-Pratt string matching algorithm.

  B-Trees applet demo supporting insert and delete as well as find
    and inorder traversal.

  Splay trees applet demo.

The project proposal form handed out in class contains a draft schedule for your work on the project. You are welcome to set your own schedule, except for the June 4 demo deadline. Project reports will be due on Monday, June 7 at 5:00 PM.

Project reports

The report should be an electronic document (either raw ASCII text, MS Word file, or a PDF file). The key elements of your report include:

(1) Title of project,
(2) names and roles of each teammate,
(3) what the applet is supposed to do,
(4) technique used,
(5) how much you have succeeded in getting to work,
(6) any remaining functionality that was intended by not working,
(7) what the most challenging part of the project was,
(8) what the most enjoyable part of the project was,
(9) what each team member learned in this project.
(10) a list the names of your source code files and roughly what each of them contributes to the overall program.
(11) any other comments.

The source files and the project report file should be turned in as a ZIPped archive with a filename based on your last name (for a partnership, both partners' last names. For example, JONES-MILLER-373-PROJ.ZIP).

Turn-in

Here is the submit form.