Main »

Project

Tasks

edit SideBar

On this page... (hide)

  1. 1. Schedule
  2. 2. Project Options
  3. 3. Proposal
  4. 4. Progress Report
  5. 5. Talks
  6. 6. Final Report
  7. 7. Topics

1.  Schedule

  • Proposal: At Lecture Fri Mar 11
  • Progress Report: At Lecture Wed Apr 6
  • Talks: Mon May 2 (starting at 12:30 & continuing at lecture), & Wed May 4 (starting at 12:30 & continuing at lecture)
  • Final Report: Hardcopy in my mailbox or email, 8:59 AM Tue May 10 Wed May 11

2.  Project Options

The project has two options.

(a) Original Research. The first option is to do some original research in computer architecture (e.g., write a simulator and gather some simple numbers) or to re-validate data found in a published paper. This type of project is especially recommended for students considering a Ph.D. You will be graded on how well you define your problem, survey previous work, design and conduct experiments, and present your results. The goal to shoot for is conference paper, like the ones in your reader. Since time is limited, however, the above goal is hard to reach, and I will reward those that aim high even if they do not completely succeed. The key is insuring that some aspects of your work are completely done; it is very hard to grade a project where the simulator did not quite work. This type of project should use groups of three (preferred) or two.

(b) Survey Paper. In the second option, you may work alone to write a paper that surveys an area within computer architecture. The paper should: summarize work in an area, giving extensive references, present opinions of others for and against various options (with references), and conclude with your opinion of the strengths and weaknesses of arguments presented above. You will be graded on the completeness of your survey, the accuracy of your summaries, the support you give for your opinions, and the quality of your presentation. Since a survey paper is "safer" than a research project, I will hold survey papers to a higher standard of completeness and analysis of the literature.

I normally accept no late assignments. For this project, papers turned up to 24 hours hours late will be accepted with a 25% penalty. Don't avail yourself of this option; your hard work deserves full credit.

I strongly recommend that you come by my office hours (a) before finalizing your project proposal and (b) before writing your progress report. My experience can aid you and not re-discovering many past mistakes.

3.  Proposal

I strongly recommend that you come by my office hours before finalizing your project proposal. My experience can aid you and not re-discovering many past mistakes.

Proposals should be about two pages long. They should include:

  • A description of your topic,
  • A statement of why you think the topic is interesting or important,
  • A description of the methods you will use to evaluate your ideas, and
  • References to at least three relevant papers you have already read and a plan to address other related work (see Text and References).

4.  Progress Report

Progress Reports should include a revised version of the proposal plus one page describing accomplishments so far. Concentrate on describing sub-tasks completed, rather than the tasks started. For example, say ``completed simulator modification to watch and fake FOO rather than saying ``started simulator modifications.

5.  Talks

We will divide up the last few lectures into 20-minute-ish conference-style talks. Depending on class size, some talk may be scheduled at alternative times. All group members should deliver part of the talk. The talk should give highlights of the final report, including the problem, motivation, results, conclusions, and possible future work. Time limits will be enforced to let everyone present. Please, practice your talk to make it better and see how long it is. Have a plan for what slides to skip if you get behind.

  • PRINT SLIDES: Make sure that I can take notes on a six slides per page copy of your (near) final slides. Either print them for me or email me pptx by 6:59am the day of your talk with subject [CS/ECE 757] Project Final Talk.
  • PRESENT SLIDES: By default, please present using one laptop from your group. If you wish to present on my laptop, follow the email rules above and note in the body of the message that you want to present with my laptop.

6.  Final Report

Reports should consist of an abstract, body and optional appendices, much like a conference paper. The abstract should summarize the contributions of the report in one or two paragraphs. The length of the body should be the equivalent of 15-20 pages at double-spaced 10-point. Additional supporting material of any length can be put in appendices. I will read the body and only skim appendices. See your reader for examples.

Put final reports in my mailbox or email with subject: [CS/ECE 757] Project Report.

7.  Topics

You are encouraged to come up with your own topic. Ideally, the topic will be related to your current research interests.

There can be value in combining your project with other work in one of two ways. First, if you have active research in a related area (e.g, an RA), you can do a deeper project by combining your current (supported) research with your course project. Second, it is also possible to do a single multi-disciplinary project to satisfy multiple courses (e.g., CS736). However, this must be coordinated with the other instructor(s) and you will be expected to do two (or more) projects worth of work. In all such cases, it is imperative that such overlaps be disclosed at the proposal stage so that we can address the scope of research that will be required.


Page last modified on April 28, 2016, at 09:18 AM, visited times