welcome to engineering senior design exhibit i fall 2014 dr. laura lackey 301-4106;...

Post on 02-Jan-2016

215 Views

Category:

Documents

0 Downloads

Preview:

Click to see full reader

TRANSCRIPT

Welcome to Engineering Senior Design Exhibit I

Fall 2014

Dr. Laura Lackey301-4106; lackey_l@mercer.edu

Agenda• Sign in• Class Policy• Course Documentation• Course Syllabus/Administrative Details• Course Schedule• Teams/project adjustments• Proposal : Due• Questions• Meet with your team

Class Policy (487/488)

• Attendance Policy - function of professionalism and therefore your grade

• Dress Code – please leave personal details to the imagination

• Cell Phones – It is understood that we all occasionally forget to turn our cell off. If yours rings in this class, quietly gather your things and as inconspicuously as possible, leave the room.

Class Policy (XXX 487/488) – Due Dates

• We do not take late work (nonnegotiable)– If you put me in a bind, penalties are severe

• COB is 5:00 p.m.

• At class time means at the beginning of class – not 5 minutes after class has started

• PDR/CDR – due 3 working days prior to oral presentation – copy to instructor, client, tech advisor, Ms. Rogers (on a CD)

Class Policy

• BE ON TIME

Class will typically begin a couple of minutes late. If you arrive after class has started, please do NOT enter the room. Get details you missed from a teammate.

Why…

DOCUMENTS

• 487/488 GUIDE• SYLLABUS WITH SCHEDULE• SCHEDULING A PDR

Guide and Syllabus

• Read all material in this packet/syllabus– you’re responsible whether we’ve specifically

gone over subject or not

• We will cover Highlights today

• Notice PDR and CDR Guidelines – beginning on p. 9

Class Schedule Highlights

• XXX487 only meets on Tuesdays as a class (XXX488 – Thursday)

• Periodic Team/Management Meetings with Instructor - Thursdays

• Consider scheduling meetings on alternate weeks with– tech advisor(s)– client

TuesdayTuesday

Deliverables Thursday Meetings

         

Week 1 1/7 Course Introduction and Administration 01/09

   

Week 2 1/14 Brainstorming - Dr. Laura Moody

   

Week 3 1/21Mock Proposal Presentation Written Proposal

01/23 Project Proposal

Description

   

Week 4 1/28 Proposal Presentations Oral reports

   

Week 5 2/4Engineering Analysis - Dr. Loren Sumner 02/06

Progress report

   

Week 6 2/11 Codes and Standards/Ethics Lecture/Exam

   Week 7 2/18 No Lecture 02/20

   

Week 8 2/25 Status Presentations Oral reports

   

Week 9 3/4Designing Written Reports (TCO) 03/06

Progress Report

   

Week 10 3/11 Spring Break

Time 23-Jan 6-Feb 20-Feb 6-Mar 20-Mar

Edward Adams3:00 - 3:25

Project Proposal Description

Individual Progress Report

Individual Progress Report

Nicholas Reina

Renita Mason

Joshua Lindsey

Andrew Gill3:30 - 3:55

Project Proposal Description

Individual Progress Report

Individual Progress Report

Will Daniel

Gabe Denes

Matthew Harmon

Ryan King4:00 - 4:25

Project Proposal Description

Individual Progress Report

Individual Progress Report

Harry Baker

Joao Pagan

Ned Nobles

Importance of Meeting Documentation

• Use Team Meeting Log– Document conversations/meetings with

clients– Document meetings with technical advisors– Document meetings with management

– Consider having client/tech. advisors/management initial form – showing consent of ideas discussed

“Just in Time” Lecture Series

• Merit Analysis• Design Applications• Design Analysis• Document Usability• Oral Presentations• Engineering Ethics• Future of Engineering

Progress Reports – no surprises at the end of the semester

• Individual – Your time to tell us what you’ve done, private correspondence between only you and the instructor

• Submit via email (by COB)– Appropriately label the subject line– At the beginning of the email, remind me of you, your

team, and project– Due

• February 6• March 6

The Process

• 1st semester – design and create a test plan

• 2nd semester – build and test

At this point -

• Everyone should be on a team

• Each team should have an approved project

• Are there exceptions??

Proposals

• Due – (3:05 p.m.), Tuesday, January 21st

• Guidelines – page 8 of Guide

• Budget Request Form

• Proposal Grading Considerations

• Guidelines for Written Project Reports

Grading Rubric

20 Executive Summary

10 Introduction/Background

21 Problem Statement

22 Deliverables

10 Proposed Possible Solutions/Methods

23 Design Plan

10 Resource Requirements

24 References

5 Resume/Bios of Team

Project Proposal Description (February 6)

SENIOR DESIGN Project Plan Form

Project Team Members:

Project Title:

Name Major Signature

XXX 487 Grade GuidelinesGraded Item Weight %

Proposal 10Preliminary Design Review - Written (includes project plan form) 30 - Oral 10 - Engineering Content 25Professionalism (progress report, responsiveness, ownership, responsibility, ethics, etc.)

15

Test Plan 10Final Exam -5 or 5

TOTAL 100

Feasibility and Merit Analysis

• Must have one formal MA in PDR

• All design decisions must be justified with analysis! But, the formal MA process learned in EGR 107 is not the only method to communicate decision making

PDR/CDR Grade ConsiderationsAll Projects are NOT Created Equal

Box

Fancy digitized thermometer

Hovercraft

Space shuttle

Increasing Complexity

Grade Considerations

• Engineering:– Complexity– Difficulty– Quality– Service– Content

• What did your Engineering Education allow you to accomplish? What content delivered distinguishes your abilities from non engineers? Did you develop/design independent from faculty advice?

If I could give just one piece of advice to facilitate your success…

• Frequently meet with– Client– Technical Advisor(s)

• Keep management informed

• Communicate!

XXX 487/488 Webpage

• I’ll post this presentation and additional XXX 487/488 materials on my website

http://faculty.mercer.edu/lackey_l/XXX487488Resources.htm

Questions

• Consider spending the remainder of the class period working with your team

top related