Checklist
(RTF File)
Overview
An abstract provide a brief summary of a longer document, most often
a published research article. They are a single paragraph, typically
200-500 words (10% or less of the original document). Readers use abstracts
most often to determine whether to read the entire article.
Content
Abstracts typically include purpose, methods, scope, conclusions, and
recommendations (the exact information depends on the specific field,
and sometimes the journal that publishes the article).
"Descriptive Abstracts," which serve only to introduce
the document, often do not include conclusions and recommendations.
Usually only 100 words or so, they typically act as a kind of "table
of contents" for the document, explaining what it covers, but
providing few, if any, details.
"Informative Abstracts" are usually longer and cover key
details such as the major findings or conclusions of the document.
Writing Tips
(Review the samples above right for more specific examples of these
strategies at work).
- As you read the article, note the key components (purpose,
method, scope, conclusions, recommendations).
- Use the article's headings and subheadings to help you define
and organize what information the document includes.
- After reading the document and making notes, write a rough draft
from memory, then check it against the document for completeness
and accuracy.
- Don't rely on the language of the article itself; summarize the
information in your own words.
- Begin with the document's main purpose or focus to orient
the reader.
- For Example:
This article summarizes the current state of computer technology
for music education and provides guidelines for implementing
it in schools.
This article provides an overview of the ethical debates surrounding
the Human Genome Project.
- Specify what kind of information the document includes, but
for brevity, avoid specific details.
- For Example:
The article provides a brief background on computer technology
in education, describes the Musical Instrument Digital Interface
(MIDI), and covers budgeting, hardware and software needs, and
facility design. It also offers additional resources for those
who want more information.
- Do not include background; references to any charts, tables,
or figures in the document; or any information not found in the document
itself.
- When writing an abtract for publication, include a list of keywords
to use for indexing purposes.
(Sources: Jones, Dan. The Technical Communicator's Handbook.
Boston: Allyn and Bacon, 2000; Markel, Mike. Technical Communication
6th Edition. New York: Bedfort/St. Martins, 2001)
Annotated Bibliographies-->