Handout 5: 2/5/03

Computer-Supported Collaborative Work, Spring 2003
Term Project

Proposal due by Monday, February 17, 2003
Literature review due by Friday, March 28, 2003
In-class presentations beginning Monday, April 21, 2003
Written report due by Wednesday, April 30, 2003

In the term project, you are to locate a problem of relevance in the domain of computer-supported cooperative work, propose and design a solution, and implement the solution in prototype form. You have wide lattitude in choosing a problem. The term project may be an individual or group project--the larger the group, the more ambitious the project should be. In the case of a group project, all members of the group receive the same grade. You might start by thinking of a kind of a project that when written up would result in a paper like the conference research papers that we have been reading in class. A larger group would be expected to come close to the scope of work found in these papers. A smaller group's problem would be scaled back proportionately.

The proposal is to be a short, written, statement indicating the following:

  1. identify and discuss the problem to be investigated
  2. identify and locate the computing and other resources needed to implement the prototype
  3. identify the team members
An appropriate length for the proposal is one page or less, single spaced or equivalent.

The literature review is intended to survey the "state of the art" with regards to what others have done addressing your problem or similar problems. The review can be as long as needed. A literature review might run around five pages (single spaced or equivalent) in length. It should include accurate and complete literature citations.

The in-class presentation is to provide a demonstration of your prototype, either interactively (if facilities are available) or by pre-prepared slides.  You will have to make advance arrangements if any equipment is required for the presentation.

The written report is likely to be at least 6000 words and is to cover the following

  1. Problem statement and review of other solutions (I would expect that this would be derived from the earlier proposal and literature report.)
  2. Users and use environment
  3. Solution description
  4. Prototype: design and presentation of implementation
  5. Evaluation, if any
  6. Discussion, analysis, future work, etc.
The written report serves as the archival report on your project. It should be self contained and should serve as a complete description without reference to presentation, other reports, etc.
Richard Furuta

February 4, 2003