CSE Senior Design II Final Project Presentation. 1  This critical formal review serves as your Final Exam for SD2  Date: Friday, December 6 th, 2013.

Slides:



Advertisements
Similar presentations
“Freud and Friends” Theories & Theorists Presentations
Advertisements

CSE Senior Design II Final Project Presentation. 1  Monday, May 6 th 8:00 AM in ERB 103  Begins sharply at 8:00 AM in ERB minutes  Each team.
1 CS 446 – Tutorial 6 Frid. Nov. 6 th, 2009 Implementation Tutorial.
COMP4710 Senior Design Process Documentation and Deliverables.
Boat Construction Design Design of boat is neat with clear measurements and labeling for all components. Design of boat is neat with clear measurements.
Research and Presentation Expectations Nutrients.
Presentations of Learning (POLs) The man, the mystery.
Activities Leadership Team. Goals  To train potential Leaders within Hettinger High School.  Not to focus on the great athletes.  Look for individual.
SIM SOFTWARE ARCHITECTURE Instructor: Masrah Azrifah Azmi Murad, PhD Room: C masrah.azrifah [at] gmail.com OR masrah [at] fsktm.upm.edu.my.
Science Project June 7, Outline 1.March 26 th Assembly 2.Project Launch 3.Creating Student Teams 4.Evaluation and Assessment.
ME EN 282 – Pipsqueak Project Deliverables Due as scheduled on website This includes: – Hardware – Report – Updated Drawing Package – Presentation.
Announcements Class is cancelled on Monday 11/22 The final exam will be take-home, two-three questions, optional for those who want to boost their mid-
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter 2007 Lecture on Oral Presentations Week 7 Day 1.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter 2007 Progress Reports Week 4 Day 1.
EDGE™ Preparing a Poster for a Publication and Display Prepared by Edward Hensel (ME) Elizabeth DeBartolo (ME) Copyright © 2005 Rochester Institute of.
COMP4710 Senior Design Richard Chapman. Outline What is Senior Design? What is Senior Design? Course Structure Course Structure End of Cycle Binder End.
Spring 2015 Senior Design College of Engineering The University of Georgia DEVELOPMENT OF AN EMBEDDED SYSTEM FOR ASSESSING EXTREMITY BLOOD VOLUMES BASED.
Engineering H193 - Team Project Spring Quarter2005 Gateway Engineering Education Coalition P. 1 Lecture on Oral Presentations Week 7 Day 1.
Business Plan Preparation: Publishing Your Plan Publishing & Presenting Your Plan Frank Moyes Leeds College of Business University of Colorado Boulder,
Steps 2 & 3 Presenter:. Training Overview Introduction Walk Through Steps 2 & 3 Username & passwords Team Requirements Scheduled FET Trainings & Completion.
Professional Development Topics that help students demonstrate Proficiency in State Standards on the CST.
EDGE™ Preparing a Poster for a Publication and Display Prepared by Edward Hensel (ME) Elizabeth DeBartolo (ME) Copyright © 2005 Rochester Institute of.
The Presentation How to Make it a Success …or not.
CSE Senior Design II Final Project Presentation. 1  This critical formal review serves as your Final Exam for SD2  Date: Friday, December 5 th, 2014.
10 Aug 2010 ECE/BENG-493 SENIOR ADVANCED DESIGN PROJECT Meeting #3.
1 Welcome to Senior Design 4106 Fall 2005 Section B: Dr. Marc Goetschalckx Dr. Spyros Reveliotis Webpage: Acknowledgement:
Chemistry of the Environment Turn in your pre-lab Turn in your Soda Ash Report Did you place group form into the D2L drop box? Today: Look at Environmental.
Historical Change Project. Project Guidelines and Rules  Project will be completed in class.  You must bring all supplies needed. If you are unprepared.
Creating a Research PowerPoint. The 1st Slide Topic title Your name Date Class period A picture that represents your topic as a whole.
ORAL PRESENTATION TECHNIQUES Food for Thought: Effective communication is 20% what you know and 80% how you feel about what you know. ~Jim Rohn ~
Game Project IMGD 4000 Due Dates: Form Teams Treatment Website Tech milestone AlphaApril 17 Beta Final Presentation.
CSSE 371/372 – Software Requirements and Specification/Software Project Management Steve Chenoweth/Sriram Mohan RHIT.
CSE Senior Design II Day 1: Getting Organized Spring 2015 Instructor: Manfred Huber.
“If you can’t communicate it doesn’t matter what you know.” ~ Chris Gardner © 2013 University of Notre Dame. All rights reserved. This PowerPoint presentation.
DMD Senior Design Projects CIS 497 Joseph T. Kider Jr.
June 7th 1:15 PM = start of first presentation session 1:00 – 5:00 PM Must have table set-up before 11:30 AM in Sullivan Hall.
Senior Project Presentation Guidelines. When Will My Presentation Be? Determine how many days of presentations we need College Now students sign up first.
ECE791 Senior Design Experience Project Requirements and Timeline.
1 04/30/2003 ECE 554 COUNTDOWN DEMONSTRATION  Scheduling  Miscellaneous  Content FINAL REPORT  Check-In  Content FEEDBACK.
CSE Senior Design II Final Project Presentation. 1  Friday, May 3 rd 8:00 AM in ERB 103  Begins sharply at 8:00 AM in ERB minutes  Each team.
Quarter 2 Literature Project DUE December 8 th. Project Guidelines Part One:  Create a mosaic (a picture or decoration made up of diverse elements) 
Class of 2016 Senior Advisory 2/17/16. What’s next?
CSE Senior Design II Day 1: Getting Organized Spring 2012 Instructor: Mike O’Dell.
CSE Senior Design II Day 1: Getting Organized Spring 2016 Instructor: Mike O’Dell.
Edit Final Report & Presentation Final Testing. Lab Schedule LAST LAB!! Should be near completion - polishing report and practicing presentation If not,
1SEP Software / Web Engineering Projects 2IPE0 Spring Lou Somers.
Student Presentations Developing rubrics for assessment Nancy Rees, Barbara White.
PREPARING FOR APRIL 15 JUDGING Nancy Goodman, Pace MBA Citibank VP, retired.
CSE Senior Design II Final Project Presentation. 1  Friday, May 6 th 8:00 AM in GACB 105  Begins sharply at 8:00 AM in GACB minutes  Each team.
Overview of course and How to register
Day 1: Getting Organized Spring 2014
Software / Web Engineering Projects 2IPE0
Publishing & Presenting Your Plan
Final Project Presentation
Sophomore Defenses for the Class of 2020!.
Day 1: Getting Organized Fall 2011
ECE/BENG-493 SENIOR ADVANCED DESIGN PROJECT
Day 1: Getting Organized Fall 2012
Day 1: Getting Organized Summer 2012
Final Project Presentation
Final Project Presentation
Day 1: Getting Organized Fall 2013
Day 1: Getting Organized Spring 2013
Final Project Presentation
Final Project Presentation
Day 1: Getting Organized Spring 2011
Final Project Presentation
Software / Web Engineering Projects 2IPE0
Presentation transcript:

