1

WWriting a riting a research research

paperpaper

2

연구개발의의미 연구개발의의미• 연구

– 硏 : 갈고닦는다는뜻 究 : 궁리한다는뜻– 어떤일에대하여깊이생각하고사리를따지어보는일

• Research– Search again– Scientific investigation

• 개발– 開 : 새로운길 , 방법을연다 發 : 꽃을피운다– 새로운것을고안해내어실용화함 ( 교학사국어사전 )

• Development– To bring, grow, or evolve to a more complete,

complex, or desirable state (American Heritage Dictionary)

3

연구개발이란무엇인가 연구개발이란무엇인가 ??• “When you steal ideas from many

people, it is called research. When you steal ideas from one person, it is called plagiarism.”

• Research = re-search– 즉다른사람이해놓은일을다시조사하는

데서또는새로운각도에서조명하는데서 연구개발이시작된다 => 硏究員은곧調査

員 !!

4

R&D R&D 분야의세계적추세 분야의세계적추세

• Outsourcing•Licensing•Strategic alliance ( 적과의동침 )•Grand alliance ( 세계적표준전략 )•Contract research•M&A

• Concurrent Engineering vs Sequential Engineering

•R&D 초기단계부터여러부서 ( 특히마키팅부서 ) 가공동참여

5

Matrix Management & Matrix Management & Dual LadderDual Ladder

• Matrix management– 기본조직과프로젝트조직의 2 원화

•기본조직 : 수직적구조 ( 계장 , 과장 , 부장 , 이사… )• 프로젝트조직 : 수평적구조 (project manager,

project leader, team leader….)• Dual ladder

– Scientist 나 engineer 가기본조직을통하지않고 연구에만전념하여도직급승진과보수를많이받을수있는

제도• Research and Engineering Fellow: 미국•연구위원 : 한국의대기업연구소에서채택한제도

6

R&D skill vs. People skillR&D skill vs. People skill• 연구원은연구를함으로과학 , 공학적인지식을

얼만큼갖고있느냐하는것만중요하다 .

• 과학공학적지식만큼 , people skill, leadership skill, speaking and writing skills 도아주중요하다 . 특히 writing, speaking skill 은 project 에아주중요한

역할을한다 .

7

How to write a How to write a research paper research paper

Simon Peyton JonesSimon Peyton Jones

Microsoft Research, CambridgeMicrosoft Research, Cambridge

8

• “The best way to understand something really big, is to reduce it to something meaningful.” Alex Beam, Boston Globe

9

Writing papersWriting papers

Idea Write paper Do research

• Crystallises what we don’t understand

• Opens the way to dialogue with others: reality check, critique, and collaboration

10

Do not be intimidatedDo not be intimidated

Write a paper, and give a talk, about

any idea, no matter how weedy and

insignificant it may seem to you

Fallacy You need to have a fantastic idea before you can write a paper. (Everyone else seems to.)

11

Papers communicate ideasPapers communicate ideas

Writing the paper is how you develop the idea in the first place

It usually turns out to be more interesting and challenging that it seemed at first

12

Your narrative flowYour narrative flow• Here is a problem• It’s an interesting problem• It’s an unsolved problem• Here is my idea• My idea works (details, data)• Here’s how my idea compares to

other people’s approaches

13

Structure Structure (conference paper)(conference paper)

• Title (1000 readers)• Abstract (4 sentences, 100 readers)• Introduction (1 page, 100 readers)• The problem (1 page, 10 readers)• My idea (2 pages, 10 readers)• The details (5 pages, 3 readers)• Related work (1-2 pages, 10 readers)• Conclusions and further work (0.5

pages)

14

The abstractThe abstract• I usually write the abstract last• Used by program committee

members to decide which papers to read

• Four sentences [Kent Beck]1. State the problem2. Say why it’s an interesting problem3. Say what your solution achieves4. Say what follows from your solution

15

StructureStructure• Abstract (4 sentences)• Introduction (1 page)• The problem (1 page)• My idea (2 pages)• The details (5 pages)• Related work (1-2 pages)• Conclusions and further work (0.5

pages)

