Final Group Information

Deliverables

Each group is responsible for submitting, as a tar file, complete source and documentation for the group project. The file will be ftp'd to a Duke Computer Science machine. Instructions on where to put the tar file will follow.

Ideally, it will be possible to make an executable (if C++ is used) with a simple modification to a supplied Makefile. If Python is used, a Makefile should be provided, if possible, that will freeze the application and make an executable. Extra points will be awarded to groups that provide, via their home-page, frozen (executable) web editors on multiple platforms. This means:

Documentation

Documentation should be provided as HTML files, or, if that is not possible, as either ASCII files, LaTeX files, (or some other format). If you use hyper-text documents, please try to ensure that all links are relative so that the documentation can be ported to other systems.

Your group should turn in a hard copy of user-level documentation, and this documentation should be included in your submission as well.

Group Meetings

Each group must submit all code, files, and supporting documentation by 7:00 pm, Wednesday, May 1. Groups should demo their project one last time on either Tuesday or Wednesday. (Note that I will be out-of-town the April 27-29.)

Please sign up for a time to demo your project on Tuesday or Wednesday. I imagine that it may take up to 30 minutes. If you'd like to get a novice user to demo your system, please let me know and I will try to recruit students who know HTML, but who haven't used your system.

Grading
Group Name/Number/Something Else Novice User (yes/no)
Monday 10:00 am
Monday 10:30 am
Monday 11:00 am
Monday 1:30 pm
Monday 2:00 pm
Monday 2:30 pm
Monday 3:00 pm
Tuesday 10:00 am
Tuesday 10:30 am
Tuesday 11:00 am
Tuesday 11:30 am
Tuesday 1:30 pm
Tuesday 2:30 pm
Tuesday 3:00 pm
Tuesday 3:30 pm
Tuesday 5:30 pm
Tuesday 6:30 pm