CSE Senior Design II Final Project Presentation

1  This critical formal review serves as your Final Exam for SD2  Date: Friday, December 6 th, :30 AM in ERB 103 (verify)  Begins sharply at 9:30 AM in ERB 103 (verify) 40 minutes  Each team has 40 minutes for:  Presentation (35 min)  Q & A (5 min)  Store presentations a copy  Store presentations on your computer or a USB drive. a copy to before 9:00 AM on presentation

1 Final Project Presentation  Order/timing of presentations is:  9:30 – 10:10 AMTeam Overdrive  10:15 – 10:55AMTeam TKForce  11: :40AMTeam Kingpin  11: :45PMDemos, pizza, cake in ERB 103  Informal discussions with teams and project poster board discussions during lunch

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

1 Final Project Presentation Hints for Success:  Dress professionally  Dress 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  Rehearse  Rehearse as a team – coach each other be crisp, concise, don’t ramble  Stay on topic – be crisp, concise, don’t ramble graphics, pictures  Use graphics, pictures wherever possible to liven up the presentation  Practice your demo  Practice your demo so you can show what you’ve done in no more than 10 minutes.

1 Final Project Presentation Other Info:  Friends, family  Friends, family, significant others are invited/encouraged to attend posterboard  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

1 Final Presentation Scoring 38% - 39%  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)

1 Final Product Prototype Demonstrations  Demos  Demos will be set up in ERB 103 before 9:00 AM, 11/30 project poster board  Your project poster board will be set up for the demo 15 minutes  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.

1 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)