Abstracts An abstract is a summary of a body of information.
Philip KoopmanCarnegie Mellon University October, Abstract Because on-line search databases typically contain only abstracts, it is vital to write a complete but concise description of your work to entice potential readers into obtaining a copy of the full paper. This article describes how to write a good computer architecture abstract for both conference and journal papers.
Writers should follow a checklist consisting of: Following this checklist should increase the chance of people taking the time to obtain and read your complete paper. Abstract technical writing Now that the use of on-line publication databases is prevalent, writing a really good abstract has become even more important than it was a decade ago.
Abstracts have always served the function of "selling" your work.
But now, instead of merely convincing the reader to keep reading the rest of the attached paper, an abstract must convince the reader to leave the comfort of an office and go hunt down a copy of the article from a library or worse, obtain one after a long wait through inter-library loan.
In a business context, an "executive Abstract technical writing is often the only piece of a report read by the people who matter; and it should be similar in content if not tone to a journal paper abstract.
Parts of an Abstract Despite the fact that an abstract is quite brief, it must do almost as much work as the multi-page paper that follows it. In a computer architecture paper, this means that it should in most cases include the following sections. Each section is typically a single sentence, although there is room for creativity.
In particular, the parts may be merged or spread among a set of sentences. Use the following as a checklist for your next abstract: Why do we care about the problem and the results? This section should include the importance of your work, the difficulty of the area, and the impact it might have if successful.
What problem are you trying to solve? What is the scope of your work a generalized approach, or for a specific situation? Be careful not to use too much jargon. In some cases it is appropriate to put the problem statement before the motivation, but usually this only works if most readers already understand why the problem is important.
How did you go about solving or making progress on the problem? Did you use simulation, analytic models, prototype construction, or analysis of field data for an actual product?
What was the extent of your work did you look at one application program or a hundred programs in twenty different programming languages? What important variables did you control, ignore, or measure?
Specifically, most good computer architecture papers conclude that something is so many percent faster, cheaper, smaller, or otherwise better than something else.
Put the result there, in numbers. Avoid vague, hand-waving results such as "very", "small", or "significant. What are the implications of your answer? Is it going to change the world unlikelybe a significant "win", be a nice hack, or simply serve as a road sign indicating that this path is a waste of time all of the previous results are useful.
Are your results general, potentially generalizable, or specific to a particular case?
Other Considerations An abstract must be a fully self-contained, capsule description of the paper. It must make sense all by itself. Some points to consider include: Meet the word count limitation.
If your abstract runs too long, either it will be rejected or someone will take a chainsaw to it to get it down to size. Your purposes will be better served by doing the difficult task of cutting yourself, rather than leaving it to someone else who might be more interested in meeting size restrictions than in representing your efforts in the best possible manner.
An abstract word limit of to words is common. Any major restrictions or limitations on the results should be stated, if only by using "weasel-words" such as "might", "could", "may", and "seem". Think of a half-dozen search phrases and keywords that people looking for your work might use.The audience for an executive summary is precisely what the name indicates – executives and managers; the audience for the abstract is usually a more technical reader.
A design report may include an executive summary aimed at your boss, who may need to decide whether or not to use your design, and also an abstract for your peers or other. 1 Writing Technical Abstracts Kent State University Dr. Jonathan I Maletic Contents of a Technical Paper • Title, Author(s) • Abstract – ( words) • Introduction • .
Abstracts of scientific papers are sometimes poorly written, often lack important information, and occasionally convey a biased picture. This paper provides detailed suggestions, with examples, for writing the background, methods, results, and conclusions sections of a good abstract.
In writing a research paper, writing the abstract is an absolute must. In most research papers, the abstract is the section which includes the summary of the whole research paper. It usually gives a general overview of the major aspects of the entire research process, including the .
How to Write a Technical Paper: Arizona State University Tempe, Arizona, USA [email protected].com Abstract A major problem that young researchers face is their inability to write good research papers. This writing guides, writing technical papers, format guides 1 Introduction The introduction serves a twofold .
The abstract is the most widely read part of your manuscript and it is recommended to write it last. However, this can mean rushing this crucial piece. Edanz can help you prepare an abstract that will clearly show the importance and novelty of your research.