CS 4243-4: Senior Design

Teams and presentations

• Some will be short presentations:
  • 5 minutes for a 2-person team.
  • 7 minutes for 3-person team.
  • 9 minutes for 4-person team.
• Others will be of standard length:
  • 8 minutes for a 2-person team.
  • 10 minutes for 3-person team.
  • 12 minutes for 4-person team.
• All members of a team need to be part of preparing and delivering the presentation. Ideally, the speaking parts should be evenly distributed. All members will need to be standing during the presentation, but the speaker should step forward.
• It is your responsibility to ensure that you've tested your presentation laptop at the presentation venue.

Presentation workshop (individual)

• Group A: Friday, 9/13, 10am-4pm, SEH-1270 (RS/PFB). Gregor, Simon, Robbie, Paul, Ben, Larissa, Lian, Monica, Braden, Pat
• Group B: Saturday 9/14, 10am-4pm, Rome-201 (RS/EN). Alicia, Jen W, Abia, Chengkai, Jinwen, Kyle, Tim, Mihir, David, Joe H, Brian
• Group C: Saturday 9/14, 10am-4pm, Rome-202 (CT/PFB). Shiva, Aimen, Matt, Zach, Joe E, Jenny F, Weiming, Jiawei, Eric, Ahmet
• Group D: Sunday 9/15, 10am-4pm, SEH-1300 (CT/EN) Jack, Henry, Chloe, Jon, Dan, Dennis, Suraj, Billy, Allison, Rachel, Jaesok

Instructions::

• Please report 15 minutes early. WE NEED ALL PRESENT in a group to start.
• Bring your laptops.
• Lunch will be served. If you have an allergy that'll preclude standard pizza, please let us know.

Presentation 1: overview (team)

For this presentation, pretend you are presenting your project to non-technical investors or foundations. Explain what your project is about, what problem it solves, what the impact will be, and why it's novel. Outline what it will be like to use your project.

Presentation 2: impact (team)

Think of this presentation as your second "vetting" with investors or foundations who are doing due-diligence. Start again with an overview of the project, why it's useful, and what you hope to achieve. Explain what other solutions exist to the problem you are solving, and why yours is better. Flesh out with statistics.

Presentation 3: technical overview (team)

Imagine the audience for this presentation to be high-level, technically savvy managers. In addition to a quick overview (reminder) of your project, your goal is to persuade that you have a sound technical approach. Outline the technical solution, explaining key components, providing intuition for algorithms.

Presentation 4: mock-final (team)

The audience for all the Spring presentations are technically savvy generalists. In this case, you are going to pretend you've completed your project and practice what your final presentation might look like. Some slides will be wishful or placeholders because you haven't reached those milestones yet. That's OK, the purpose is to solidify your final presentation.

The final presentation will have the following:

• What is your project about? What is its purpose and why is it valuable?
• Include a video demo (screencast or otherwise).
• Outline key technical contributions using pictures, showing for example, how one of your algorithms work.
• If you have data from experimentation, show the results.
• A strong ending.

Presentation 5: mock-final II (team)

Update your presentation based on feedback, and based on added progress in your project.

Practice for final (team)

Update your presentation based on feedback, and based on added progress in your project. At this point, your project should be nearly complete.

Final presentation (team)