CSE Senior Design II Final Project Presentation. 1 Friday, May 3 rd 8:00 AM in ERB 103 Begins...
-
Upload
audrey-merritt -
Category
Documents
-
view
215 -
download
0
description
Transcript of CSE Senior Design II Final Project Presentation. 1 Friday, May 3 rd 8:00 AM in ERB 103 Begins...
CSE Senior Design IICSE Senior Design II
Final Project PresentationFinal Project Presentation
1 Final Project PresentationFinal Project PresentationFriday, May 3rd
Begins sharply at 8:00 AM in ERB 1038:00 AM in ERB 103Each team has 35 minutes 35 minutes for:
Presentation (30 min) Q & A (5 min)
Store presentations Store presentations on your computer or a USB drive. Email a copy Email a copy to [email protected] before 8:00 AM on presentation day.
DemosDemos will be set up on tables in ERB 103 before 7:30 AM. Teams will do their demos after the last presentation
Poster boardPoster board is set up with demo
1 Final Project PresentationFinal Project PresentationOrder/timing of presentations is:
8:00 – 8:35 AM Team Power Visio 8:40 – 9:15 AM Team MASS 9:20 - 9:55 AM Team Behind the
Curtain 10:00 - 10:35 AM Team Easy Office
Solutions 10:40 – 11:15 AM Team AVIAR 11:20 AM - 12:30 PM Demos & lunchNoteNote: plan to begin your demo set-up early, and to be finished and
in your seats in ERB 103 no later than 7:55 AM. Demos should be planned (and rehearsed) to last no longer than 10 minutes per team.
1 Final Project Presentation Final Project Presentation ContentContent
Roles and Responsibilities Roles and Responsibilities of team members (1)(1)
Project OverviewOverview & Product ConceptConcept (2)(2)Requirements Requirements OverviewOverview – Per baseline SRD (2)(2)
Requirements Completion Summary/Analysis (green, yellow, red button next to requirements)
DesignDesign Overview (4)(4) Summarize ADS and DDS, design trade-offs
Test Plan Test Plan Overview & Results report (2)(2)Project Effort AssessmentEffort Assessment: (1)(1)
Lines of code, hardware, earned value, time spent …
TEAM Lessons Learned TEAM Lessons Learned (1)(1)Numbers in parentheses represent approximate number of slides/weight for each topic.
1 Final Project PresentationFinal Project PresentationHints for Success:Dress professionallyDress professionally and present at your best
SPEAK UP - Project your voice to the back the room Hands out of pockets Eye contact with entire audience
RehearseRehearse as a team – coach each otherStay on topic – be crisp, concise, don’t ramblebe crisp, concise, don’t rambleUse graphics, pictures graphics, pictures wherever possible to
liven up the presentationPractice your demo Practice your demo so you can show what
you’ve done in no more than 10 minutes.
1 Final Project PresentationFinal Project PresentationOther Info:Friends, familyFriends, family, significant others are
invited/encouraged to attendPlease attend a short celebration short celebration after
demos (approx. 12:30 PM).Each demo setup must include a 3-part
posterboardposterboard project summaryPicture of team, title of project, key roles & responsibilitiesProduct concept/descriptionArchitectural design diagramKey requirements, with completion indicatorLessons LearnedPhotos, etc. as required
1 Final Presentation ScoringFinal Presentation ScoringOverall, this day represents 38% - 39% 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.
1 Final Product Scoring GuidelineFinal 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 (somewhat common) 85-89: operational prototype, numerous functional deficiencies, not
well packaged (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)