|
Wednesday,
22 Nov (Day Prior to Thanksgiving) |
||
|
Team |
Topic |
|
|
Hartig |
Foster |
Dynamic
Microcell Assignment for Massively Multiplayer Online Gaming |
|
Stolsig |
Kysiak |
Doom as an Interface for Process
Management * |
|
Dailey |
|
Multi-Core
Microprocessors: Tradeoffs and Potential Solutions |
|
Tantillo |
Fallon |
Microarchitectural Denial of Service:
Insuring Microarchitectural Fairness. |
|
|
|
|
|
Friday, 1
December (Day prior to Army-Navy Game) |
||
|
Team |
Topic |
|
|
Syme |
|
Measuring Real-Time Op Sys Performance * |
|
Sung |
Cosgrove |
Comparison of old fashioned OS to the latest OS |
|
Fernandez |
Mott |
A
Reconfigurable Generic Dual-Core Architecture |
|
|
Hesch |
The
Problem with Threads * |
1. Purpose. To give exposure to what someone pursuing graduate education in computer science can expect as part of researching the background of his or her masters-level thesis topic. Graduate programs require you to develop a thesis paper, typically broken into several major parts. The first part of a thesis, commonly termed a literature search (and the focus of your presentation in this course), includes an examination of current work related to your thesis topic. For this presentation, you will do an in-depth reading of a previously published paper (including reading any references necessary for you to understand the author’s work), and present the author’s work to the rest of the class. Note that you do not have to write your own paper, rather, you are to present a previously published paper.
2. Paper Selection. Go to Nimitz Library and find an operating systems related paper that provides “depth” in an area that interests you from one of the sources listed in the below Paper Sources section. Providing depth means that the paper goes into the nitty-gritty of a research topic, as opposed to a paper that merely provides an overview. You may use scholarly sources other than the ones listed below, but only with permission of the instructor. Non-scholarly articles such as those typically found in Byte magazine, PC Magazine, etc, will not be permitted, although they may provide a good initial discussion to help you find a topic that interests you. The article you choose does not have to be related to concepts discussed in class, but it must be related to operating systems. If your topic is related to topics discussed in class, you must go into additional detail beyond what was covered in class. Read the article through several times, looking up and reading referenced papers as needed to make sure you understand the content of the paper.
3. Scheduling your Paper Presentation. Once you have identified the paper you wish to present, e-mail the instructor and give:
4. Presentation Deliverables. Present the author’s work using appropriate visual aids. Your presentation is to take between 8-10 minutes (if necessary, your team will be cut off after 12 minutes so that all teams can complete their presentations during the scheduled period). All team members must participate equally, including speaking, during the presentation. Your presentation will be graded according to the criteria posted on the course web page. In your presentation, include:
a. A detailed presentation of the contents of the paper you selected (including all figures included in the paper), as well as additional information needed to understand the author’s work. Use Powerpoint and the following format:
i. a title slide (include the exact citation information from 3 above)
ii. an introductory slide (include a discussion of why you chose this particular article),
iii. a background slide (or two),
iv. several slides that give a detailed discussion of the main points of the paper (including all figures from the paper, you must understand the paper’s content well enough to talk intelligently about the paper’s figures), and
v. a conclusions slide (include your suggestions for someone who is considering continuing the author’s work).
b. At the start of your presentation, provide your instructor with:
i. a paper copy of the paper being presented,
ii. a paper copy of the slides used in the presentation, (printed as “handouts” no more than 4 slides to a page (slides must be clearly readable in this handout form, so use appropriate font/size/colors), and
iii. a copy of the presentation grading sheet (with your name and the paper’s title filled in) available from the course web page.
iv. Failure to provide the instructor with paper copies of the above at the start of your presentation will result in a 10 point deduction in your presentation grade, and the items will still have to be turned in in order to receive any grade other than a zero. Be sure to test run your presentation on the machine in the classroom ahead of time to be sure you do not encounter foreseeable technical difficulties during your presentation.
5. Allowable Paper Sources (all available through Nimitz Library. Note that you may use scholarly sources other than the ones listed below, but only with prior permission of the instructor). You may pick any operating systems related paper that appears in Communications of the ACM or IEEE Computer. You are encouraged to pick a current topic of interest to your team such as
a. Microsoft’s Longhorn (focusing on something of interest to you such as writing and deploying applications in the next generation of Windows or encryption systems for Windows).
b. A Linux topic of interest to you (such as how to write a Linux device driver).
c. Operating systems requirements for machines with dual core processors.
d.
Other operating systems topics of interest to you.
If you’re having trouble coming up with a topic of interest
to your team, you may chose one of the
below papers, or search for a related one that better meets your team’s interests. Remember that the use of any
source other than Communications of the
ACM or IEEE Computer must be
approved by your instructor.