Look for a new one each day. The next newsletter will have them all if you miss any!
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.
Introduction 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 summary" 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? If the problem isn't obviously "interesting" it might be better to put motivation first; but if your work is incremental progress on a problem that is widely recognized as important, then it is probably better to put the problem statement first to indicate which piece of the larger problem you are breaking off to work on.
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. There is a tension here in that you should not provide numbers that can be easily misinterpreted, but on the other hand you don't have room for all the caveats.
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 can't assume or attempt to provoke the reader into flipping through looking for an explanation of what is meant by some vague statement. It must make sense all by itself. Some points to consider include:Table 1. Table 1. Seven Myths about Obesity.
We review seven myths about obesity, along with the refuting evidence. Table 1 provides anecdotal support that the beliefs are widely held or stated.
A review article differs from a research article in that the review article examines the evidence presented in a Your life as a researcher, student, and writer will be . Qualities of good essay writers. Writing an essay is a creative process which requires concentration.
It is a test of the writer's ability to think things over, make conclusions, and express his or her own opinion. Bought a 5 page english paper. The writer followed the instructions on what to write for each paragraph.
But totally ignored the " don't summarize the story" instruction, and there were many faulty sentences. An abstract is brief summary of a research article that emphasizes what is new, captures the salient features of the purpose, design, findings, and implications, and contains no unnecessary sentences or explanations.
A good abstract includes. How to Write an Abstract. In this Article: Article Summary Getting Your Abstract Started Writing Your Abstract Formatting Your Abstract Community Q&A If you need to write an abstract for an academic or scientific paper, don't panic!
Your abstract is simply a short, stand-alone summary of the work or paper that others can use as an overview. An abstract describes what you do in your essay.