Project Proposal ECE 445 Lecture 2 Jan 27, 2015 ECE Main Slide.

Slides:



Advertisements
Similar presentations
Creating a Winning E-Business Second Edition
Advertisements

Instructions and Guidelines for Final Report and Final Presentation 55:089 EE Senior Design Fall, 2008.
Software Quality Assurance Plan
EPICS Design Review Template Notes:  Use the template as a guide to preparing your presentation….you may add, subtract, or rearrange as needed to tell.
Math 1160 – Finite Mathematics and Its Applications Openers.
WEBQUEST Let’s Begin TITLE AUTHOR:. Let’s continue Return Home Introduction Task Process Conclusion Evaluation Teacher Page Credits This document should.
Writing a Technical Manual Wentworth Institute of Technology Elec163 Electronic Design I Professor Tim Johnson.
Your Project Proposal.
Key dates lists of suggested projects published * *If you or your partner are working in a biology lab, try to find a relevant project which can.
Your Presentation Title Names of Team members Advisor name EE496A Midterm Presentation Fall, 2006.
Technical Communication 1
Engineering H193 - Team Project Gateway Engineering Education Coalition Final Report – An Overview Week 4 Day 2.
CS & ECE Senior Design Project Winter 2008 Karen Davis Chia Han Altan Ferendeci.
Chapter 2- Visual Basic Schneider1 Chapter 2 Problem Solving.
CSULB EE400D Documentation Instructional Series
The Project AH Computing. Functional Requirements  What the product must do!  Examples attractive welcome screen all options available as clickable.
Project Management Lecture 5+6 MS Saba Sahar.
Abdulmotaleb El Saddik Prof. Dr.-Ing., FIEEE, FCAE University Research Chair ELG 4913F ELG 4913F Electrical Engineering Design Project II
IENG 471 Facilities Planning
FCS - AAO - DM COMPE/SE/ISE 492 Senior Project 2 System/Software Test Documentation (STD) System/Software Test Documentation (STD)
Software Requirements Engineering CSE 305 Lecture-2.
Project Proposal ECE 445 Lecture 2 September 1 st, 2015.
10/10/2015 IENG 471 Facilities Planning 1 IENG Lecture END Project Report Requirements & Project Presentation Information.
Software Engineering Management Lecture 1 The Software Process.
Communication 2 Report Writing.
ECE445: The Design Review Raj Vinjamuri February 3, 2014.
BIS3324 Group Assignment – Schedule, guideline & templates (2015-Jan Semester)
ECE 4901 Computer and Electrical Engineering Design I John Chandy
Project Proposal ECE 398 PSC. General Information Due Date – Wed 9/23 at Midnight – Submit PDF to PACE Should be 1-2 Page overview of your project – Not.
CSULB EE400D DOCUMENTATION INSTRUCTIONAL SERIES PRELIMINARY DESIGN REVIEW.
6/3/2016 IENG 471 Facilities Planning 1 IENG 465 – Final Design Project Report & Presentation Requirements.
Project Documentation Steve Harris SPASH PLTW - Biotechnical Engineering.
Project Documentation Presentation Fall Outline Purpose Types of Documentation Individual Documentation Project Documentation Team Documentation.
ECE445: The Design Review Sept 2, Documentation Roadmap Request for Approval Proposal Design Review Final Paper &Presentation Sept 10Sept 16Sept.
ECE398: The Design Review Fall What the Design Review is  Board meeting with engineers- (faculty, TA, classmates)  Structured discussion of your.
ECE 4901 Computer and Electrical Engineering Design I John Chandy
Design Report – Fall Semester. Title Page List name of project and team number List date List team members, advisor, sponsor Team logos.
Engineering H193 - Team Project Gateway Engineering Education Coalition P. 1 Spring Quarter Final Report – An Overview Week 4 Day 2.
The Draft and Formal Project Proposal
Now what? 1.  I have short-listed projects I am interested in  I know the types of projects I would like to pursue  I have an idea of the resources.
Knocker Unlocker JACOB GILBERT | SENIOR DESIGN PROJECT 1.
Research Methods Technical Writing Thesis Conference/Journal Papers
Chapter 2- Visual Basic Schneider1 Chapter 2 Problem Solving.
Preparing Your Final Report for ECE 445, Senior Design Jamie Hutchinson ECE Publications Office
ENGR 1181 College of Engineering Engineering Education Innovation Center Introduction to Technical Communication.
TMP3413 Software Engineering Lab Lab 01: TSPi Tool Support.
Reform Groups and Analyze Preliminary Designs. Schedule Week 6 Lab Small Group Presentations Form into three large teams Agree on problem statement and.
Dr. Thomas Tomasi Associate Dean, Graduate College.
Logic Circuit Teaching Board Team 3 David Lee, Younas Abdul Salam, Andrzej Borzecki ECE 445 Senior Design TA: Ankit Jain Date: April 27, 2015.
Modular Swimming Pace Aid ECE 445 Group Members: Igor Fedorov, Ryan Cook, Michael Chan Professor Carney (TA Ryan May)
Welcome to UTS 101 – STEP 1, Week #1 Instructor: Brian Fortney  Please sign in  Pick up a copy of each handout  Please do not sit at back 2 tables 
Roller Coaster Overview ENGR1182.  As part of the project in ENGR , your team will: Innovate, Design, Build, Document, Test a model roller coaster.
From Notebook to Report Guidelines
Dr. Thomas Tomasi Associate Dean, Graduate College
ED 690: Reflecting, Writing, and Reviewing the PDP
EPICS Design Review Template Notes:
Roller Coaster Overview
Planning Phase: Project Control and Deliverables
Introduction to New Product Development (Portfolio)
RFIC2018 Interactive Forum (IF)
Technical Report Writing
Project Title, date “Team Name: Team members, …”
Writing a Technical Manual
Proposal & Leadership Documents
RFIC Interactive Forum (IF) PowerPoint Presentation Template
Software Requirements Specification (SRS) Template.
Basic Design Documentation
Interactive Forum (IF) Poster Guidelines
Preparing Your Final Report for ECE 445, Senior Design
Presentation transcript:

