1 / 8

Final Project Presentation

Final Project Presentation. Final Project Presentation. Friday, May 6 th Begins sharply at 8:00 AM in GACB 105 Each team has 50 minutes for: Presentation (45 min) Q & A (5 min) Load presentations on GACB 105 computer starting at 7:30AM, to be finished by 7:55 AM.

decima
Download Presentation

Final Project Presentation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Final Project Presentation

  2. Final Project Presentation • Friday, May 6th • Begins sharply at 8:00 AM in GACB 105 • Each team has 50 minutes for: • Presentation (45 min) • Q & A (5 min) • Load presentations on GACB 105 computer starting at 7:30AM, to be finished by 7:55 AM. • Demos will be set up in ERB 208 (lab) before 8:00 AM and done after the last presentation • Poster board is set up with demo

  3. Final Project Presentation • Order/timing of presentations is: • 8:00 – 8:50 AM Team Aerotag • 8:55 – 9:45 AM Team DefeNder • 9:50 – 10:40 AM Team eCycle • 10:45 – 11:35 AM Team Pegasus • 11:40 - 12:30 PM Demos (ERB 208) • Note: plan to begin your demo set-up in your cubicle around 7:00 AM, and to be finished and in your seats in the GACB 105 no later than 7:55 AM. Demos should be planned (and rehearsed) to last no longer than 10 minutes per team.

  4. Final Project Presentation Content: • Roles and Responsibilities of team members • Project Overview & Product Concept • Requirements Overview – Per baseline SRD • Requirements Completion Summary/Analysis – green, yellow, red chart • Design Overview (per baseline ADS and DDS) • Test Plan Overview, status report (bugs, etc.) • Project Effort Assessment: Lines of code, hardware, earned value, time spent … • Lessons Learned

  5. Final Project Presentation Hints for Success: • Dress professionally and present at your best • Project your voice to the back the room • Hands out of pockets • Eye contact with entire audience • Rehearseas a team – coach each other • Stay on topic – don’t ramble • Use graphics, pictures wherever possible to liven up the presentation • Practice your demo so you can show what you’ve done in no more than 10 minutes.

  6. Final Project Presentation Other Info: • Friends, family, significant others are invited/encouraged to attend • Please attend a short celebration in the lab area after demos (approx. 12:30 PM). • Each demo setup must include a 3-part posterboard project summary • Picture of team, title of project, key roles & responsibilities • Product concept/description • Architectural design diagram • Key requirements, with completion indicator • Lessons Learned • Photos, etc. as required

  7. Final Presentation Scoring • Overall, this day represents 38% - 39% of your grade for Senior Design 2! • Final Presentation = Final Exam = 30% • Final Product = 100 of approx. 350 possible points for team deliverables (30%) = 8.57% • Final Presentation Score by peer, GTA and instructor evaluation rubric (on website) • Final Product Scoring by instructor per following scale.

  8. Final Product Scoring Guideline • 100: fully operational prototype, fully functional per plan, professionally packaged (extremely rare) • 95-99: operational prototype, with minor functional deficiencies, cleanly and neatly packaged (rare) • 90-94: operational prototype, some major functional deficiencies, packaged well as a prototype (common) • 85-89: operational prototype, numerous functional deficiencies, not well packaged (most common) • 80-84: functioning prototype, with minimal features operational, not well packaged or not packaged at all (frequent) • 70-79: non-functioning prototype, unable to demonstrate key/critical features, prototype is not worthy of display (occasional) • <70: non operational bread-boarded design only, numerous functional deficiencies, unable to demonstrate critical features (rare)

More Related