Kick-Off Meeting August 24 th , 2011 John H.L. Hansen, EE Dept. Head - - PowerPoint PPT Presentation

kick off meeting
SMART_READER_LITE
LIVE PREVIEW

Kick-Off Meeting August 24 th , 2011 John H.L. Hansen, EE Dept. Head - - PowerPoint PPT Presentation

Faculty Meeting May 12,08 EE/TE/CE Senior Design EE/TE/CE Senior Design 1: Kick-Off Meeting August 24 th , 2011 John H.L. Hansen, EE Dept. Head Andrea Fumagalli, TE Program Head Mehrdad Nourani, CE Program Head Marco Tacca, UTDesign


slide-1
SLIDE 1

Senior Design 1 Kickoff Meeting (Hansen)

 EE/TE/CE Senior Design Day: TBA  Oral Presentations: (times to be determined)  Poster Session: (times to be determined)

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design EE/TE/CE Senior Design 1: Kick-Off Meeting

John H.L. Hansen, EE Dept. Head Andrea Fumagalli, TE Program Head Mehrdad Nourani, CE Program Head Marco Tacca, UTDesign

August 24th, 2011

slide-2
SLIDE 2

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

Why is Senior Design so Important for your BS - EE / CE / TE Degrees?

 It represents the “Open Design” Experience resulting from 4 years of coursework  It is the ONLY class, where the students are completely responsible for direction & content of their work  It is the ONLY class where students have direct feedback from Industry  Projects are “Open Ended” – not cookbook/structured  Failures can happen – you need to overcome these!  No Excuses! – You MUST deliver a solution (or repeat!)  It is your time to “show us what you have learned!”

slide-3
SLIDE 3

EE Fundamentals Chart

 Step 1: EE Faculty identified skills necessary for BS in EE  Step 2: Individual EE Faculty assigned/determined skills/knowledge for each class  Step 3: EE-IAB reviews to determine skills and knowledge appropriate  Step 4: EE Sub-Areas Assess Collectively (Digital Area reviewed, etc.) (EE faculty have made 8-10 full passes on fundamentals chart in AY 06-07)

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

slide-4
SLIDE 4

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

slide-5
SLIDE 5

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

EE 4388 Senior Design 1

EE 4388 Senior Design Project I (3 semester hours) First of two sequential semesters

devoted to a team project that engages students in the full engineering design process. The goal

  • f senior design projects is to prepare the student to run/participate in engineering projects related

to an appropriate industry. Thus, all project teams are to follow standard industrial practices and

  • methods. Teams must carry the engineering project to completion, examining real world

constraints, following applicable industrial and business standards. Such constraints may include but are not limited to: economic, environmental, industrial standards, team time/resource management and cross-disciplinary/departmental result integration. (Students are encouraged to work in teams that include collaborative design interaction, but may work on individual projects as well, provided there is a collaboration component. Additionally, cross disciplinary/departmental teams are encouraged but not required.) In Senior Design I, project proposals will be written, reviewed and approved. Initial designs will be completed and corresponding constraints will be

  • determined. All students will participate in a public oral presentation following departmental

approved guidelines at a departmental approved time and location. Teams will also submit a written end of semester progress report and documented team communication (complete sets of weekly reports and/or log books) following guidelines approved by the faculty. Students must have completed ECS 3390 and one of the following prerequisite sequences: (CE 3311, CE 3320, CE 3346, and CE 3354), or (EE 3300, EE 3302, EE 3311, and EE 3320), or (EE 3300, TE 3302, and TE 3346; pre- or corequisite EE 3350). (Same as CE/TE 4388) (3-0) S

slide-6
SLIDE 6

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

EE 4389 Senior Design 2

EE 4389 Senior Design Project II (3 semester hours) Continuation of the Senior Design project begun in the previous semester. In Senior Design II, projects based on approved project proposals will be completed. All limitations of the design will be determined and addressed. All students will participate in a public oral presentation following faculty-approved guidelines at a faculty-approved time and location. Teams will also submit a written final report and documented team communication (complete sets of weekly reports and/or log books) following faculty-approved guidelines. Prerequisite: CE/EE/TE 4388. (Same as CE/TE 4389) (3-0) S

slide-7
SLIDE 7

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

First two weeks of November for Fall ‘12

