Study the following information and check your answers.

An abstract is a brief summary of a research article, thesis, review, conference proceeding or any in-depth analysis of a particular subject or discipline, and is often used to help the reader quickly ascertain the paper's purpose. When used, an abstract always appears at the beginning of a manuscript or typescript, acting as the point-of-entry for any given academic paper or patent application. Abstracting and indexing services for various academic disciplines are aimed at compiling a body of literature for that particular subject.

An academic abstract typically outlines four elements relevant to the completed work:

· The research focus (i.e. statement of the problem(s)/research issue(s) addressed);

· The research methods used (experimental research, case studies, questionnaires, etc.);

· The results/findings of the research;

· The main conclusions and recommendations

It may also contain brief references, although some publications' standard style omits references from the abstract, reserving them for the article body (which, by definition, treats the same topics but in more depth).

Abstract length varies by discipline and publisher requirements. Typical length ranges from 100 to 500 words, but very rarely more than a page and occasionally just a few words. An abstract may or may not have the section title of "abstract" explicitly listed as an antecedent to content. Abstracts are typically sectioned logically as an overview of what appears in the paper, with any of the following subheadings: Background, Introduction, Objectives, Methods, Results, Conclusions

Abstracts in which these subheadings are explicitly given are often called structured abstracts by publishers. In articles that follow the IMRAD pattern (especially original research, but sometimes other article types), structured abstract style is the norm. (The "A" of abstract may be added to "IMRAD" yielding "AIMRAD".) Abstracts that comprise one paragraph (no explicit subheadings) are often called unstructured abstracts by publishers. They are often appropriate for review articles that don't follow the IMRAD pattern within their bodies

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. ['ʤɑgən] 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 [veɪg], 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).