Writing Title, Abstract, and Methodology Prof Shou-de Lin sdlin@csie.ntu.edu.tw Technical Writing NTU CSIE/GINM 12/31/2018 TW-abstract, 07, Shou-de Lin

TW-abstract, 07, Shou-de Lin How to prepare a title A good title can help the paper to reach its intended audience . A good title will distinguish your work from all others which have to do with the same general area of study. A title is the label (keywords) of a paper. A good title uses the fewest possible words that adequately (specifically) describe the contents of the paper. A title should almost never contain abbreviations. 12/31/2018 TW-abstract, 07, Shou-de Lin

The purpose of an abstract Descriptive abstract Describe what the article is about (its purpose, scope, methods, and the results). Usually proceed a technical paper. Informative abstract An expanded version of the descriptive abstract. Usually being submitted independently for review. Usually retains the tone and the essential scope of the report while omitting the details. 12/31/2018 TW-abstract, 07, Shou-de Lin

TW-abstract, 07, Shou-de Lin Abstracts usually come after the title. It contains 100-300 words. Usually the longer the paper, the longer the subject. The abstract may affect how many (and what kind of) people will read your paper. Two types of abstract: Results-driven Summary (purpose of this project, main solutions, and principal results) 12/31/2018 TW-abstract, 07, Shou-de Lin

Rules for an abstract (Bor-ming JAHN, 2006) It should be a mini-version of the original paper. It should provide balanced coverage of the original. It should present the source material in a neutral unbiased fashion. It should include nothing that is not in the original (no personal comments). 12/31/2018 TW-abstract, 07, Shou-de Lin

Rules for an abstract (Bor-ming JAHN, 2006) Do not try to paraphrase specialized vocabulary or technical terms. Include enough support and detail to make it clear. Make it flow smoothly. Use full sentences. Avoid negatives, abbreviations, and jargon. 12/31/2018 TW-abstract, 07, Shou-de Lin

Methodology Should Contain formal (e.g. mathematical) problem definition, hypothesis, assumption. main concept/idea outline and motivation (it’s good to describe an example or intuition behind). proof or algorithm. 12/31/2018 TW-abstract, 07, Shou-de Lin

TW-abstract, 07, Shou-de Lin Flow flow1: problem def  review of previous solution and their drawbacks  new solution  how much the new solution gains flow2: problem def  using example first  formalize the example into algorithm flow3: problem def  describe the solution for a simpler case  extend it to a more complex case, thus avoiding explaining basic concepts in a complex framework 12/31/2018 TW-abstract, 07, Shou-de Lin

TW-abstract, 07, Shou-de Lin Tips Write your abstract AFTER you finish writing the whole paper Your methodology should be reasonable independent of other articles (i.e. people don’t have to read other articles to understand it) 12/31/2018 TW-abstract, 07, Shou-de Lin