1 / 17

EAS 140 Engineering Solutions

EAS 140 Engineering Solutions. Lecture #28 Course Review. Announcements – A, B. Mon. 12/3: Lecture - Lessons from Failure Wed. 12/5: Lecture - Course Review Thurs. 12/6: In-lab quiz for Thursday labs Mon. 12/10: Final Examination Sample questions available at the EAS 140 Web site

destiny-hawkins
Download Presentation

EAS 140 Engineering Solutions

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. EAS 140Engineering Solutions Lecture #28 Course Review

  2. Announcements – A, B • Mon. 12/3: Lecture - Lessons from Failure • Wed. 12/5: Lecture - Course Review • Thurs. 12/6: In-lab quiz for Thursday labs • Mon. 12/10: Final Examination • Sample questions available at the EAS 140 Web site • Will emphasize material from lecture and case studies; no computing from lab

  3. Announcements – C • Tues. 12/4: In-Class Ethics Case Study • Thurs. 12/6: Lecture - Lessons from Failure and Course Review • In-lab quiz for Thursday labs • Mon. 12/10: Final Examination • Sample questions available at the EAS 140 Web site • Will emphasize material from lecture and case studies; no computing from lab

  4. Announcements - D • Wed. 12/5: Lecture - Lessons from Failure • Thurs. 12/6: In-lab quiz for Thursday labs • Fri. 12/7: Course Review • Mon. 12/10: Final Examination • Sample questions available at the EAS 140 Web site • Will emphasize material from lecture and case studies; no computing from lab

  5. EAS 140 Final Exam Date and Time: • Monday December 10, 2001 • 11:45 am to 1:45 pm Place: • Last name starting with: • A-G 201NSC • H-K 210 NSC • L-Z 225 NSC Exam Format: • 60 multiple choice questions • closed book, closed notes

  6. EAS 140 Final Exam Bring: • Two #2 pencils with eraser • Your SUNY card - no card, no exam: We will check ID • No calculators, no notes, no books Material: • Emphasis on the material from lecture and case studies • No Unix, Excel or Maple from lab • See EAS 140 web site for example problems

  7. Course Review • Academic Success Strategies • Computing • Technical Communications • Engineering Problem Solving • Engineering Profession • Learning from Failure

  8. Academic Success Strategies • Manage Your Time Stay informed (syllabus, e-mail) Go to class • Manage Yourself Study habits (in groups, by yourself, 60 hour rule) Take notes Come to class prepared • Manage Resources Seek help (prof, TA, study groups) Seek advisement (SEAS, dept) Case study link: Forced groups can be challenging - Use e-mail, Web to stay informed

  9. Computing • Computers Remember: many types Hardware, software • Computing at UB ACSU vs ENG Case study link: Lots of tools for data analysis available on ENG

  10. Eng. Communications • Written Documents Overall organization - use headings Paragraph and sentence structure - one idea per sentence, paragraph Grammar and spelling - spell checker not enough! Proofreading • Oral Presentations Before - pick one type of visual aid, practice in front of others During - minimize outward signs of nervousness After - seek feedback Case study link: Concise writing that uses data to justify your conclusions

  11. Eng. Communications • Eng. Communications Important also rewarded by employer • Before You Start, Know: goals audience - technical or not? constraints - time, page limits, $$ • Organize use outlines show organization • Showing Data figures for trends, tables for numbers give title, number, and cite in text use scatter plot if x-axis continuous

  12. Eng. Problem Solving • Eng. Analysis Characteristics: well-defined system usually only one solution more science than art Steps: 1. Define problem 2. Gather/verify data 3. Select analysis method 4. Estimate solution 5. Solve problem 6. Check results Case study link: Used in all case studies

  13. Eng. Problem Solving • Eng. Design Characteristics: poorly-defined system more than one solution more art than science Steps: 1. Define problem 2. Gather information 3. Generate multiple solutions 4. Analyze/select a solution 5. Implement solution 6. Evaluate solution Case study link: Computer workstation design

  14. Eng. Problem Solving • Eng. Calculations Have Meaning check with estimation, common sense, units • Engineers Generate/Use Data precision vs accuracy measures of central tendency, variability Case study link: Are data reasonable? Maple, Excel can help

  15. Eng. Profession • Ethics need because engineering is complex and cost of failure is high canons: • 1. Public safety, health and welfare are paramount • 2. Practice only in area of competence • 3. Only truthful public statements • 4. Act as a faithful agent for clients • 5. Avoid deceptive acts • 6. Act honorably, responsibly, ethically, and lawfully When in doubt, first canon rules

  16. Eng. Profession • Professional Registration (PE) need to approve designs, drawings and to use the title “engineer” steps: BS from accredited dept. (like UB) pass Fundamentals of Eng. exam work under PE for 4 years pass Professional Eng. Exam Case study link: Ethics of last case study

  17. Learning from Failure • Engineers design systems so that systems will fail • Remember: too expensive to design a building so it will never fall down • Reasons for Failure • Engineer’s error (Hyatt Regency) • Warning signs ignored (Challenger) • Cycle of overdesigning and underdesigning (Galloping Gertie)

More Related