Due: Wednesday, May 6, 1998

1. All program source and binary code, including any files used for system installation, and word processing files for items 2 through 5. They may be zipped or tarred, and should be provided on diskette or zip disk.
2. Written installation instructions. These instructions should also be included on the disk as a README file.
3. Users guide. This will provide instruction how to get going once installation is complete. This need not be an exhaustive user manual that describes all possible interactions.
4. Maintenance manual. This should include information that a future software engineer would require in order to maintain your system. This should include a dictionary for all files that are included on the disk (from item 1). Dictionary entry should include file name, file type (e.g. C++ source, HTML, etc.), its implementation platform (e.g. browser, Win95), any compilers necessary to process it, brief description of its contents. It should also include a system architecture diagram showing the relationship of the modules.
5. Written credits for everything submitted for items 1 through 4 above. Includes authorship for all program units, authorship for items 2 through 4, and editor(s) for items 2 through 4.
6. Your individual and confidential assessments of the team project. Please submit to me by email (pete@csc). You may submit this at any time. Topics to address include, but are not limited to,:

• Team organization:
• Did you feel it necessary to have an appointed leader?
• Were decisions democratic, or autocratic?
• Meetings:
• Was it difficult to get team members together for meetings?
• Were meetings run effectively?
• When appropriate, were subgroup meetings held (meetings that didn't involve everyone)?
• Contributions:
• Do you feel that teammates contributed their fair share to the project? Note that I didn't say "equal" share.
• Is it unreasonable for me to assign individual grades for multiple documents? An alternative would be to assign one individual grade based on contribution over the whole project. This would give you more flexibility (e.g. one or two people "carry" the requirements doc, one or two others "carry" the design doc, etc).
• The Project:
• Did it turn out to be more complex than you originally thought?
• Was it too complex? Too easy?