Each summer, the BWRC has the pleasure to host a student or two from the SUPERB program here at UCB.  Here's an introduction to students who have worked with Jan Rabaey and Fred Burghardt, and links to their papers and presentation slides.

2002	Candice Jang	U. of New Mexico	A Media Access Control Protocol for the SPECS Project	Proposal	Paper	Poster
2002	DeLynn Bettencourt	CSU Fresno	A System for Performance Measurement of PicoRadio Network Protocols	Proposal	Paper	Slides
2001	Tiffany Crawford	Howard University	Performance Modeling of the Pico-Radio Sensor Network in a VCC Environment	Proposal	Paper	.
	Dan Petkovsek	University of Maryland	System Profiling and Error Analysis of a PicoRadio Sensor Network	Proposal	Paper	Slides
2000	Muhua Pang	University of Rochester	Bluetooth Control Interface for the PicoRadio Network	Proposal	Paper	.
1999	Magali Figueroa	University of California  at Santa Cruz	A Graphical User Interface for a Wireless Intercom System	Proposal	Paper	Slides
1998	Monique Bonneville	North Carolina A&T	Design and Implementation of a Control Protocol for a Wireless System	Proposal	Paper	.

At BWRC, focus has been on the following goals:

1. Learning to be an independent thinker. Research is all about problem solving - you often have to be able to define a problem on your own. Most of the time as a student, you’re given assignments for which the solution has already been found and a framework for solving the problem has already been constructed. In research and design the problem has not yet been solved, and usually has not been fully defined. This is why research is challenging - it’s an opportunity to be truly original, to play with ideas, and to see your ideas become reality.

2. Becoming familiar with the process of bringing an idea from conception to completion. This involves a number of steps from tossing around random ideas to a specific tangible end result - in our case software and hardware. This process involves a gradual movement from generality to specialization; you consider different options in each context, choose the best alternative, and refine the design based on the choice. Engineering is iterative: evaluation/refinement occurs a number of times for a given design.  We hope to expose you to an example of this process, by making you an important part of the project. Your contribution will be an essential subcomponents of the system.

3. Learning the difference between design and implementation. The bulk of engineering work should be in the design phase of a project, not the implementation. A lot of engineers are tempted to go straight to the code or straight to the schematic without a clear solution in mind - kind of engineering-on-the-fly. It’s like: "I don’t wanna waste time simulating, lets just cut to the chase". Fine, you get started sooner, but you nearly always finish later.  Part of your task will be understanding when design should give way to implementation.

4. Finding out what it’s like to be part of a research/design project.  You’ll be exposed to the regular day-to-day happenings of a typical research project at a major US university, in a top department. You’ll be part of the group rather than simply an observer.