CSCE 492: Problem Set 3

Presendation/Demo: 1-2 May 2001

1 May between 1-4pm, 2 May between 10am-1pm

Writeup: 7 May 2001

The Final Step consists of a presentation and a writeup, both of which are equally important.

Presentation: All presentations and demos will be held on the 7 of December in room 1D11 from 1pm to 4pm. All students must attend. There will be a computer projector. Each team will have 30 minutes to give the full demo and presentation. (If you cannot demo in the 1D11 machines, your presentation should have enough screenshots to give us an idea of how the program works). You must request a day and time(s) so I can schedule you. The times will be posted on the homepage as they are requested (first-come first-serve). The presentation should cover:

Writeup: The writeup will consist of a set of static HTML pages that you will place in the public_html directory of one of your team members (in source.cse.sc.edu), along with a printout of your commented code which you will hand to me. The set of pages you create must form a coherent website. It does not need to be fancy but it should allow visitors to easily find all the information. These websites will be kept "forever" as examples of the work previous students have done. Specifically, I will have the students next Spring look at those pages in order to get ideas about what type of project to do and to gauge the amount of work I expect (hint: more than you did ;-)

All the webpages should be static (i.e. no VBScript, PHP, etc.) so that I can put them under any webserver. This set of webpages will contain:

  1. a homepage with the team name, member names, division of labor, a small blurb, and links to all your other pages, (optional screenshot). Note:,If the division of labor was not even, i.e., not everyone worked the same amount, please give percentages specifying how much each person contributed to the project.
  2. all the slides from your presentation, in HTML format ("save as" HTML), or you can incorporate these into your website,
  3. the UML diagrams (Rational Rose has an "export as HTML" option),
  4. an optional section with comments on how you think this laboratory class could be improved, try to be realistic (e.g., we cannot give a PC to each student), this section is just meant to help me improve the class and will not affect your grade in any way,
  5. optional API documentation (perhaps, automatically produced by javadoc, or doc++),
  6. optional links to download your source code.

You will email me the URL for your project.



Jose M. Vidal
Last modified: Tue Mar 27 11:11:33 EST 2001