1 / 26

Engineering Design

Engineering Design. - A general approach. Outline. Form a group Proposal Milestone A - 1 st Demo Milestone B - 2 nd Demo Final check Poster day Final report Assessment Resources Suggested approach. Form a group. Find partners (usually 4 in each group) as early as possible

deanna-martinez
Download Presentation

Engineering Design

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Engineering Design - A general approach

  2. Outline • Form a group • Proposal • Milestone A - 1st Demo • Milestone B - 2nd Demo • Final check • Poster day • Final report • Assessment • Resources • Suggested approach

  3. Form a group • Find partners (usually 4 in each group) as early as possible • Better with a project idea already before looking for partners • Better to find partners with complementary talents and/or skills • Mutual respect

  4. Form a group • Deadline: Sept. 19 • Everybody in C02 will be informed by his/her group assignment no later than Sept. 22

  5. Proposal • Raise and collect possible project ideas • Think of the application, rather than the technology • Think of what is needed, rather than what you are good at • Every partner needs to make contribution to project ideas • Search literature (publications and internet links) for inspirations

  6. Proposal • Identify the project to work with • Comparison and analysis on: significance in application, impact to the general audience, technical soundness, feasibility • Get the opinion from the instructor • Get the unanimous support from every partner on the final selection

  7. Proposal • Prepare for the proposal presentation • Motivation • Background (similar works done by others) • Feasibility (manpower with necessary knowledge and skills involved, time, and funds) • Step-by-step technical approach • Scheduling • Risks and alternative plan

  8. Proposal format • Objectives: (Up to 10 lines) Clear and concise • Resources: People - Names and effective time Facility/Equipment/Software/Funding • Description:(4 pages maximum) Motivation Background (with references) Project details – Provide details of each milestone and expected time for its completion (usually set your target at the Bronze, Silver, and Gold level)

  9. Proposal format • Scheduling: Make use of Gantt Charts • Assumptions/Risks: Examples: • Delayed delivery of components • Components too expensive • Deliverables: Itemize each deliverable (at the Bronze, Silver, and Gold level) • Summary: (Up to 10 lines) Focus on expected end results

  10. Proposal • Proposal due: Oct. 6 • Presentation time: • In the week of Oct. 6-10, at the normal lecture and tutorial hours, 10~15 minutes for each group • Location: BSB-120 (at lecture hours), ABB-165 (at the tutorial hour) • 1st mandatory meeting: • In the week of Oct. 13-17, at the normal lecture and tutorial hours, 15~20 minutes for each group • Location: ITB-A313

  11. Analog electric signal Temperature Pressure Motion ECG signal …… Sensor A/D Processor Digital electric signal Control unit Driving circuit D/A Analog electric signal Display A project example Input Interface Output Interface

  12. Milestone A – 1st demo • At about 1/3 of the time: • Simulation (if possible) is successful • Hardware components are ready • Logic design for the processor is ready • Circuit design for I/O interfaces is ready • Demo: • Show the simulation result (if there is any) • Show the logic and circuit designs • Check the component list

  13. Milestone A – 1st demo • 1st progress report: • Current status: implementation, scheduling, expenditure • Problems encountered • Prediction on progress

  14. Milestone A – 1st demo • 1st progress report due: Nov. 24 • 1st demo time: • In the week of Nov. 24-28, at the normal lecture and tutorial hours, 10~15 minutes for each group • Location: BSB-120 (at lecture hours), ABB-165 (at the tutorial hour) • 2nd mandatory meeting: • In the week of Dec. 1-5, at the normal lecture and tutorial hours, 15~20 minutes for each group • Location: ITB-A313

  15. Milestone B – 2nd demo • At about 2/3 of the time: • Implementation completed at least at the Bronze level • Demo: • Show a closed-loop working system • Identify added functions • Consider how to show the full system in a most attractive way on the Poster Day

  16. Milestone B – 2nd demo • 2nd progress report: • Current status: implementation, scheduling, expenditure • Problems encountered • Prediction on progress

  17. Milestone B – 2nd demo • 2nd progress report due: Feb. 23 • 2nd demo time: • In the week of Feb. 23-27, at the normal lecture and tutorial hours, 10~15 minutes for each group • Location: BSB-120 (at lecture hours), ABB-165 (at the tutorial hour) • 3rd mandatory meeting: • In the week of Mar. 2-6, at the normal lecture and tutorial hours, 15~20 minutes for each group • Location: ITB-A313

  18. Progress report format (for both demos) • Project briefing (in a few lines) • Technical approach • List of tasks • Current status • Problems encountered • Problems yet to be solved

  19. Final check – on Apr. 2 • Check the working status of the fully functional system • Check miscellaneous issues for display: panel posters, power supplies, system settings, possible interferences (space, wireless, etc.)

  20. Poster day – on Apr. 6 • A full day, every partner must show up • Always leave at least one partner at your booth • Every partner must be at your booth for the presentation to examiners, and for possible extra presentations to VIPs • Clean up your booth upon completion, don’t drop any piece in your system

  21. Final report – due on Apr. 13 • Introduction (motivation and background) • Project goals and planned approach • Actual approach (design, modeling/simulation, implementation) • Critical problems solved • Conclusion (final result achieved) • Future plan (any potential market value or specific usage?)

  22. Assessment • Meeting milestones 10% • Proposal 10% • 1st demo 10% • 2nd demo 10% • Final (including final demo, poster, presentation, and report) 40% • Weight factor 0.9~1.1 (depending on technical complexity)

  23. Resources • Manpower: 4 • Time: ~6 months • Fund: ~CAD$200 (on average) • Lab space: ITB-156 (open full time) • IEEE student chapter: PCB milling • Instructor: ITB-A313, ext. 27698, lixun@mcmaster.ca • TAs’ office hour: one hour daily from Mon. to Fri. (check course webpage for location and time)

  24. Suggested approach • Find an application: better to utilize an existing technology to solve a new problem, or enhance a popular technology, rather than to develop a new technology from scratch • Set up step-by-step technical approach that will lead to the final accomplishment of the goal • Complete a design for the whole system • Find components: read data sheet beforehand, make careful comparisons on multiple choices, weigh among performance, cost, and lead time

  25. Suggested approach 5. Run simulations or perform analyses to your design, with components specified by the data sheet 6. Order components or start over again from step 4 or even step 3, depending on the result of step 5 7. Build your system towards the Bronze level 8. Test your system 9. Add features to your system to reach the Silver, or Gold level

  26. Suggested approach 10. A few hints in the execution process: • Work on a parallel, rather than a serial fashion whenever possible (for saving time) • Always have a plan B • Think about if your system will be well presentable to the general audience on the poster day

More Related