CS 263: Wireless Sensor Networks

Prof. Matt Welsh
Spring 2009

Research Projects

Projects are to be undertaken either individually or in pairs, unless you have made special arrangements with me.

Project Presentation Schedule

April 28, 2009

April 30, 2008

Each talk will be 15 minutes in length followed by 5 minutes for questions.


Proposal Format

Research Project Proposals due by beginning of lecture on Tuesday March 3, 2009. Please email your proposal in PDF format to cs263-staff@eecs.

The proposal should be a 2-3 page document including sections on:

Project Presentations

CS263 final project presentations will take place during class on April 28 and 30. All students are expected to attend both days.

Each project group will prepare a 15 minute presentation outlining your project and presenting initial results. Following each presentation we will have 5 minutes for questions and to switch to the next group. The presentation format is intended to resemble a "work in progress" session at a research conference, in which individuals are given an opportunity to present a brief overview of a new and exciting project. We do not expect that you will have completed your project by this date, although you should have done most of the work so you have something tangible to present. You should include a summary of the status of your project as well as what your expected outcome will be.

Presentation format: Please prepare a short presentation in PowerPoint or PDF format. We suggest no more than 10 slides total in your talk. Only one project member needs to give the presentation, but you are welcome to "tag team" if you like. Please time yourselves and be sure that your talk will exceed no more than 15 minutes ... we will "gong" any talk that goes over time (and you will lose points for exceeding the time limit!).

The goal of your presentation is not to explain everything that you have done, but rather to get the main points across in a short time. Above all, you should make your talks fun and interesting. Of course, this does not mean the talk should not have any technical depth. All talks will be graded on clarify, style, technical content, and whether it stays on time.

Please email your presentation slides to cs263-staff@eecs by 11:59pm the day before your presentation. We will load all slides onto one laptop so that switching between presentations will go smoothly.

Final Report

Your final paper for the course is due at 5:00pm EST on May 11, 2009. No late papers will be accepted. Please e-mail the paper as an attachment (not a URL) to cs263-staff@eecs.

The final paper for the course is intended to be a conference-style paper, much like the papers you have been reading all semester. It should include the same general structure (abstract/intro/related work/system architecture/implementation/evaluation/future work/conclusions) as these other papers. Of course, depending on your project, the exact structure may vary.

The paper should be written for a scientific audience of experts in the field of wireless communications and sensor networks. In other words, it should present your research in the same manner as you would expect to see in a conference such as Sensys, Mobicom, SIGCOMM, etc. The idea behind this is to give you practice writing conference papers, and hopefully we will be able to actually submit your paper to one of these conferences in the coming months (the Sensys deadline is in April, for example). If you are interested in this, I am happy to work with you to refine your paper for submission.

As with all conference papers, you must follow a set of formatting guidelines. I am not going to pull out a ruler to check your margins, etc. but if you seriously abuse these general guidelines then you run the risk of making the reviewers (i.e., me) unhappy.

Project Ideas

These are only suggestions to help you get a sense of the scope and topics for research projects that would work for CS263. As mentioned previously, projects must have some connection to the overall topic of the course, but can draw on ideas from other fields (e.g., theory, AI, languages, etc.) In fact, we encourage projects that have a "non-systems" component.