ABSTRACT SENTENCE!! NEED HElP!!!!!!!!!?
my topic for my science fair is how does music affect your studying habits? but my question is how do i start off the abstract part????
- lolslaveryLv 41 decade agoFavorite Answer
Here's a list (below) of 5 points you should cover in your abstract.
Based on this (and having seen several abstracts in research papers) I would suggest starting out with a little background, saying how our music listening habits have shifted to portable players and laptops, and thus we can take music to the library, our room, and other traditional study areas with relative ease. This, combined with our culture's affinity to do two or three things at once and have constant stimulation, presents some real interference with studying (that's the "Problem Statement"). After that just describe what sort of experiment you did to test this problem (Approach, Results, Conclusion).
As you may know, it's just a short summary of everything your project covered, and most importantly, why should we even care about it!
Here's a guideline, and good luck on your science fair.
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.
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?
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.
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?