Project Pages (only accessible from the internal web; i.e., use

Project Overview

The project will be a semester-long implementation project that will be conducted by groups. Each project will involve the implementation of a non-trivial and useful sensor-based application. You will first select an application idea, optionally based on my suggestion. Each group (i.e., those who are interested in the same application) will then study the application in depth and write a draft project proposal that provides (1) the detailed description of the target application, (2) a high-level design, (3) the set of hardware/software tools to be used, and (4) a timetable including intermediate milestones. Groups will pitch their proposals in class and seek feedback. Based on the discussion, groups will revise and finalize their proposals.

Groups will present their status in class towards mid-semester and demo their final product during the end-of-semester mini workshop. Groups will also generate a mid-term status report and a final report that summarize their status to date. Each group will create a public project web page that will include its progress reports and other relevant information.

Hardware Resources

You will have access to:

bullet Wi-fi Pocket PCs (Toshiba e740s).
bullet Wireless sensor devices (Mica Motes) that run TinyOS.
bullet Wireless and wired Internet cameras (D-Link DCS-5300w).
bullet Bluetooth adapters (FMI USB).
bullet AIBO robot (ERS-7M2).

Project Timetable (tentative)


9/21 Project groups due
10/05 In-class presentation
10/14 Project proposals & web page due
11/09 Progress report; in-class presentation
TBA Mini workshop; demo presentations
TBA Final report


The proposal should not be longer than 5 typeset pages, and should consist of the following sections:

    1. Abstract (brief overview of application and why it is important and relevant)
    2. Detailed description of the application (including target users)
    3. Motivation (why is this problem important and relevant?) 
    4. Methodology (tools, techniques, and environment you will use for the implementation)
    5. Timetable and workload division (intermediate steps that will ensure the desired outcome -- with dates and names)
    6. Related work (have others implemented similar applications? If so, how? How is your approach better?)

Progress Report

The intermediate progress report is an important checkpoint for the successful completion of your project. The progress report should be a revision/extension of the proposal, and should provide details of your progress. Any changes to the original proposal should be clearly spelled out. This document should not be longer than 10 typeset pages.

Final Report

This is the final description of your project (no more than 15  typeset pages). This is an expanded/revised version of the progress report and should additionally include the following sections:

bullet Users guide (how do I install and use the system?)
bullet Programmer's guide (main components of the program; high-level control & data flow among the components)
bullet Future work (are there known bugs or limitations? What extensions are desirable?)