w10 Writing abstract - handout

w10 Writing abstract - handout - Writing abstract Contents:...

Info iconThis preview shows pages 1–8. Sign up to view the full content.

View Full Document Right Arrow Icon
Writing abstract
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Contents: Structure of a technical papers Writing abstract
Background image of page 2
Structure of Technical papers http://myweb.ncku.edu.tw/~msju/mml/techwrt.htm http://www.cs.ccu.edu.tw/~ccc/article/TecWrite.htm http://www.cs.columbia.edu/~hgs/etc/writing-style.html
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
A technical paper should be clear and concise. The goal is to convey ideas and results to the readers in the least possible time and space. Everything about the document should contribute to this goal. The notations and format should be consistent throughout the paper. It is a very common error to dive into the technical approach or the implementation details without having appropriately framed the problem. You should first say what the problem or goal is, and — even when presenting an algorithm — first state what the output is and probably the key idea, before discussing steps.
Background image of page 4
A paper usually consists of the following components: 1) Title —It should be concise and to the point. For example, some publications limit the title to less than ten words. Avoid all but the most readily understood abbreviations. Avoid common phrases like "novel", "performance evaluation" and "architecture", since almost every paper does a performance evaluation of some architecture and it better be novel. Unless somebody wants to see 10,000 Google results, nobody searches for these types of words. Use adjectives that describe the distinctive features of your work, e.g., reliable, scalable, high-performance, robust, low- complexity, or low-cost. If you need inspiration for a paper title, you can consult the Automatic Systems Research Topic or Paper Title Generator . Structure of a technical paper
Background image of page 5

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
2) Abstract —A summary of the paper, including a brief description of the problem, the solution, and conclusions. Do not cite references in the abstract. 3) Keywords —They should be selected such that a computerized search will be facilitated. 4) Introduction —This should contain the background of the problem, why it is important, and what others have done to solve this problem. All related existing work should be properly described and referenced. The proposed solution should be briefly described, with explanations of how it is different from, and superior to, existing solutions. The last paragraph should be a summary of what will be described in each subsequent section of the paper.
Background image of page 6
5) System Model —The proposed model is described. There will invariably be assumptions made. State the model assumptions clearly. Do the assumptions make sense? Use figures to help explain the model. 6) Numerical results —Based on the model, numerical results will be generated. These results should be presented in such a way as to facilitate the readers’ understanding. Usually, they will be presented in the form of figures or tables. The parameter values chosen should make sense. All the
Background image of page 7

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Image of page 8
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 19

w10 Writing abstract - handout - Writing abstract Contents:...

This preview shows document pages 1 - 8. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online