ALL PROJECT WORK IS DUE 11:59PM 12/14/97.
The project is worth 64 points. The number of points each student receives will be assigned as follows:
The client will judge how well the project objectives were met, how useful the end results will be for the client's purposes, how clear the documentation is so that changes or extensions are facilitated, and how much work was required. The client will notify the instructor of any special efforts made by particular member(s) of the project team, so they can be rewarded for such labor. Students are obliged to make sure their client provides a report to the instructor.
The in-class presentation should be a professional delivery, carefully rehearsed to fit into the time allowed, with clear graphics, audible speech/audio, and other forms of multimedia as appropriate. There should be a brief explanation of the project goals and of the history of the effort, comments on problems faced and lessons learned, and a demonstration or description of the final project deliverables.
A written report is required to describe in more depth what is covered in the Presentation. Also, there must be a section for users, saying how the project should be used. (In some cases this may be limited to be a one-page handout or flier, if user instructions and help are part of the project.)
Every project must include discussion for those who may need to maintain, revise, or extend the project. This must describe all raw materials (tapes, disk files, etc.) used, how they were transformed, all intermediate files or results, documentation of any programs and their building or use, and give locations (physical or on computer file systems). A knowledgeable person reading this should be able to carry on the work or make revisions if there are problems.
A one page abstract/executive summary also must be included.
A 5 point bonus will go to all team members involved in a project that submits a paper or demonstration proposal to ACM DL'98 or other conference.
The project quality is measured in terms of the quality of its elements, their integration, and how the deliverables satisfy the goals of the project. Video, audio, images, scripting, programs, user-interface, and other aspects will all be assessed. All project specific factors will be considered.
Each student will provide 2 numbers for each other project team member. One will reflect the quality of that student's work and the other the amount of work.
Each number should be on a scale of 0 to 8, where 0 represents no contribution and 8 represents superlative contribution. It is important that these numbers be honestly assigned. If a student turns in the same numbers for all team members, those scores will be ignored and zeroes assumed.