CSE321: Computer Architecture I

Final Project

• Project Description: pdf | ps
• Project grade distribution:
  • proposal: 10%
  • progress report: 10%
  • presentation: 10%
  • final report: 70%
    • expected results: 30%
    • technical depth: 15%
    • writing: 25%
• Due Dates:
  • Nov. 10: Project proposal
  • Nov. 24: Progress report
  • Dec. 8: Project report
• Presentation Guidelines:
  • Presentations will take place in class on Dec. 6 and 8. Each class period will start at 1:50 and end at 3:30.
  • Each student is allotted 4-5 minutes for the presentation.
  • Each student needs to fill an evaluation form for each team's presentation.
  • The evaluation form shows how a presentation will be judged.
  • Make sure that the presentation file is put in the web space of one of the team members for easy access from the classroom computer.
  • Make sure that the team number (assigned) as well as the presenters' names (in the order of the presentation) are provided on the title page.
• Final Report Guidelines:
  • A formal technical report format should be followed. Following are some basics:
    • Think about the reader. Assume the reader is your manager whose knowledge about computer architecture is about the level of your fellow students in this class.
    • Include at least sections on introduction, technical approach, experimental results, and conclusion. You can use whatever section titles you feel are most descriptive and feel free to use more subsections to help the reader.
    • Clearly describe your proposed design and compare it with the Simple12 design given in class.
    • Include figures and tables wherever necessary to help with the description. (I don't think you would like to read a 10 page technical report without any figures or tables.)
    • Use the formal English language (e.g., no slangs, no contractions). Also make sure that correct technical terms are used.
    • PROOFREAD the report before turning it in.
    • If you want to include some sample VHDL code, ModelSim waveforms, etc., put them in the appendix and give a short description.
  • The report will be graded not only for its technical strength but also writing style.
  • To accompany the report, the following also needs to be done by 12/8:
    • Make a separate directory in the dropbox of one of the team members and name it "project". Indicate this choice in the final report.
    • Put a copy of ALL relevant VHDL files in the directory.
    • Create a "README" file to describe clearly what each VHDL file is for and how to start simulating the design.
    • This directory will be used to grade the "expected result part" of the final report.