Project Proposal ECE 445 Lecture 2 Jan 27, 2015 ECE Main Slide

Begin working on your proposal once your project is approved! The Project Proposal The purpose is to articulate: Benefit to end user Product features Design overview Anticipated performance specs Project plan and timeline Begin working on your proposal once your project is approved!

Document Outline Introduction Design Requirements and Verification Title Page Objectives Design Block design Block description Requirements and Verification Requirements Verification Tolerance Cost and Schedule **See commented example on course website! Commented Example of Project Proposal

1. Introduction Title page Statement of Purpose (Motivation) Project title, group members, TA, date, course # Statement of Purpose (Motivation) Why did you select this project? Objectives Goals: What problem is being solved? Functions: What is the product supposed to do? Benefits: How is it good for the consumer? Features: What aspects make it marketable?

Example: Swim Pace Aid Objectives Goals Functions Benefits Features Improve athletic training and coaching for swimmers Functions Light a sequence of LEDs at a set pace to guide swimmers Benefits Provide real-time visual indication of pace to swimmer Features LED panels submergible in up to 2.5 meters of water Lap pace ranges between 8 and 45 seconds, 0.5 second increments

2. Design Block Diagram Block Description Modular Interconnections Consider high-level and detailed-level diagrams (example on website) Block Description Matches block diagram 1-1 Describe function of each block Contribution to overall system Interconnection Functionality Use quantitative, specific language Summary of system followed by specific descriptions

Example: Swim Pace Aid

Example: Swim Pace Aid Power Supply Not quantitative The power supply will provide power for all of the components in the system. The power supply will consist of 3 AA batteries wired in series to provide a 4.5 V voltage source. The power supply will have reverse voltage protection in the form of a MOSFET reverse voltage protection circuit. The MOSFET circuit is a much more efficient alternative to a diode reverse polarity protection circuit and will increase the lifetime of the batteries in the voltage source. A low dropout regulator (LDO) or linear regulator will be used to step down the voltage source voltage to 3 V in order to provide power for the microcontroller and communications modules. The voltage at the output of the reverse polarity protection circuit (~4 V) will be sent to the LED module. Not quantitative

Requirements and Verification At least one per block Concise and specific – don’t need full sentences Define functioning behavior Project should work if all requirements satisfied Verification Test procedure for each requirement Quantitatively define “passed” test Describe how results will be presented (i.e. tables, graphs)

Example: Power Supply Requirements Verification Power Supply must provide 12 V ± 0.2 V at output. Connect output of the power supply to multimeter. Check that output voltage falls within spec. The measured value will be presented on a number line with specified voltage range indicated. Quantitative values on this side

Tolerance Analysis Critical part of the design process Pick 1 significant component of your design Why is this component significant? What is an acceptable tolerance and why? Relate back to requirements on that module What is the test procedure? How do you check the component is operating within that tolerance? Use quantitative language If I choose resistors with +/- 10% tolerance, will the resulting variation in gain of my amplifier be within spec? Tolerance analysis isnt an experiment done after the project is constructed to find the tolerance of some parameter. At any point in the semester: Test this component at the extremes and include results in lab notebook and final report.

4. Cost and Schedule Cost Labor = (Ideal salary) * 2.5 * (hours to complete) Sum labor costs for each partner in the project, to compute the total labor cost Parts = Sum of cost of all parts Include part # GRAND TOTAL = LABOR + PARTS

Example: Swim Pace Aid Person B Person C Person A

Example: Swim Pace Aid

Keep careful track of all costs and schedule changes along the way—you’ll need them for the final report!

Schedule Use the modularity of your design to allocate responsibility Weekly time-table outlining project completion Only one person responsible for each task At least one task per week per person Responsibility ≠ workload Define tasks in terms of deliverables Research and ordering parts not considered weekly tasks (by themselves) No "To be determined" weeks Be SPECIFIC Use the modularity of your design to allocate responsibility

Example: Swim Pace Aid Person B Person C Person A

Additional Info Proposal due Wed 2/17 at 4pm 25/515 points Grading Scheme and Evaluation sheets located here Detailed description located here Web resources in “The Written Report” section here IEEE Citation Guidelines LaTeX template Label figures, schematics, etc. Approx. 5 pages (of writing) Upload PDF to PACE