[fly]How to write abstract[/fly]
All the important results achieved by google are as follows:
1.How to Write an Abstract. http://www.klariti.com/technical ... rite-Abstract.shtml
Abstracts are more important than ever. We have an ever-increasing need for quick access to information. Think of those search engine results that you find on Internet sites. If the first few lines were an abstract, you'd know whether you should go and read it. Instead, you often have to wade through link after link until you find what you were after.
So how do you write an abstract?
Once you've finished writing, stop and think about the document.
What is the main subject?
What is the main conclusion?
What is its primary purpose?
What would you expect the reader to do with this document?
Collect this together and write a sentence - this is your topic sentence.
You need to write one topic sentence that covers the entire document, regardless of whether the
document is a one-page letter or a thousand-page manual.
Getting Ideas
Look at the recommendations, conclusions, summaries, and results in the completed document.
When abstracting a manual, look at the tutorial. These sections cover the essence of the document.
Avoid the document title
This can be misleading. It may not help you write the topic sentence. Chances are the title will be too vague. Parts of the title might serve as modifiers in your topic sentence, but you'll probably need to go beyond the title.
Be specific
Make the topic sentence be specific. Avoid writing "This report describes… [document title]."
Instead, write something like "The results of this… [subject]… study show that… [result]."
Use supporting sentences to fill in details
After you identify your topic sentence, write supporting sentences. Make each of these supply specific details about the ideas in the topic sentence. Think of what supports the topic sentence.
Who? What? Where? When? Why? How? and How much?
Give statistics, results, conclusions, or recommendations that back up the topic sentence. Only use two or three major supporting ideas. Include the less important evidence as subordinate clauses and modifiers.
Transitions holds it together
Arrange the supporting sentences in a logical sequence after the topic sentence. Add whatever transition is needed to connect the supporting sentences to the topic sentence and to connect ideas within the sentences to each other. Rewrite the sentences to improve the connections.
The Tricks
Write the abstract only when the document is finished. Abstracts written before then are just previews.
If you are forced to write an abstract before the document is completed, think about its purpose and write a topic sentence. Keep in mind that you'll need to rewrite the abstract when the document is finished because it will no longer accurately reflect the contents of the document.
Before starting the abstract, list your thoughts on the document. Group related items together.
Prioritize the list and put the most important group first. The first few groups form the core of the topic sentence. The rest lead to supporting sentences.
If you can't create a topic sentence, write the supporting sentences first. The topic sentence may then become obvious.
Write for an audience not necessarily up to speed in your subject area. This is important because you never know who will read your abstract.
Choose acronyms, abbreviations, and technical terms carefully as they may confuse many readers.
Define the scope of the project in the abstract.
Reread your abstract after several days have passed.
Remove all superfluous information.
Your Result
Your abstract is now of use to the reader. This technique works for documents of any length from a couple of pages to multi-volumes. It also works for letters, reports, articles, scripts, and anything else you have to write.
2.Writing Your Abstract. http://www.albany.edu/cpr/gf/gfj/writing-your-abstract.htm
The abstract is a brief (150-250 word) overview -- an "executive summary" -- that states the nature, purpose, and benefits of your article or chapter. It helps the reader decide whether or not to continue reading.
Your abstract should:
- detail the subject of your article or chapter,
- identify its primary audience (and any secondary audiences),
- indicate the approach your article or chapter takes to its subject (especially how that approach
separates it from exsiting literature
- highlight the results, conclusions, and benefits it offers readers
- be written in narrative form
- not include an outline, bulletted lists, or lists of keywords
- not provide biographical information about the author
- not substitute for or repeat extensively information that should be in the introduction
For additional advice on writing abstracts, visit:
http://www.gmu.edu/departments/w ... douts/abstract.html
http://www.galaxygoo.org/resources/abstract_writing.html
http://www.klariti.com/technical ... rite-Abstract.shtml
3.Phil Koopman. How to Write an abstract. http://www.ece.cmu.edu/~koopman/essays/abstract.html
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: motivation, problem statement, approach, results, and conclusions. 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.
Checklist: 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:
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.
Problem statement:
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.
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?
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.
Conclusions:
What are the implications of your answer? Is it going to change the world (unlikely), be 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:
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 150 to 200 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. Be sure that those exact phrases appear in your abstract, so that they will turn up at the top of a search result listing.
Usually the context of a paper is set by the publication it appears in (for example, IEEE Computer magazine's articles are generally about computer technology). But, if your paper appears in a somewhat un-traditional venue, be sure to include in the problem statement the domain or topic area that it is really applicable to.
Some publications request "keywords". These have two purposes. They are used to facilitate keyword index searches, which are greatly reduced in importance now that on-line abstract text searching is commonly used. However, they are also used to assign papers to review committees or editors, which can be extremely important to your fate. So make sure that the keywords you pick make assigning your paper to a review category obvious (for example, if there is a list of conference topics, use your chosen topic area as one of the keyword tuples).
Conclusion
Writing an efficient abstract is hard work, but will repay you with increased impact on the world by enticing people to read your publications. Make sure that all the components of a good abstract are included in the next one you write.
4.HOW TO WRITE ABSTRACT. www.ntu.edu.sg/mae/Research/Programmes/
Thinfilms/Sam/Abstract-Conclusion.pdf
1. Shrink your INTRODUCTION section into one or two sentences (this may not necessary for some journals because of length constraint in abstract)
2. Shrink your EXPERIMENTAL PROCEDURE into a few sentences
3. Shrink your RESULTS into one or two sentences
4. Shrink your CONCLUSIONS into one or two sentences
5. Put these sentences together ---- congratulate yourself, you’ve written a good abstract!
Thanks for your patience to read! Hope the above content is helpful for you.
ynylb |
发表于 2006-6-11 21:34:44
