Final reportguidelines
- 1. Instructions and Guidelines for Final Report and Final Presentation 55:089 EE Senior Design Fall, 2008
- 2. Final Report Format • Cover page – title – author – partner(s) – abstract • Introduction – need/rationale – previous work by others (if applicable) – brief summary of project – description of customer
- 3. Final Report Format (Continued) • System Requirements – What is the system supposed to do – What are the quantitative and qualitative performance objectives – What constraints does the system need to satisfy—specifically comment on economic, environmental, social, political, ethical, health and safety, manufacturability, and sustainability – Customer requirements – Comment specifically on how this project has contributed to your perspective on the need for lifelong learning in the practice of engineering – Identify contemporary issues you had to deal with during this project – How has your engineering education helped you understand the impact of your design in a global, economic, environmental, and societal context
- 4. Final report Format (Continued) • Architectural Overview – system level (block diagram) view of your design – technology choices and rationale – relevant standards • Detailed System Design – Description of design – discussion of major design tradeoffs and/or decisions – diagrams, schematics, etc – test procedures
- 5. Final Report Format (Continued) • Results and Conclusion – report on level of success in achieving objectives – reasons for shortfalls – lessons learned • References – relevant books, periodicals, web links, etc referenced in the report
- 6. What is a Requirement? • A requirement is a statement about what the system should do. • A requirement may be a statement about an important constraint that the system must satisfy • A requirement is not a statement about how the system is implemented
- 7. Requirements Examples • Which of these are valid requirements: – The system shall have a range of 300 meters. – The system shall run on a Window XP platform – The system shall be coded in C++ – The system shall use a QJD 1000 microcontroller to interface with the pressure sensor.
- 8. Final Report—Additional Guidelines • Each team should submit one final report – The report should describe each team member’s specific contribution to the overall project
- 9. Final Report—Additional Guidelines (Continued) • Report Format – 10 pages maximum – double-spaced, 12 point font – lengthy documentation such as program code listings can be included as an appendix and is not subject to the 10 page limit. – Report should be written in the third-person – The tone of the report should be professional • proper grammar and spelling • avoid slang, contractions, and informal language
- 10. REMINDER: The final report must address the use of appropriate engineering standards and include consideration of realistic constraints, as appropriate: economic environmental sustainability; manufacturability ethical health and safety social political
- 11. Final Report Submission • Final reports must be submitted electronically • Follow the submission instructions provided under the General Information link on the class web page • Final reports are due on Thursday, December 11, 2008.
- 12. Final Presentations • Final Presentation Dates (in-class): – Tuesday, December 9 – Thursday, December 11 • NOTE THAT THIS TUESDAY IS NOT A REGULARLY SCHEDULED CLASS METING DATE • One presentation per project – 15 minutes, 12 for presentation, 3 for questions • Time limits will be strictly enforced
- 13. Final Presentations (Continued) • All team members must present • Format: – Introduction and general overview of system requirements and architecture by designated team member – presentation by each team member on their portion of the project • Presentation organization should generally correspond to that of the final report • Final Presentations will be rated by the DRB. Other interested parties may be invited as well.
- 14. Final Presentations (Continued) • PowerPoint slides must be submitted electronically no later than 9:00 a.m. on Monday, December 8. Email reports to [email protected]
- 15. Additional Details • The presentation order for the final presentations will be posted on the class web site on Friday, December 5. – Any team that wants to volunteer to present on the first day should contact the instructor no later than Thursday, December 4. – Anyone who cannot be present on Tues or Thurs, December 9 or 11 due to a conflict must inform the instructor of this fact by Thursday, December 4. • Each team should arrange with the instructor and TA separately for a demonstration of the final project sometime between December 8 and December 12.