EE/CE/TE Senior Design Training Sessions  ALL Teams REQUIRED to send at least 1 member  Review SDD Evaluation Form (Poster & Oral)  Review Format and Goals for Slide & Poster  Highlight what makes a “Good” Slide & “Bad” Slide  Student Teams have option to give “Practice Runs” during the training sessions http://ecs.utdallas.edu/students/senior-design.html

VIDEO DOWNLOADS HERE!

slide-8
SLIDE 8

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

April 15, 2011

EE/CE/TE Senior Design Training Sessions

slide-9
SLIDE 9

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

SENIOR DESIGN 1: eight teams

slide-10
SLIDE 10

Faculty Meeting – May 12,’08

SENIOR DESIGN 2: sixteen teams

EE/TE/CE Senior Design

slide-11
SLIDE 11

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

SENIOR DESIGN 2: sixteen teams

slide-12
SLIDE 12

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

Combined Senior Design EE/CE/TE Scores [Dec. 2, 2010]

slide-13
SLIDE 13

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

slide-14
SLIDE 14

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

slide-15
SLIDE 15

Faculty Meeting – May 12,’08

Senior Design 1: Dec. 2, 2010

1st Place: Haptic Shoe for the Visually Impaired [Team 7] Rodolfo Guzman, Whitney Scott, Laura Shagman, Steven Truong 2nd Place: Micro Air Cycle System I [Team 8 tie]

Clement Wong, Sven Moon, Brady Spenrath, Brandon Geil, Michael Galuardi Remote Alarm Management System (RAMS) [Team 2 tie] Adam Sidelsky, Don Vinson, John Dalton Stringer

3rd Place: Wireless & SMS Based Appliance Monitor And Update System [Team 6] Alan Jurcak, Effat Sharmin, Jastine Thomas, Uzma Azim

Senior Design 2: Dec. 2, 2010

1st Place: Wireless Bullet Counter [Team 10]

Zack Mai, Adrian Reese, Michael Arrambide, Michael Hanschke, Justin Elliot

2nd Place: Micro Air Cycle System II [Team 9] Robert Brisco, Nosa Endokpayi, Steven Foland, Amsalu Gedamu, John-Paul Lum Hee & Yuriy Savchyn 3rd Place: Audio Video Avatar Tele-Conference at Remote Location [Team 13] Ajay Patel, Jimmy Kirk, Peter Kariuki, Amare Worku

EE/TE/CE Senior Design

slide-16
SLIDE 16

Faculty Meeting – May 12,’08 EE/TE/CE Senior Design

UTDesign Senior Design Teams: Dec. 2, 2010

1st Place: Temperature Sensing in a UHV Environment [Team 24] Long Nguyen, Alan Wisler, Ward Parsons, Wai Law 2nd Place: Celestial Star Tracker [Team 19 tie] Stephen Blystone, Jeffery George, Noah Robb, Tom Schmidt Stress in FE-RAM devices [Team 23 tie] Eddie Burgess, Muhammad Khan, Rifaz Iqbal, Vikas Poddar, Faisal Akhtar 3rd Place: Automatic Hole-Punch System [Team 20] Lauren Bagen, Dallas Bartlett, Evan Bone, Anthony Stillo

slide-17
SLIDE 17

CRSS: Automatic Capture & Transcription of SDD

EE/TE/CE Senior Design

slide-18
SLIDE 18

EE/TE/CE Senior Design Day April 29, 2011

Faculty Meeting – Sept. 15,’08 Faculty Meeting – Jan. 12,’09

slide-19
SLIDE 19

EE/TE/CE Senior Design Day April 29, 2011

Faculty Meeting – Sept. 15,’08 Faculty Meeting – Jan. 12,’09

slide-20
SLIDE 20

EE/CE/TE Senior Design Day: April 29, 2011

slide-21
SLIDE 21

EE/CE/TE Senior Design Day: April 29, 2011

slide-22
SLIDE 22
slide-23
SLIDE 23

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08 Senior Design Experience

slide-24
SLIDE 24

EE/TE/CE Senior Design Day Dec. 2, 2010

Faculty Meeting – Sept. 15,’08 Faculty Meeting – Jan. 12,’09

slide-25
SLIDE 25

Senior Design 1 Kickoff Meeting (Hansen)

