Abstract essay for final project, Undergraduate Research Center

>>> CLICK HERE <<<

The most straightforward method for writing an abstract is to mimic the arrangement of the more extensive work; consider it a small version of the dissertation or research paper. In most cases, the abstract must include four key elements: aim, methodology results, and conclusions, as earlier stated. Abstract essay for final project

Writing an Abstract

An abstract is a 150- to 250-word paragraph that provides readers with a quick overview of your essay or report and its organization. It should express your thesis (or central idea) and your key points; it should also suggest any implications or applications of the research you discuss in the paper.

According to Carole Slade, an abstract is «a concise summary of the entire paper.»

The function of an abstract is to describe, not to evaluate or defend, the paper.

The abstract should begin with a brief but precise statement of the problem or issue, followed by a description of the research method and design, the major findings, and the conclusions reached.

The abstract should contain the most important key words referring to method and content: these facilitate access to the abstract by computer search and enable a reader to decide whether to read the entire dissertation.

Note: Your abstract should read like an overview of your paper, not a proposal for what you intended to study or accomplish. Avoid beginning your sentences with phrases like, «This essay will examine. » or «In this research paper I will attempt to prove. «

Bad abstract:

This paper will look at the human genome project and its goals. I will prove that scientists have ethical and moral questions about genetic engineering because of this project.

Good abstract:

Begun in 1988, the human genome project intends to map the 23 chromosomes that provide the blueprint for the human species. The project has both scientific and ethical goals. The scientific goals underscore the advantages of the genome project, including identifying and curing diseases and enabling people to select the traits of their offspring, among other opportunities. Ethically, however, the project raises serious questions about the morality of genetic engineering. To handle both the medical opportunities and ethical dilemmas posed by the genome project, scientists need to develop a clear set of principles for genetic engineering and to continue educating the public about the genome project.

(The examples above are taken from Form and Style (10th ed.), by Carole Slade; The Scott, Foresman Handbook for Writers (5th ed.); and the Publication Manual of the American Psychological Association (5th ed.).)

Note: The following are specifications for an abstract in APA style, used in the social sciences, such as psychology or anthropology. If you are in another discipline, check with your professor about the format for the abstract.

Writing an Abstract for an IMRaD Paper

Many papers in the social sciences, natural sciences, and engineering sciences follow IMRaD structure: their main sections are entitled Introduction, Methods, Results, and Discussion. People use the abstract to decide whether to read the rest of the paper, so the abstract for such a paper is important.

Because the abstract provides the highlights of the paper, you should draft your abstract after you have written a full draft of the paper. Doing so, you can summarize what you’ve already written in the paper as you compose the abstract.

Typically, an abstract for an IMRaD paper or presentation is one or two paragraphs long (120 – 500 words). Abstracts usually spend

25% of their space on the purpose and importance of the research (Introduction)

How to Write an Abstract for the Undergraduate Research, Scholarship and Creative Activities Conference

The following instructions are for the Undergraduate Research Center’s Undergraduate Research, Scholarship and Creative Activities Conference, however the general concepts will apply to abstracts for similar conferences. In the video to the right, Kendon Kurzer, PhD presents guidance from the University Writing Program. To see abstracts from previous URC Conferences, visit our Abstract Books Page.

What is an abstract?

An abstract is a one-paragraph summary of a research project. Abstracts precede papers in research journals and appear in programs of scholarly conferences. In journals, the abstract allows readers to quickly grasp the purpose and major ideas of a paper and lets other researchers know whether reading the entire paper will be worthwhile. In conferences, the abstract is the advertisement that the paper/presentation deserves the audience’s attention.

Why write an abstract?

The abstract allows readers to make decisions about your project. Your sponsoring professor can use the abstract to decide if your research is proceeding smoothly. The conference organizer uses it to decide if your project fits the conference criteria. The conference audience (faculty, administrators, peers, and presenters’ families) uses your abstract to decide whether or not to attend your presentation. Your abstract needs to take all these readers into consideration.

How does an abstract appeal to such a broad audience?

The audience for this abstract covers the broadest possible scope–from expert to lay person. You need to find a comfortable balance between writing an abstract that both shows your knowledge and yet is still comprehensible–with some effort–by lay members of the audience. Limit the amount of technical language you use and explain it where possible. Always use the full term before you refer to it by acronym [DNA double-stranded breaks (DSBs), for example]. Remember that you are yourself an expert in the field that you are writing about–don’t take for granted that the reader will share your insider knowledge.

What should the abstract include?

Think of your abstract as a condensed version of your whole project. By reading it, the reader should understand the nature of your research question.

Like abstracts that researchers prepare for scholarly conferences, the abstract you submit for the Undergraduate Research Conference will most likely reflect work still in progress at the time you write it. Although the content will vary according to field and specific project, all abstracts, whether in the sciences or the humanities, convey the following information:

• The purpose of the project identifying the area of study to which it belongs.
• The research problem that motivates the project.
• The methods used to address this research problem, documents or evidence analyzed.
• The conclusions reached or, if the research is in progress, what the preliminary results of the investigation suggest, or what the research methods demonstrate.
• The significance of the research project. Why are the results useful? What is new to our understanding as the result of your inquiry?

Whatever kind of research you are doing, your abstract should provide the reader with answers to the following questions: What are you asking? Why is it important? How will you study it? What will you use to demonstrate your conclusions? What are those conclusions? What do they mean?

Stylistic considerations

The abstract should be one paragraph and should not exceed the word limit. Edit it closely to be sure it meets the Four C’s of abstract writing:

• Complete — it covers the major parts of the project.
• Concise — it contains no excess wordiness or unnecessary information.
• Clear — it is readable, well organized, and not too jargon-laden.
• Cohesive — it flows smoothly between the parts.

The importance of understandable language

Because all researchers hope their work will be useful to others, and because good scholarship is increasingly used across disciplines, it is crucial to make the language of your abstracts accessible to a non-specialist. Simplify your language. Friends in another major will spot instantly what needs to be more understandable. Some problem areas to look for:

• Eliminate jargon. Showing off your technical vocabulary will not demonstrate that your research is valuable. If using a technical term is unavoidable, add a non-technical synonym to help a non-specialist infer the term’s meaning.
• Omit needless words—redundant modifiers, pompous diction, excessive detail.
• Avoid stringing nouns together (make the relationship clear with prepositions).
• Eliminate «narration,» expressions such as «It is my opinion that,» «I have concluded,» «the main point supporting my view concerns,» or «certainly there is little doubt as to. . . .» Focus attention solely on what the reader needs to know.

Before submitting your abstract

• Make sure it is within the word limit. (Over-writing is all too easy, so reserve time for cutting your abstract down to the essential information.).
• Make sure the language is understandable by a non-specialist. (Avoid writing for an audience that includes only you and your professor.)
• Have your sponsoring professor work with you and approve the abstract before you submit it online.
• Only one abstract per person is allowed for the URC’s Undergraduate Research, Scholarship and Creative Activities Conference.

Examples

Multimedia Risk Assessment of Biodiesel – Tier II Antfarm Project

Significant knowledge gaps exist in the fate, transport, biodegradation, and toxicity properties of biodiesel when it is leaked into the environment. In order to fill these gaps, a combination of experiments has been developed in a Multimedia Risk Assessment of Biodiesel for the State of California. Currently, in the Tier II experimental phase of this assessment, I am investigating underground plume mobility of 20% and 100% additized and unadditized Soy and Animal Fat based biodiesel blends and comparing them to Ultra Low-Sulfer Diesel #2 (USLD) by filming these fuels as they seep through unsaturated sand, encounter a simulated underground water table, and form a floating lens on top of the water. Thus far, initial findings in analyzing the digital images created during the filming process have indicated that all fuels tested have similar travel times. SoyB20 behaves most like USLD in that they both have a similar lateral dispersion lens on top of the water table. In contrast, Animal Fat B100 appears to be most different from ULSD in that it has a narrower residual plume in the unsaturated sand, essay online buy as well as a narrower and buy essay online deeper lens formation on top of the water table.

Narrative Representation of Grief

In William Faulkner’s As I Lay Dying and Kazuo Ishiguro’s Never Let Me Go how can grief, an incomprehensible and incommunicable emotion, be represented in fiction? Is it paradoxical, or futile, to do so? I look at two novels that struggle with representing intense combinations of individual and communal grief: William Faulkner’s As I Lay Dying and Kazuo Ishiguro’s Never Let Me Go. At first glance, the novels appear to have nothing in common: Faulkner’s is a notoriously bleak odyssey told in emotionally heavy stream-of-consciousness narrative, while Ishiguro’s is a near-kitschy blend of a coming-of-age tale and a sci-fi dystopia. But they share a rare common thread. They do not try to convey a story, a character, an argument, or a realization, so much as they try to convey an emotion. The novels’ common struggle is visible through their formal elements, down to the most basic technical aspects of how the stories are told. Each text, in its own way, enacts the trauma felt by its characters because of their grief, and also the frustration felt by its narrator (or narrators) because of the complex and guilty task of witnessing for grief and loss.

This webpage was based on articles written by Professor Diana Strazdes, Art History and Dr. Amy Clarke, University Writing Program, UC Davis. Thanks to both for their contributions.

How to Write an 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.

Further Reading

Michaelson, Herbert, How to Write & Publish Engineering Papers and Reports , Oryx Press, 1990. Chapter 6 discusses abstracts.

Cremmins, Edward, The Art of Abstracting 2nd Edition , Info Resources Press, April 1996. This is an entire book about abstracting, written primarily for professional abstractors.

© Copyright 1997, Philip Koopman, Carnegie Mellon University.Embedded system designers may be interested in my blog.

Abstract essay for final project, Abstract essay for final project