CS 6000 Research Methodologies
Papers to be Reviewed (Oral Presentation):
Papers to be Reviewed (Written Presentation):
Useful URLs:
Oral Presentation Suggestions:
- talk to your audience, not to your instructor or the screen
- assume your audience is exactly a group of Master's students
- assume your audience knows very little about your particular topic
- try to be as relaxed as possible
- be sure your audience can hear you
- for 15-20 minute talk, consider about 15 slides or so
- start off with an index or table of contents
- then we need to see the point of the paper
- most of your talk should then be on the content
- finish up with contribution, technical quality, strong/weak points, open issues
- you don't have to do all of these but think about them
- if you choose a really light-weight paper:
- there might not be enough "meat" to make it interesting
- you might have to bolster your talk to give more info
- if you choose a more technical paper:
- you have to make sure that you can summarize for the audience
- do not just read your slides
- make short "bullet" items, rather than paragraphs, and then talk more about them
- do not read from another set of notes
- be careful about your organization
- maybe it should not flow exactly like the paper, just consider it
- it's OK to "edit"
- if it's long, you definitely want to get the key points
- try to help your audience with the real "meaning" of the topics
Written Presentation Suggestions:
- select a technical paper
- summarize the technical aspects to demonstrate that you understand it
- assume your audience is your instructor (Ph.D., Professor)
- assume your audience might have had some exposure to the area
- assume your audience has not read the paper in detail
- assume your audience *will* read in detail if necessary
- think of your paper as a "reader", or "attachment" to the source paper
- you don't have to make figures or equations, just refer to the source
- try to get quickly to the heart of the technical material and put it into your own words
- be careful about your organization
- since you are summarizing, maybe there's a different organization than the paper
- the length does not have to be long
- the goal is to summarize
- but it has to be long enough to demonstrate understanding
- 2 pages (maybe too short), 3, 4, 5 (maybe too long)
- the style should be "narrative"
- do not make bullets but rather paragraphs
- if you need to show some math, fine
- but just don't show the same math as in the paper and leave it at that. instead, your job is to convert to words.
- don't write anything "verbatim", paraphrase in your words
- don't waste (stuff) your few pages with algorithm code directly from the paper. instead, refer to the code in the source paper and explain it in your own words.