16

The introduction The introduction (1 page)(1 page)

1. Describe the problem2. State your contributions...and that is all

17

Describe the problemDescribe the problem

Use an example

to introduce

the problem

18

State your State your contributionscontributions

• Write the list of contributions first• The list of contributions drives the

entire paper: the paper substantiates the claims you have made

• Reader thinks “gosh, if they can really deliver this, that’s be exciting; I’d better read on”

19

State your contributionsState your contributions

Bulleted list of

contributions

Do not leave the reader to guess what

your contributions are!

20

Contributions should be Contributions should be refutablerefutable

NO! YES!We describe the WizWoz system. It is really cool.

We give the syntax and semantics of a language that supports concurrent processes (Section 3). Its innovative features are...

We study its properties We prove that the type system is sound, and that type checking is decidable (Section 4)

We have used WizWoz in practice

We have built a GUI toolkit in WizWoz, and used it to implement a text editor (Section 5). The result is half the length of the Java version.

21

StructureStructure• Abstract (4 sentences)• Introduction (1 page)

•Related work• The problem (1 page)• My idea (2 pages)• The details (5 pages)• Related work (1-2 pages)• Conclusions and further work (0.5

pages)

22

No related work yet!No related work yet!We adopt the notion of transaction from Brown [1], as modified for distributed systems by White [2], using the four-phase interpolation algorithm of Green [3]. Our work differs from White in our advanced revocation protocol, which deals with the case of priority inversion as described by Yellow [4].

The reader knows nothing about the problem yet; so your (carefully trimmed) description of various technical tradeoffs is absolutely incomprehensible

23

StructureStructure• Abstract (4 sentences)• Introduction (1 page)• The problem (1 page)• My idea (2 pages)• The details (5 pages)• Related work (1-2 pages)• Conclusions and further work (0.5

pages)

24

Presenting the ideaPresenting the idea3. The idea

Consider a bifircuated semi-lattice D, over a hyper-modulated signature S. Suppose pi

is an element of D. Then we know for every such pi there is an epi-modulus j, such that pj < pi. Sounds impressive...but

Sends readers to sleep

In a paper you MUST provide the details, but FIRST convey the idea

25

Presenting the ideaPresenting the idea• Explain it as if you were speaking to

someone using a whiteboard• Conveying the intuition is

primary, not secondary• Once your reader has the intuition,

she can follow the details (but not vice versa)

• Even if she skips the details, she still takes away something valuable

26

Using examplesUsing examples

Introduce the problem, and your idea, using

EXAMPLESand only then present the

general case

27

Using examplesUsing examples

Example right away

28

The details: evidenceThe details: evidence• Your introduction makes claims

• The body of the paper provides evidence to support each claim

• Check each claim in the introduction, identify the evidence

• Evidence can be: analysis and comparison, theorems, measurements, case studies

29

StructureStructure• Abstract (4 sentences)• Introduction (1 page)• The problem (1 page)• My idea (2 pages)• The details (5 pages)• Related work (1-2 pages)• Conclusions and further work (0.5

pages)

30

Related workRelated workGiving credit to others does not diminish

the credit you get from your paper

Warmly acknowledge people who have helped you

Be generous to the competition. “In his inspiring paper [Foo98] Foogle shows.... We develop his foundation in the following ways...”

Acknowledge weaknesses in your approach

31

StructureStructure• Abstract (4 sentences)• Introduction (1 page)• The problem (1 page)• My idea (2 pages)• The details (5 pages)• Related work (1-2 pages)• Conclusions and further work (0.5

pages)

32

Conclusions and further Conclusions and further workwork

• Be brief.

33

The processThe process• Start early. Very early.

– Hastily-written papers get rejected.

– Papers are like wine: they need time to mature

• Collaborate

34

Getting helpGetting help

• Experts are good• Non-experts are also very good• Each reader can only read your paper for

the first time once! So use them carefully• Explain carefully what you want (“I got lost

here” is much more important than “Jarva is mis-spelt”.)