EE/TE/CE Senior Design Day July 25, 2008

Faculty Meeting – Sept. 15,’08 Faculty Meeting – Jan. 12,’09

PREVIOUS

slide-26
SLIDE 26

EE/TE/CE Senior Design Day Dec. 2, 2010

Faculty Meeting – Sept. 15,’08 Faculty Meeting – Jan. 12,’09

slide-27
SLIDE 27

EE/TE/CE Senior Design

April 30, 2010: EE/TE/CE IAB Reviewers

slide-28
SLIDE 28

Faculty Meeting – May 12,’08

MANY THANKS! to all our EE &TE & CE Industrial Advisory Board Members for their participation

EE/TE/CE Senior Design

slide-29
SLIDE 29

Faculty Meeting – May 12,’08

VI Technology Tektronix Alcatel-Lucent CISCO Systems Raytheon Nortel Communications National Instruments Micro-Technology Services

EE/TE/CE Senior Design

Texas Institute

  • f Science

Technicolor – Thomson Communications

Kruvand Research in Motion Mustang Technology Convergys

MANY THANKS! to all our EE &TE & CE Industrial Advisory Board Members for their participation

slide-30
SLIDE 30

Senior Design 1 Kickoff Meeting (Hansen)

http://www.utdallas.edu/news/2008/08/11-002.php?WT.mc_id=RSS

UTD News

slide-31
SLIDE 31

Senior Design 1 Kickoff Meeting (Hansen)

External Industry Evaluator Results for: Summer 2008 SDD

EE/TE/CE Senior Design

Don’t Let This be YOUR team! SD1

slide-32
SLIDE 32

What Should your Slide & Poster Contain / Address?

EE/TE/CE Senior Design

 What is the Problem you are addressing? [limited amount of text]  Why is this Problem Important? Why is the Impact? [know your facts! Give some examples]  How does YOUR solution compare with what is available in the field? (did you get independent feedback on the effectiveness of your solution?)  Identify 1-2 New/Novel Ideas or Aspects about your team’s solution  What are the Challenges you faced? Lessons Learned? [what was something you tried and it failed and how did you overcome it?]  What Are Your Plans? [Senior Design 2; where could this go?]

slide-33
SLIDE 33

EE/TE/CE Senior Design

slide-34
SLIDE 34

EE/TE/CE Senior Design

slide-35
SLIDE 35

Senior Design 1 Kickoff Meeting (Hansen)

Smart Walking Stick for the Visually Impaired

GOALS:

  • 1. Navigation around obstacles
  • 2. Indoor navigation through RFID
  • 3. Outdoor emergency position broadcast
  • 4. Alert others of users’ presence
  • SONAR Navigation: Detects proximity and

depth, alerts via vibration in handle.

  • GPS Locator System: Relays the co-ordinates
  • f the user to an email address.
  • RFID Indoor Navigation: Uses Breadth First

Search based algorithm to navigate e.g. entrance to rest-room.

  • LED Warning System: LEDs flash in low light

conditions.

  • Audio Warning System: Speaker beeps when

activated

APPROACH: Previous Design Current Design

slide-36
SLIDE 36
  • Aug. 24, 2009

Senior Design 1 Kickoff Meeting (Hansen)

EE/TE/CE Senior Design The Judges! The Judges!

slide-37
SLIDE 37

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

What are You responsible for? (1)

 Form your team (pick members carefully; know the technical needs of your project)  Wednesday: change section if necessary  Decide between regular senior design and UTDesign  Set up weekly meetings with instructor  Meet weekly with instructor  Discuss Proposed SD1 Project with instructor  Prepare written “Project Proposal” by the end of September  Prepare project abstract and send to Marco Tacca: mtacca@utdallas.edu by the first week of October

EE/TE/CE Senior Design

slide-38
SLIDE 38

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

What are You responsible for? (2)

 Hold regular meetings – DOCUMENT interactions and exchanges (all of the documentation must be included in the final report)  Note Successes, Failures, etc.  Know the Trade-offs of your Solution  Know your Customers  Have single slide ready (draft) by beginning of November  Participate in the training session (date TBD)  Have final version of slide and poster for senior design day ready one week before senior design day (possibly earlier for UTDesign projects)  Prepare final report

EE/TE/CE Senior Design

