Proposal due date: April 10th (earlier is fine)
Project due date: April 20th
You are to design, implement and evaluate a project of your choosing. The emphasis of the project can vary, from implementation of new code, to modification of existing code, to incorporation of other code, to measurement of existing programs. Whatever you choose, your projects will require a report and an evaluation, in addition to any code you develop.
You will submit a proposal to me roughly 1.5 weeks before your project is due. In the proposal, you will outline the work that will constitute your project. It should include:
Your proposal should be about 1-2 pages in length.
The work itself can involve a wide variety of possibilities, including:
Any project should, of course, relate to topics relevant to the class.
No matter what the implementation effort of your project, you must include a report. The focus of the report may vary, somewhat, but it will contain elements common to the evaluation summaries we have seen thus far in class, including:
There are many possible projects that are suitable. If in doubt, you can run ideas by me briefly via email before starting work on the proposal.
This project is not intended to be an extra large project. Roughly, it should be the same size in total effort as your other projects (1 and 2). So, don't bite off more than you can chew. Especially remember to allocate appropriate time and effort to any new technology you incorporate into your project that you need to learn.
Here is a list of some example topics for projects:
Mini RLM - a previous project that implemented text-based video over receiver driven layered multicast.
Enhancements to your Habla audioconference to support multiple users in "party-call" using either unicast or multicast (or both).
Empirical measurements of the system, the network or the quality of commercial streaming media. See the RealTracer work for an example.
Enhancement or evaluation of multimedia networking research in NS. This can include simulated protocols, such as TFRC or RAP, router queue management techniques such as CBT or ABE, or multicast work such as RLM.
In case you are wondering, Agent Smith is the bad guy in the movie The Matrix. And if you haven't seen the Matrix, I recommend you do so (after your projects is over, of course. :-)).
You must turn in appropriate material so your project can be evaluated:
Your report (see above).
All source code used or developed in your project, including header files. Please include a Makefile, too, for building your code.
A README file with any special instructions or platform requirements for running your application. Provide some examples, even, if that would help.
A file named "group.txt" which contains the following:
login_name1 last_name1, first_name1 login_name2 last_name2, first_name2
Tar up (with gzip) your files, for example:
mkdir proj2 cp * proj2 /* copy all your files to submit to proj2 directory */ tar -czf proj2.tgz proj2
You will use the online turnin program
/cs/bin/turnin) to submit your files:
proj3.tgz to your account on the CCC
/cs/bin/turnin submit cs525z proj3 proj3.tgz
to submit your files.
Return to the Multimedia Networking Home Page
Send all project questions to the TA mailing list: firstname.lastname@example.org.