Final Design Report

Your final report describing your design should be organized, detailed, and concise. The information must be clear and legible, accompanied by appropriate, well-laid-out diagrams. It is your responsibility to convey information about your final design so that we can appreciate your work. As in real life, the evaluation of your project (i.e., your grade) will be based on its presentation—clarity, organization, proper use of language, neatness, spelling, etc.—as well as on its technical qualities.

Report Checklist

You may use the following list as a guideline in organizing and determining the contents of your report.
  1. Title Page, Abstract, Table of Contents, Table of Figures
  2. Introduction: General requirements, features, and design approach (high-level goals and philosophy)
  3. Design discussion: Top-down discussion of your entire design, including high-level and low-level design considerations, decisions, and tradeoffs.
  4. Conclusion: Discussion of constraints, performance, cost (number of primitives used), recommendations for future designs, known bugs and their likely causes and possible fixes.
  5. Appendices
    1. Complete schematics and diagrams
    2. Critical path analysis
    3. Parts list (how many of each primitive did you use)
    4. Simulation results, including demonstrations of any remaining bugs, the working test programs, and programs demonstrating any untested features of your design (two-way associative caches, write-back caches, external interrupts etc. but not untested instructions)