1 / 9

Final Project Presentation

Final Project Presentation. Final Project Presentation. Friday, November 30 th Begins sharply at 9:30 AM in ERB 103 Each team has 40 minutes for: Presentation (35 min) Q & A (5 min)

quanda
Télécharger la présentation

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, November 30th • Begins sharply at 9:30 AM in ERB 103 • Each team has 40 minutes for: • Presentation (35 min) • Q & A (5 min) • Store presentations on your computer or a USB drive. Email a copy to odell@uta.edu before 9:00 AM on presentation day.

  3. Final Project Presentation • Order/timing of presentations is: • 9:30 – 10:10 AM Team eCardiac • 10:15 – 10:55 AM Team ITUS • 11:00 - 11:40 AM Team TBGL • 11:45 - 12:45 PM Demos, pizza, cake in ERB 103 • Informal discussions with teams and project poster board discussions during lunch

  4. Final Project Presentation Content • Roles and Responsibilities of team members (1) • Project Overview & Product Concept(3) • Requirements Overview– Per baseline SRD (3) • Requirements Completion Summary/Analysis (green, yellow, red button next to requirements) • Design Overview (4) • Summarize ADS and DDS, design trade-offs • Test Plan Overview& Results report (1) • Project Effort Assessment: (1) • Lines of code, hardware, earned value, time spent … • TEAM Lessons Learned (1)

  5. Final Project Presentation Hints for Success: • Dress professionallyand present at your best • SPEAK UP - 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 – be crisp, concise, 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 • Each team’s display/demo area must have on display 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)

  8. Final Product Prototype Demonstrations • Demos will be set up in ERB 103 before 9:00 AM, 11/30 • Your project poster boardwill be set up for the demo • Each team will be given about 15 minutes to demonstrate their product prototype to reviewers. • Order: same as presentations • Teams will be available in demo area for Q&A • Final product prototype scoring is by instructor per the following scale. • Product and poster board will be set up in lab cubicle by Tuesday, 12/4, class time – final demos for invited guests, instructor, ABET review groups, etc.

  9. 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