1 / 18

ECE361 Engineering Practice

ECE361 Engineering Practice. Reporting. Design Process Assures Design will meet Requirements. Stage 1 – Problem Definition & Potential Solutions. Requirements Specification. Brainstorming. Trades. Preliminary Design. Requirements vs. Capabilities. Detailed Design Review.

dions
Download Presentation

ECE361 Engineering Practice

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. ECE361Engineering Practice Reporting Page 1

  2. Design Process Assures Design will meet Requirements Stage 1 – Problem Definition & Potential Solutions Requirements Specification Brainstorming Trades Preliminary Design Requirements vs. Capabilities Detailed Design Review Stage 2 – Design Implementation Testing Reporting Stage 3 – Verification This process is part of what we call Systems Engineering Deliver = $$$ Page 2

  3. Purpose of Reporting • To tell your client what work you have completed • To document your design • To explain the rationale supporting your engineering decisions • To specify your conclusions and recommendations Page 3

  4. Final Report Contents • Needs Analysis • Alternatives • Bases for making decisions • Decisions made • Summary of results • Appendices with technical details Page 4

  5. A Final Report is NOTaCHRONOLOGICALRECORDof yourDESIGN PROCESS Page 5

  6. Final Report Outline • Executive Summary • Introduction and Overview • Design Alternatives • Methodology • Results • Conclusions • Recommendations • Supporting Materials Page 6

  7. Executive Summary • Concise summary (written for your manager) of essential points in the report • Purpose or problem • Method • Results • Conclusions • Recommendations • http://www.sba.muohio.edu/hwi/executivesummary.htm Page 7

  8. Introduction & Overview • Background • Problem or need • Purpose of report • Overview • Prior work Page 8

  9. Design Alternatives • Alternatives Considered • Evaluation of alternatives • Basis for design selected Page 9

  10. Methodology • Engineering Design • Construction • Operation • Verification & Testing Page 10

  11. Results • Test Results • Comparison with Requirements Page 11

  12. Conclusions • Interpretation of Results • What does it mean Page 12

  13. Recommendations • Based upon system designed • Future design recommendations Page 13

  14. Supporting Materials • Appendices for details • Technical details • Computer code • Drawings • CD Roms to support report Page 14

  15. Format of Final Report ECE Department Writing Standards are at http://137.112.38.207/Labs/Documents/ECE%20Writing%20Standards%2011-27-00.PDF Page 15

  16. Assembling the Final Report I • List conclusions and recommendations; • Construct a rough outline to support your conclusions and recommendations; • Review the outline within the team; • Construct and review a topic sentence outline within the team; Page 16

  17. Assembling the Final Report II • Prepare a rough draft (the writing assignments may be distributed among the team); • Revise and rewrite as many times as needed (use only a single editor of revisions); • Read the last draft aloud to catch mistakes and poor wording; • Prepare final version of report. Page 17

  18. Final Report Due Date • The final report is due Friday, November 14, 5PM • The cover page will be initialed by all members of the team. Page 18

More Related