How to Read Technical Papers

Embed Size (px)

Citation preview

  • 8/11/2019 How to Read Technical Papers

    1/36

  • 8/11/2019 How to Read Technical Papers

    2/36

    2

    Challenges for reading:

    Written succinctly

    Page limitation

    Accepted style Dont write verbosely

    For specific audience

    Knows area well

    Engineering Research Papers

  • 8/11/2019 How to Read Technical Papers

    3/36

  • 8/11/2019 How to Read Technical Papers

    4/36

    4

    Despite different contents, papers have verysimilar structure

    Paper reading is a repetitive activity

    By knowing the structure of papers, you may want toread a paper out of order

    General Structure of a Paper

  • 8/11/2019 How to Read Technical Papers

    5/36

    5

    Abstract:

    Abstract of the paper:

    A brief intro

    Problem statement

    Authors contribution Achievements

    General Structure of a Paper

  • 8/11/2019 How to Read Technical Papers

    6/36

    6

    Introduction:

    The entry statements to the subject:

    More clear statement of the problem

    What is solved

    Motivations

    Why it is important

    Literature review

    Sometimes in a separate section

    Contribution

    How it is solved (one/two before lastparagraphs)

    Organization of the paper

    General Structure of a Paper

  • 8/11/2019 How to Read Technical Papers

    7/36

    7

    Literature Review:

    Related work

    How they approached the same/relatedproblem

    What are the disadvantages In the body of the paper, they should show that their paper

    doesnt have these problems

    General Structure of a Paper

  • 8/11/2019 How to Read Technical Papers

    8/36

    8

    Body:

    Basic concepts

    Terminology (definitions)

    Assumptions

    Their solution

    Experimental Results:

    The environment for experiments

    Results

    Analysis of results

    Conclusion and Future works

    General Structure of a Paper

  • 8/11/2019 How to Read Technical Papers

    9/36

  • 8/11/2019 How to Read Technical Papers

    10/36

  • 8/11/2019 How to Read Technical Papers

    11/36

  • 8/11/2019 How to Read Technical Papers

    12/36

    12

    Pass 1 (get general idea):

    A quick scan to get the main idea

    Can decide whether you need to do more

    passes

    5-10 minutes

    Three-Pass Approach

  • 8/11/2019 How to Read Technical Papers

    13/36

    13

    Pass 1 (get general idea):

    Steps:

    1. Carefully read the title, abstract, [parts

    of introduction]

    2. Read (sub-)sections headings

    3. Read conclusions

    4. Glance over the references

    Three-Pass Approach

  • 8/11/2019 How to Read Technical Papers

    14/36

  • 8/11/2019 How to Read Technical Papers

    15/36

  • 8/11/2019 How to Read Technical Papers

    16/36

    16

    Pass 2 (grasp the papers content):

    Read the whole paper but Ignore details

    E.g., proofs.

    ~ 1 hour

    Appropriate for a paper in which you are interested,

    but does not lie in your research specialty

    Steps:

    1. Look carefully at the figures, diagrams, etc.

    To get an idea of the proposed solution, etc.

    2. Mark relevant references for further reading Write a statement in front of it

    Keep a list of references which you wish to get back to

    Three-Pass Approach

  • 8/11/2019 How to Read Technical Papers

    17/36

    17

    Pass 2 (grasp the papers content):

    After pass 2: should be able to:

    Summarize the main point, with supportingevidence, to someone else

    If you dont understand it, possible reasons: Subject matter is new to you, with unfamiliar

    terminology and acronyms

    Authors may use techniques/matters that you

    dont understand Poorly written

    Youre tired!

    Three-Pass Approach

  • 8/11/2019 How to Read Technical Papers

    18/36

    18

    Then, possible options (based on your judgment):

    Set the paper aside, hoping you dont need tounderstand the material to be successful

    Return to the paper later, perhaps after readingbackground material

    Persevere and go on to the third pass

    Three-Pass Approach

  • 8/11/2019 How to Read Technical Papers

    19/36

    19

    Pass 3 (understand the paper in depth):

    ~5 hours for beginners, ~1 hour for experienced reader

    After pass 2: should be able to:

    identify and challenge every assumption in everystatement (hidden failings and assumptions)

    think about how you yourself would present aparticular idea

    propose ideas for future work

    Should be able to virtually re-implement the paper

    i.e., making the same assumptions as the authors, re-create the work

    Three-Pass Approach

  • 8/11/2019 How to Read Technical Papers

    20/36

    Questions to Be Answered by Reader

    20

  • 8/11/2019 How to Read Technical Papers

    21/36

    21

    What do you want from the paper:

    Questions which you should look for answers to:

    What are the motivations for this work?

    Expectation: a problem solved that no one hassolved before

    Two types of problems:1. Peoples problem (often not stated): benefits that are

    desired in the world (e.g., errors in mobile comm,slow computers)

    2. Technical problem: why doesnt peoples problemhave a trivial solution

    What are previous solutions

    and why they are not adequate

    Questions to Be Looked for

  • 8/11/2019 How to Read Technical Papers

    22/36

    22

    What is the proposed solution? (hypothesis or idea)

    Why is it believed that it will work?

    Why is it believed that it is better than others?

    How is the solution achieved (or achievable)?

    Questions to Be Looked for

  • 8/11/2019 How to Read Technical Papers

    23/36

  • 8/11/2019 How to Read Technical Papers

    24/36

    25

    What are the future directions for this research?

    Their insight

    Your own ideas (take notes for future research) Can it be generalized/specialized?

    Can the flaws be overcome?

    Can the assumptions be corrected and solve it again?

    What is your take-away message from this paper? Sum up the main implication of the paper from your own

    perspective

    Very useful for quick review and refreshing your memory

    Forces you to try to identify the essence of the work

    What questions are you left with?

    What questions would you like to raise in an open discussion

    of the work

    What do you find difficult to understand?

    Questions to Be Looked for

  • 8/11/2019 How to Read Technical Papers

    25/36

    Note Taking Practice

    26

  • 8/11/2019 How to Read Technical Papers

    26/36

  • 8/11/2019 How to Read Technical Papers

    27/36

    28

  • 8/11/2019 How to Read Technical Papers

    28/36

    29

    Note taking:

    Mark the important paragraphs according to

    motivation/problem

    idea/solution

    their evaluation contributions

    On the front of the paper, write down the take-awaymessage

    Note Taking

  • 8/11/2019 How to Read Technical Papers

    29/36

  • 8/11/2019 How to Read Technical Papers

    30/36

  • 8/11/2019 How to Read Technical Papers

    31/36

    Notes

    Components of notes:

    Take-away message (your own):

    Problem

    Solution Use the words which will remind you instantly about the take-away

    message

    Main differences with other papers

    Inspired ideas

    Critical views

    Key questions

    Classification of papers

    32

  • 8/11/2019 How to Read Technical Papers

    32/36

    Literature Survey

    33

  • 8/11/2019 How to Read Technical Papers

    33/36

    Literature Survey

    What is literature survey?

    Use of ideas in the literature to justify

    the particular approach to the topic,

    the selection of methods, and

    demonstration that this research contributessomething new. [Hart98]

    Novice researchers view:

    A collection of summaries of papers!

    34

  • 8/11/2019 How to Read Technical Papers

    34/36

    Literature Survey

    Effective literature survey:

    Should explain how one piece of research builds on

    another [Shaw95]

    If I have seen further, it is by standing on ye sholders of

    Giants. Isaac Newton

    Creates a firm foundation for advancing knowledge

    Facilitates theory development

    [Closes areas where a plethora of research

    exists]

    Uncovers areas where research is needed[Webster02]

    35

  • 8/11/2019 How to Read Technical Papers

    35/36

    Literature Survey

    Authors of literature review are at risk for producing mind-

    numbing lists of citations and findings that resemble a

    phone bookimpressive case, lots of numbers, but not

    much plot [Bem95].

    Researchers must continuously ask themselves: How is the work presented in the article related to

    my study?

    allows them to tie the literature into their own study

    36

  • 8/11/2019 How to Read Technical Papers

    36/36

    37

    References

    William G. Griswold, How to Read an Engineering

    Research Paper,

    cseweb.ucsd.edu/~wgg/CSE210/howtoread .html

    S. Keshav, How to Read a Paper, ACM SIGCOMM

    Computer Communication Review, Volume 37,Number 3, July 2007.

    Yair Levy and Timothy J. Ellis, A Systems Approach

    to Conduct an Effective Literature Review in Support of

    Information Systems Research, Informing Science

    Journal, Volume 9, 2006.