Академический Документы
Профессиональный Документы
Культура Документы
The major aspects of the entire paper in a prescribed sequence that includes:
The overall purpose of the study and the research problem(s) you investigated;
The basic design of the study;
Major findings or trends found as a result of your analysis; and,
A brief summary of your interpretations and conclusions.
An abstract lets readers get essence of your paper or article quickly, in order to decide
whether to read the full paper;
An abstract prepares readers to follow the detailed information, analyses, and
arguments in your full paper;
And, later, an abstract helps readers remember key points from your paper.
PARTS OF ABSTRACTS:
Abstracts are very brief, but 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.
2
The following can be used as a checklist for writing abstracts:
a) MOTIVATION:
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.
b) PROBLEM STATEMENT:
c) APPROACH:
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?
d) RESULTS:
What's the answer? 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." If you must be vague, you are only given license to do so when you can talk about
orders-of-magnitude improvement. 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.
e) CONCLUSIONS:
What are the implications of your answer? Is it going to change the world (unlikely), be a
3
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
generalizeable, or specific to a particular case?
TYPES OF ABSTRACTS:
There are four general types of abstracts. These include:
1. CRITICAL ABSTRACT:
2. DESCRIPTIVE ABSTRACT:
A descriptive abstract indicates the type of information found in the work. It makes no
judgments about the work, nor does it provide results or conclusions of the research. It does
incorporate key words found in the text and may include the purpose, methods, and scope
of the research. Essentially, the descriptive abstract only describes the work being
summarized. Some researchers consider it an outline of the work, rather than a summary.
Descriptive abstracts are usually very short, 100 words or less.
In many ways, the descriptive abstract is like a table of contents in paragraph form.
Unlike reading an informative abstract, reading a descriptive abstract cannot substitute for
reading the document because it does not capture the content of the piece. Nor does a
descriptive abstract fulfill the other main goals of abstracts as well as informative abstracts do.
For all these reasons, descriptive abstracts are less and less common.
3. INFORMATIVE ABSTRACT:
The majority of abstracts are informative. While they still do not critique or evaluate a
work, they do more than describe it. A good informative abstract acts as a surrogate for the
work itself. That is, the researcher presents and explains all the main arguments and the
important results and evidence in the paper. An informative abstract includes the information
that can be found in a descriptive abstract [purpose, methods, scope] but it also includes the
results and conclusions of the research and the recommendations of the author. The length
varies according to discipline, but an informative abstract is usually no more than 300 words in
length.
4
An informative abstract provides detail about the substance of a piece of writing because
readers will sometimes rely on the abstract alone for information. Informative abstracts typically
follow this format:
4. HIGHLIGHT ABSTRACT:
A highlight abstract is specifically written to attract the reader’s attention to the study. No
pretense is made of there being either a balanced or complete picture of the paper and, in fact,
incomplete and leading remarks may be used to spark the reader’s interest. In that a highlight
abstract cannot stand independent of its associated article, it is not a true abstract and,
therefore, rarely used in academic writing.
5
EXAMPLE OF ABSTRACT:
This example calls this paragraph at the beginning of the article a “Summary,” rather than an
“Abstract.” This is a great example of an effective graphical abstract, a bulleted list of highlights
list at the beginning of the article, and a two-sentence “In Brief” summary.
CONCLUSION:
Abstract writing efficiently is hard work, but it will be highly beneficial in tempting and
attracting people to read the paper, article or publication. Having a good abstract can be an eye
catching opening that will tempt the readers to know in detail about the writing. One should
make sure that all the components of a good abstract are included in the abstract so that it can
appeal to the people.