(If you're not in class today, do these steps at home, so you're not getting left behind!)
Wednesday, 29th: 2 mini lessons
HOMEWORK for Wed., 29th, class time: email me your Word document containing title, abstract (unfinished), keywords, Lit Review
________________________________________________________
Today, we will need our Word document with the 12 headings.
Our Research Papers are growing substantially. We've finished the Annotated Bibliography, which you can copy and paste into your Word doc as soon as you got them back from me with my remarks. Note: The 10 max. points you get for your Annotated Bibliography have nothing to do with the grade you'll get for your final Research Paper. They simply mean you've done your homework. I've marked format, academic voice, and spelling errors, and whether the homework was submitted on time; I didn't check the content. We will have a peer-editing session in the end, where your peers will evaluate the content of your paper components.
We will also do a readability exercise with our finished research essays to establish our personal readability levels - at what grade level we write. For an academic paper, it should be 16+. If your readability level is lower, you need to change your sentence structure by incorporating more commas and semicolons, and elevated vocabulary. If your Annotated Bibliography in the section of "personal statement" contains a sentence such as "This article was very helpful to me because it helped me to...," this is obviously corresponding to grade level 4 or so, and needs to be reworded to "according to the results, it can be suggested that prospective teachers employ the delineated strategies to improve...."
Now, we are continuing with our Lit Reviews which are due this Wednesday, Oct. 29th, at class time.
But we will also deal with some other headings: the title, the abstract, the keywords. The more you read in your secondary sources, the more keywords will pop up, so type them directly in the space under the abstract reserved for them. It is obvious that we can merely BEGIN with these steps, and will finish them within the next four weeks, since we do not have any results yet, and do not even know the actual number of our "participants." (NOTE: We will only count as "participants of the study" the people who actually answered the survey, NOT all the people we have asked to take the survey!!!)
Today, we will
1) invent a catchy title that foreshadows your topic (keep academic voice, but still make it attention-catching). Also add your name and institution, and the two black lines above and below the abstract. NOTE: You can have a one-sentence title (like "How much Grammar do College Freshmen Know?"), or a double-sentence title with a colon or a dash in between (like "Shakespeare Turning in His Grave - The Decline of Language in High School Students"). Don't make your title too long.
2) Begin the abstract. The word limit is 175 words - no more!!! Keep the readability very high, because your abstract will decide whether or not other researchers are going to read your whole paper.
3) list some keywords (all nouns!)
4) finish up your Lit Review that we began in last Friday's workshop. The easiest way is to print out the 3 external sources (research papers), underline the important findings, and highlight the quotes you want to use with differently-colored markers. NOTE: When you submit your final Research Papers, you will submit them in a folder that also contains your 3 sources. You can give me your high-lighted, annotated sources - in fact, I'd prefer to see that you've worked with your sources, rather than receiving clean paper that looks unread.
You can also open the online source and use two windows on your screen next to one other, so you can type the quotes from the source directly into your Word document. What doesn't work is to copy and paste the quotes, since this is not possible with pdf files (unless you have special software).
NOTE: Be careful when copying your quotes! If the original quote you are using contains a SPELLING MISTAKE, you have to misspell it, too - indicate that it was the mistake of the original author by putting square brackets with the Latin word "sic" (= "so" / "thus it was said") behind the misspelled word or punctuation sign. Example:
"This tree is gorgous [sic]" (Miller 2006, 87).
Below are the guidelines for how to write an effective ABSTRACT (taken from this source). I have made some annotations in maroon.
An abstract contains the following:
- 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. (This is your attention-catcher; here, you introduce your topic by mentioning why it is so important in our times. You can also mention the shortcomings of existing literature (your external sources), and the importance of your own study.)
- 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. (This is where your research question goes - what did you want to find out?)
- 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? (This is where you briefly describe your participants and methods. Leave out the number and demographics of your participants, since we don't know yet who will actually take your surveys.)
- 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. (This is the part you leave blank for now; we'll fill it in when we have analyzed our SurveyMonkey results.)
- 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? (This is what you are going to write in the end, when the paper is completed. Contains your implications and limitations.)
If there are any questions, ask during the workshop in class, or take a look at last semester's sample essays again.
No comments:
Post a Comment