As part of this course you are required to do a term project. The goal is to perform some original research in computer architecture or to scrutinize the results of published work. The default is to do a project in a group of two people. The projects will typically require substantial programming effort. You will be evaluated on the following areas: (1) Your experimental methodology, (2) your written report and (3) your in-class presentation. It is important to use a sound experimental methodology and to document that you did so. Your report should be such that another computer architect can understand what you did, be able to follow your results and have their key most relevant questions answered.
A list of suggested project topics is included at the end of this document.
There are four milestones regarding every project. First you should submit a short description of the proposed project and methodology. Mid-way through your project you will have to meet with me and provide a written update on your project’s progress. At the end of the course you will have to give a 20-minute presentation. Finally, you have to submit a final project report. Here are the dates you should remember:
Tuesday, October 25 Project Proposal due in class
NO
LATE PROPOSALS WILL BE ACCEPTED.
Week of November 14th Project Progress report due on Tuesday in class
You should also setup a meeting with me during this week.
Week of December 5th Project Presentations
NO LATE REPORTS WILL BE ACCEPTED.
This should be an at most two pages. You should explain in the following order:
1. Introduction/Motivation
2. Topic, i.e., what are you going to do.
3. Methodology. Are you going to use a simulator? Which benchmarks? What metrics will you use.
4. Goal: What you promise to deliver at the end.
Remember: while these may evolve or change you are required to start with a meaningful plan. No point starting something if you cannot articulate why this might be interesting or doable.
One page or less. What you have done so far. Difficulties faced. Any changes in your plan.
Try to limit this to at most 10 pages. (Remember: it’s easy to write a lot of text. It’s hard to write concise.) An approximate format is:
1. Introduction: Motivation and Problem statement. VERY VERY BRIEFLY. Also conclude with forecasting what your method and most important results are.
2. Expanded motivation if needed.
3. Related Work.
4. If you are proposing a new mechanism describe it.
5. Methodology. Which benchmarks, what simulation method and which simulator, machine configuration and any other relevant parameters. Also brief summary of your metrics and WHY are you using them
6. Evaluation. One by one the results.
7. Conclusions. “I am so good I cannot stand myself. Maybe I should donate my brain to science” put in less obvious terms. Future directions (not left or right).
NOTE: If you are already working on a topic that can be connected somehow to architecture it may be possible to do your project in that topic. You should, however, discuss this possibility prior to submitting your proposal.
VERY IMPORTANT NOTE: Prior to submitting your project proposal you should discuss your plans with me.