CS 7270 - Project Decription

The course will include a substantial group project requiring the design, implementation and evaluation of a non-trivial networked service in one of the following categories:

Project Mechanics

The project will be conducted in teams of 4.

The project milestones are:

  1. Project Description: A 2-page document listing your team and describing your project.
  2. Project design: A 5-page document, further specifying your project and describing your design of the software and implementation plan. THIS SHOULD INCLUDE A DIVISION OF LABOR STATEMENT STATING THE WORK THAT WILL BE DONE BY EVERY MEMBER OF YOUR GROUP
  3. Project Progress Report: This 5-7 page document should update us on the progress of your design and prototyping efforts and alert us to any major design changes or implementation problems you are running into.
  4. Project Demonstration: You will demo your working application to the instructor and TA.
  5. Final Report: A 10-page final report describing your system, and your implementation experience. (You may reuse portions of your previous documents for this with appropriate revisions.)

(See below for milestone schedule.)

Note: To avoid double counting, your project cannot be the same or similar to another project you are doing for another class. It also cannot be something you are already doing for your thesis research or as part of your GRA work. If you have any doubts please check with the instructor.

Some Examples

Your grade will be based in part on how creative you are. To help you start the creative juices flowing here are some ideas:

Hardware and Software Platform:

You will need to build a prototype for your system and demonstrate the workings of the prototype to us.

YOu may build your prototype using

Regardless of which platform you are using you are essentially responsible for supporting yourself in the design and construction of your software. That is, we are unable to help in detailed debugging of your code or otherwise support your programming efforts so choose carefully.

Finally, you may choose to build your system from "scratch" or you may choose to build it on top of some exisiting open source. For example, there is source available for P2P applications like Gnutella (e.g., Limewire, Gnucleus) and there is software available for some games (e.g. iMaze). Regardless of where your starting point is, the t your group does has to represent a signifcant amount of coding and design effort and not be a trivial extension of existing source code.

MAKE SURE YOU EXPLICITLY INDICATE IN YOUR REPORTS WHICH PART OF THE SYSTEM IS YOUR CODE AND WHICH PART IS SOMETHING THAT IS AVAILABLE PUBLICLY.

Project Milestones

  1. Feb 4: PROJECT MILESTONE 1 DUE IN CLASS
  2. MARCH 11: PROJECT MILESTONE 2 DUE IN CLASS
  3. April 8 : PROJECT MILESTONE 3 DUE IN CLASS
  4. April 21 - April 25: PROJECT DEMO WEEK
  5. April 28: Final Project Report Due by 5pm.

Best Project Competition

We will have a competition for the best project. the competition will be judged by a panel of faculty to be announced and will run during demo week. The results of the competition will be totally independent from course grading. Awards will be: