Pipelined Processor Design Final Presentation
Final Practical Presentation
General requirements:
During Finals Week you will give a presentation about your processor design.
- The duration the presentation should be about 5 minutes. Total time allowed between start of one presentation and the start of the next: 10 minutes.
- Every member of the team must be present for the presentation and also participate by presenting some part of the presentation.
- Prepare a professional presentation. You may wish to use PowerPoint or other similar tools. Practice your presentation before the day of the presentation.
- Your presentation will be evaluated by your classmates attending your presentation. The instructors will provide the evaluation criteria.
Content:
You will be presenting the design of your new instruction from Practical 9. Your presentation should focus on what your instruction does, why the design is good, and what the implications of the design are. Your goal is to convince a set of investors (your classmates) to fund your team's design. You are presenting to a room of expert processor designers, so your presentation should focus on the technical details that make your design unique. You also need to provide compelling evidence that your design is "good", but you probably need to define what "good" means in your context (think back to our discussion of performance). Here is a list of detailed requirements:
- Your presentation should be no more than 7 slides including a title slide that lists your team name and all team members names.
- You should show the RTL that describes your instruction, and a modified datapath that highlights any changes you made to implement your hardware.
- You should describe the implications of your design (consider things like performance, cost, and usability).
- You should show evidence of the usefulness of the instruction by providing some assembly code snippets that show the use of your instruction.
- You should discuss the performance of the
relPrime(5040)
program before and after adding your new instruction to your processor.
Don't simply read words off your slides to the audience. You should use the slides to reinforce what you say, and support you with evidence. Don't use them as note cards for yourself (if you need notecards you should make yourself some!). Consider using the Assertion-Evidence Slide Design approach.
You may optionally want to have some "extra" slides ready with figures or diagrams to help answer any questions you may expect the audience to have (these do not count towards your 7 slide limit).
Turning it In
Add and commit a copy of your presentation materials to the root of your github repository.