EECS150 Spring 2008 Partner Evaluation UNIVERSITY OF CALIFORNIA AT BERKELEY COLLEGE OF ENGINEERING DEPARTMENT OF ELECTRICAL ENGINEERING AND COMPUTER SCIENCE FINAL REPORT GUIDELINES 1. MOTIVATION Congratulations on surviving through this semester’s CS150 project. While you have no doubt spent many nights coding and debugging in Cory, this final writeup is your chance to consolidate all of the design work that went into your finished project into a single report. In the future this may be useful for reference purposes or to hand to prospective employers. Because of its importance, it will be worth approximately the same amount as an entire checkpoint and thus you should take the time to make it as polished and comprehensive as possible. 2. OVERVIEW The final report will consist of the following components: - Cover Page - Table of Contents - Abstract - System Description - Design Metrics - Conclusion - Suggestions - Appendices The total page limit is 20 pages, consisting of approximately 10 pages of text and 10 pages of appendices and diagrams. Anything beyond 20 pages will be torn off and ignored. 3. SECTIONS a. Cover Page and Table of Contents: Self-explanatory. b. Abstract: A brief (approximately 1 paragraph) description of the overall project including a timeline, general layout description and a very high level block diagram if you want.EECS150 Spring 2008 Partner Evaluation c. System Description: Approximately 5-6 pages of text with additional space for diagrams. For each subsystem describe how it works, give a detailed block diagram, timing diagrams if necessary and state machines if applicable. d. Design Metrics At most 1 page including # of LUTS used, design and implementation timing, and a brief discussion of tradeoffs involved with design in terms of these metrics (and others in the synthesis report) e. Conclusion About a page long detailing any extra features you implemented, any major bugs you encountered, what you would have done differently and anything else that seems suitable to discuss. f. Suggestions A couple paragraphs with suggestions about how to improve the project for future semesters and what could have been better. g. Appendices This is the place for all the block diagrams, timing diagrams or FSMs that didn’t fit in your
View Full Document
Unlocking...