1 / 13

Final Report Specifications

Final Report Specifications. EECS150 Fall2008 - Lab Lecture #13 Chris Fletcher Adopted from slides designed by Laura Pelton. Today. Administrative Announcements Final Project Report The End of the Semester Schedule. Administrivia (1). Final Check-off Wednesday 11/26 11:59PM

cvela
Download Presentation

Final Report Specifications

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. Final Report Specifications EECS150 Fall2008 - Lab Lecture #13 Chris Fletcher Adopted from slides designed by Laura Pelton EECS150 Lab Lecture #13

  2. Today • Administrative Announcements • Final Project Report • The End of the Semester Schedule EECS150 Lab Lecture #11

  3. Administrivia (1) • Final Check-off • Wednesday 11/26 11:59PM • EVERYONE TURN IN CODE BY THIS TIME • Partial credit will be assessed based on this submission • Final Report • Monday 12/5 2:10PM • Bring it to lab and turn it in during lab lecture (hard copy) • Commit soft copy to SVN (“ReportSubmission”) EECS150 Lab Lecture #11

  4. Final Project Report (1) • Sections • Cover Page • Table of Contents • Abstract • System Description • Design Metrics • Conclusion • Suggestions • Appendices EECS150 Lab Lecture #11

  5. Final Project Report (2) • Abstract • ~1 paragraph • Describe overall project • Timeline • General layout • Un-detailed block diagram if you want EECS150 Lab Lecture #11

  6. Final Project Report (3) • System Description • ~5-6 pages of text • Diagrams don’t count for pages • For each subsystem • Description on how it works • Give detailed block diagrams • Timing diagrams for that subsystem • State machine (if applies) EECS150 Lab Lecture #11

  7. Final Project Report (4) • Design Metrics • 1 page MAX (probably more like 1/4 page) • # LUTs • Design/implementation time for each checkpoint • Discussion of design tradeoffs, how things changes EECS150 Lab Lecture #11

  8. Final Project Report (5) • Conclusion • ~1 page • Major bugs you encountered (and how you fixed them) • What you would have done differently • What should we have done differently • Other things you want to say EECS150 Lab Lecture #11

  9. Final Project Report (6) • Suggestions • ~1-2 paragraphs • Suggestions about how this project could have gone smoother • Suggestions for class/project in the future EECS150 Lab Lecture #11

  10. Final Project Report (7) • Appendices • Any other block diagrams that didn’t fit in your report • Timing diagrams if not in the report • Any other diagrams you want to add (that are relevant) EECS150 Lab Lecture #11

  11. Final Project Report (8) • Page Limits • 10 pages of text • Table of contents and cover page do not count • 10 pages of appendices and diagrams • Extra Credit can make your report exceed 20 pages • ANY MORE THAN 20 PAGES WILL BE TORN OFF AND IGNORED!!!! (besides extra credit) EECS150 Lab Lecture #11

  12. Final Project Report (8) • Grading • Final report is 10% of your grade • Almost as much as a checkpoint! • Graded on: • Clarity • usefulness EECS150 Lab Lecture #11

  13. /endnote • Keep in mind, you want this report to show all the hard work you have done this semester • Make it so you could hand it to a possible employer and they would be impressed • Good luck with the rest of the project! EECS150 Lab Lecture #11

More Related