EE x96 Preliminary Design Review (PDR) Presentations

Friday, 7 Mar 2008
and
Saturday, 8 Mar 2008
Donald Kim Lab, POST 214

The second presentation is the Preliminary Design Review presentation. The purpose of a design review is to present your design so far and get feedback from others, both those familiar with the project, and those not familiar with what you are doing.

The PDR is held early in the design, before too many implementation details are finalized, but with enough of the research and preliminary design done to have a good understanding of what the inputs and outputs are, and the overall behaviour of the system specified to be able to draw a detailed block diagram. The purpose of the PDR is to see that you have thought about the entire design, to ask about or suggest possible alternatives, and try to catch things you might have forgotten or not considered before the design goes too far to make changes expensive.

So, you are not expected to have a complete working design for this presentation, but are expected to have begun the design process, considered some alternatives, and possibly done some preliminary tests of components and/or subsystems. You should present some details of at least one of your subsystems; enough so that someone at your level of engineering expertise can understand your design. You may have some additional slides in your ppt file, not part of the presentation, but with additional information to address possible questions. Each team will present their design in its current state and be prepared to answer questions from the audience.

This is a TECHNICAL presentation, so "feathers" are not needed. The talk should include the following:

1. Introduction of the team.

So we learn everyone's name (I wont make you do the Name Game :-))

2. BRIEF overview of the project.

Remember, not everyone has seen your Proposal presentation.

3. Overall block diagram of your system.

What are the major modules or subsystems in your design? Are any of these broken down to smaller sub-modules? How to the modules and subsystems interact?

4. For ONE of your modules, a more detailed description of the design.

What components will you be using and what kinds of tests have you done or need to do with them, including results. Drawings, schematics, pictures, algorithms or short code segments might be appropriate here or in your backup slides (as avialable detail and time allow). Discuss why you chose your decisions the way you did. You might a select module that you would most like feedback on here.

5. What remains to be done.

Discuss potential problems you fore see and outstanding issues to be resolved or decisions to be made. If you have things you would like feedback or help on, identify them here.

6. The time line for completion of the project.

Update your Gantt chart here with specific tasks, sub-tasks with milestones and deliverables (e.g. tests you plan to do and when the results will be available). What subtasks have been completed? Which are underway? Which are pending? Dicuss any problems with scheduling here.

As before, the presentations will be held in three sessions. The first session will be on Friday, 7 Mar beginning at 12:45 PM and should be done by 3:15. The second session will begin at 9:00 am on Saturday, 8 Mar and should be done by noon. The third session will begin at 1:00 pm on Saturday, 8 Mar and should be done by 4:00 pm. (NOTE: the sessions are a little longer to allow for all the questions).

If your team has preference for the order in your session (first/last/middle) you can let me know in email also by Friday, 22 Feb, and I will take that in to account (but these are only prefereces; I may or may not abide by them). I will post the schedule for the sessions by Monday 25 Feb. The entire team is expected to be present for the entire session in which they will present. Everyone is welcome to attend the other sessions if interrested.

Each team should send me the powerpoint file for their presentation TWO DAYS BEFORE the PDR, i.e. by Wednesday 5 Mar or Thursday 6 Mar. I will archive these and include a link to the files in the schedule below. I recommend all teams practice their presentation several times before your session.

IN ADDITION, I would like to review your design notebooks PRIOR to the PDR. Each team should submit your design notebook to me TWO DAYS BEFORE the PDR, i.e. by Wednesday 5 Mar or Thursday 6 Mar. by dropping it off at my Holmes 250 office before the end of the work day that day. I will return your design notebook to you at the PDR.

Session 1
12:45-3:15
Friday, 7 Mar 2008
Design Groups B and 2

Project: HIMAX: Augmented Reality

• (raymundo) Flores, Raymundo (296)
• (dbalais) Balais, Darnel (James) (496)

Team Name: Team 4
Project: uMouse

• (ssunada) Sunada, Shane (296) Team Lead
• (longhi) Longhi, Joseph (296)
• (msmenor) Menor, Malcolm (296)
• (ntumeda) Umdea, Nathan (296)

Project: CubeSat

• (amyblas) Blas, Amy (396)

Project: FIRST Robotics

• (wjones) Jones, Windell (396)

Team Name: Super Space Monkey from Space
Project: uMouse

• (trentr) Robertson, Trent (296) Team Lead
• (kdulatre) Dulatre, Krystle (296)
• (loritn) Nakamoto, Lori (296)
• (ngbenjam) Ng, Benjamin (296)

Session 2
9:00-12:00
Saturday, 8 Mar 2008
Design Groups A and 1

Project: Smith Chart

• (jliem) Liem, Jennifer (396)
• (kishida) Ishida, Katherine (396)
• (rkkfyee) Yee, Roxanne (396)

Team Name: Mighty Mouse
Project: uMouse

• (markyf) Fujihara, Mark (396) Team Lead
• (davidota) Ota, David (396)
• (komo) Komo, Bryant (396)

Project: Helicopter

• (hokazaki) Okazaki, Harris (496)
• (jlyden) Lyden, James (496)

Team Name: Ocha
Project: uMouse

• (hsun) Jou, Kanoa (396) Team Lead
• (do) Do, Alan (396)
• (kiwoon) Ahn, KiWoon (396)
• (satoryan) Sato, Ryan (396)

Project: FIRST Robotics

• (do) Do, Alan (296)

Team Name: Aether Burst
Project: uMouse

• (bkarita) Arita, Blaise (296) Team Lead
• (maran) Osakoda, Maran (296)
• (menorm) Menor, Matthew (296)
• (shaunty) Kleinschmidt, Shaunty (296)

Session 3
1:00-4:00
Saturday, 8 Mar 2008
Design Groups C and 3

Team Name: the 8" comb
Project: uMouse

• (ckho) Ho, Christopher (396) Team Lead
• (stevemiy) Miyasaki, Steve (296)
• (yuj) Yu, Joonyoung (396)

Team Name: LOCO MOCO
Project: uMouse

• (jamiery) Yamamoto, Jamie (296) Team Lead
• (aganiban) Ganiban, Aurelio (296)
• (radd) Yatogo, Radd (296)
• (tkohatsu) Kohatsu, Troy (296)

Team Name: Group C
Project: uMouse

• (zisimos) Economou, Zisimos (396) Team Lead
• (rphomsou) Phomsouvanh, Richard (396)
• (delosrey) DelosReyes, Michael (396)
• (jfleong) Leong, Jason (396)

Team Name: CheeHeePono
Project: uMouse

• (puente) La Puente, Mitchell (296) Team Lead
• (suemorit) Suemori, Travis (296)
• (wcchang) Chang, William (296)
• (astomita) Tomita, Ashley (296)

Team Name: Team Amaze Me
Project: uMouse

• (johnkala) Miyajima, John-Kalani (396) Team Lead
• (bgibu) Gibu, Brandon (396)
• (chadhiga) Higa, Chad (296)
• (justinog) Ogata, Justin (396)