35

Getting expert helpGetting expert help• A good plan: when you think you are

done, send the draft to the competition saying “could you help me ensure that I describe your work fairly?”.

• Often they will respond with helpful critique (they are interested in the area)

• They are likely to be your referees anyway, so getting their comments or criticism up front is Jolly Good.

36

Listening to your reviewersListening to your reviewersTreat every review like gold

dustBe (truly) grateful for criticism

as well as praiseThis is really, really, really hard

But it’s really, really, really, really, really, really, really, really, really, really

important

37

Listening to your reviewersListening to your reviewers

• Read every criticism as a positive suggestion for something you could explain more clearly

• DO NOT respond “you stupid person, I meant X”. Fix the paper so that X is apparent even to the stupidest reader.

• Thank them warmly. They have given up their time for you.

38

Basic stuffBasic stuff• Submit by the deadline• Keep to the length restrictions

– Do not narrow the margins– Do not use 6pt font

– On occasion, supply supporting evidence (e.g. experimental data, or a written-out proof) in an appendix

• Always use a spell checker

39

Visual structureVisual structure• Give strong visual structure to

your paper using – sections and sub-sections– bullets– italics– laid-out code

• Find out how to draw pictures, and use them

40

Visual structureVisual structure

41

Use the active voiceUse the active voice

NO YESIt can be seen that... We can see that...

34 tests were run We ran 34 tests

These properties were thought desirable

We wanted to retain these properties

It might be thought that this would be a type error

You might think this would be a type error

The passive voice is “respectable” but it DEADENS your paper. Avoid it at all costs.

“We” = you and

the reader

“We” = the

authors

“You” = the

reader

42

Use simple, direct languageUse simple, direct language

NO YESThe object under study was

displaced horizontallyThe ball moved sideways

On an annual basis Yearly

Endeavour to ascertain Find out

It could be considered that the speed of storage reclamation left something to be desired

The garbage collector was really slow

43

Figures• Graphs

– not more than two curves on a diagram• up to four if well separated

– show points only if scatter is important• points should be visible

– abstractions with respect to text

44

Figures• Numerical tables are difficult to

read– – use a diagram, istogram, pie

chart, …– if you need to use a table, no more

than 6-8 rows and 3-4 colums

45

Dave Patterson's Writing Dave Patterson's Writing Advice Advice

46

Active voiceActive voice• For example, use "Figure X

shows ..." rather than "... as shown in Figure X." Also, it is much better to mention a Figure that summarizes a lot of information early in a paragraph rather than go into details and mention the figure at the end, as early mention gives the reader a framework to refer to while reading the text.

47

Ambiguous use of pronounAmbiguous use of pronoun

• Put a noun after "This" to make it clear what you are referring to.

48

"While" instead of "and", "but", "While" instead of "and", "but", "although"."although".

• In general while should be used only in the strict sense of "during the time

49

A single numbered subsectionA single numbered subsection

• Why do you need to number it if there is only one? Either eliminate the single subsection, or change the part that precedes the subsection into a second subsection

50

Refering to Chapters, FiguresRefering to Chapters, Figures

•Capitalized when used to refer to a specifuc number. So its Chapter 1, Table 3.1, Figure 1.2.

51

Numbers spelled out vs. Numbers spelled out vs. numericalnumerical

. The general rule of thumb is to spell out one to ten and use numbers for numbers for 11 and up.

For example, " The eight-processor case (model 370) needs only four computers to hold 32 processors.

(8*4=32) instead of words (eight*four=32).

52

ReferencesReferences

• Frederick Crews and Sandra Schor, "The Borzoi Handbook for Writers (2nd edition)", Alfred A. Knopf Inc., 1989.  

• Linda Flower, "Problem Solving Strategies for Writing (3rd edition)", Harcourt Brace Jovanovich, 1989.

• “Advice on Research and Writing”

http://www-2.cs.cmu.edu/afs/cs.cmu.edu/user/mleone/web/how-to.html