slide-39
SLIDE 39

Fall 2012

Erik Jonsson School of Engineering & Computer Science

http://ecs.utdallas.edu/students/utdesign/

slide-40
SLIDE 40

What is the format

  • Kickoff meeting: Students are presented with the

problem at the kickoff meeting. Objectives and deliverables are discussed in detail with the students (and the faculty mentor) in detail at the kickoff meeting

  • Students prepare a written document (project

proposal) that includes: 1. Problem definition 2. Proposed solution approach 3. Project deliverables 4. Timeline for the solution 5. Budget

slide-41
SLIDE 41

What is the format (2)

  • Students prepare a project abstract and send it to

Marco Tacca: mtacca@utdallas.edu (by the first week of October

  • Students implement the solution
  • Students prepare a final written report
  • Students deliver a final project presentation to the

sponsoring company

  • Students prepare for senior design day (due to

possible NDA constraints, the sponsor must clear both the slide and the poster before it is presented to the public)

slide-42
SLIDE 42

Intellectual Property (IP)

  • Students & faculty mentor sign one-

way NDAs

  • Students sign IP agreement
  • Any incidental IP resulting fro the

project belongs entirely to the sponsoring company

slide-43
SLIDE 43

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

Grading Policy

 Project outcome points : up to 80 points

 Student self-assessment: up to 5 points  Soft-skills: up to 10 points:  Ethics (final reports and senior design day poster): 2%  Lifelong learning (proposal and final report): 2%  Contemporary issues (proposal and final report): 1%  Multi-disc teams (proposal and final report): 2%  Communications (semester project work and meetings): 3%  Feedback from Senior Design Day judges (if available): up to 5

  • points. If feedback from the judges is not available, the points will be

based on the instructor evaluation.

EE/TE/CE Senior Design

slide-44
SLIDE 44

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

Project Outcome Grading

Project objective should be CLEARLY spelled out in the project proposal, for example the proposal should have a section that specifies:  If the project achieves MEASURABLE feature set A (the way the measurement is performed should be clearly indicated) -> 80 points  If the project does not achieve MEASURABLE feature set A, but reaches MEASURABLE set B -> 70 points  If the project does not achieve MEASURABLE feature set A, nor set B, but reaches MEASURABLE set C -> 60 points  If the project does not achieve MEASURABLE feature set A, nor set B, nor set C, but reaches MEASURABLE set D -> 50 points  If the project does not achieve MEASURABLE feature set A, nor set B, nor C, nor D but reaches MEASURABLE set F -> 40 points The instructor MUST approve the proposal objectives

EE/TE/CE Senior Design

slide-45
SLIDE 45

Senior Design 1 Kickoff Meeting (Hansen)

Faculty Meeting – May 12,’08

Project Outcome Grading

EE/TE/CE Senior Design

NOTE: during the progress of a project, it is always possible that unforeseeable circumstances affect in a negative way the outcome of a project. Should this happen, the grade might or might not be affected. The following procedure will be in place:

  • If the project achieves MEASURABLE set A, then you get the maximum points for your project
  • If MEASURABLE feature set A is not met, then

Present evidence to demonstrate that the team did everything possible to achieve MEASURABLE feature set A:

  • The first piece of evidence is men hours: each team member is REQUIRED to keep a time log (in half

hour increments) about his/her work related to the project. Each team member is expected to allocate 7/10 hours per week to the project. If even a single team member fails to meet the 7/10 hours per week criteria, no further evidence will be accepted and the project will be graded solely based on the MEASURABLE feature set achieved, i.e., B, C, D, or F. NOTICE THAT IT WILL BE REQUIRED THAT EACH TEAM SUBMITS A WEEKLY REPORT WITH TIME LOGS FOR EACH TEAM MEMBERS FOR THE ENTIRE DURATION OF THE SEMESTER.

  • If the criteria above is met, then the team must include in the FINAL REPORT a section that explain in

great detail why the project failed to meet MEASURABLE feature set A. The final decision about how many points will be assigned for the project outcome points portion of the grade is the sole responsibility

  • f the instructor. NOTICE THAT EXPLANATIONS THAT ARE BASED ON UNAVAILABILITY OF PARTS

OR UNAVAILABILITY OF FUNDS WILL NOT BE ACCEPTED.