APA style
Moderator: HatePirate
APA style
So instead of reading this huge ass book on APA documentation style, I was wondering if anyone had a paper, in APA style, that got a good grade from a picky teacher, that I could look at. I reeeeally don't want to read all this crap, and my eyes hurt from staring at this computer all day finding the actual research that I need.
I know, excuses excuses, but if ya don't mind I would really appreciate it. No rush.
SamBearNotes@yahoo.com
I know, excuses excuses, but if ya don't mind I would really appreciate it. No rush.
SamBearNotes@yahoo.com
WORKS CITED
American Psychological Association. (2001). Publication Manual of the American Psychological Association. Washington, D.C.: American Psychological Association.
Bureau of Labor Statistics, U.S. Department of Labor. (2002-2003). Occupational Outlook Handbook. McGraw-Hill.
Donnelly, Sally B. (2000, October 30). Air-Traffic-Glitch Control? Time, 26.
Jones, Capers. (1996). Patterns of Software Systems Failures and Success. Boston: International Thomson Computer Press.
Mann, Charles C. (2002, July). Why Software is So Bad. Technology Review, 32-39.
McDermott, Terry. (1995, June 4). A Question of Safety: Is the FAA Up to the Job? The Seattle Times, pp. A1+.
Norman, Donald A. (2002, July). Beyond the Computer Industry. Communications of the ACM, 120.
Peterson, I. (1991, December 14). Software Failure: Counting Up the Risks. Science News, 388-390.
Peterson, Ivars. (1995). Fatal Defect: Chasing Killer Computer Bugs. New York: Random House.
Sewell, Marc T, & Sewell, Laura M. (2002). The Software Architect’s Profession. Upper Saddle River: Prentice Hall.
Thibodeau, Patrick, & Rosencrance, Linda. (2002, July). Users Losing Billions Due to Bugs. Computerworld, 1-3.
Thompson, Nathanael. Interview. October 29, 2002.
--- and in the paper itself--------
"...in order to assuage those fears” (Thompson Interview, 2002).
“the risks of the traditional computer business must be revisited by each new industry, usually through failures” (Norman, 2002, p.120).
“Pilots will no longer fly the aircraft via direct electrical and mechanical controls” (Peterson, 1991, p 388).
----end help----
I got an A on the paper. And you are lazy.
American Psychological Association. (2001). Publication Manual of the American Psychological Association. Washington, D.C.: American Psychological Association.
Bureau of Labor Statistics, U.S. Department of Labor. (2002-2003). Occupational Outlook Handbook. McGraw-Hill.
Donnelly, Sally B. (2000, October 30). Air-Traffic-Glitch Control? Time, 26.
Jones, Capers. (1996). Patterns of Software Systems Failures and Success. Boston: International Thomson Computer Press.
Mann, Charles C. (2002, July). Why Software is So Bad. Technology Review, 32-39.
McDermott, Terry. (1995, June 4). A Question of Safety: Is the FAA Up to the Job? The Seattle Times, pp. A1+.
Norman, Donald A. (2002, July). Beyond the Computer Industry. Communications of the ACM, 120.
Peterson, I. (1991, December 14). Software Failure: Counting Up the Risks. Science News, 388-390.
Peterson, Ivars. (1995). Fatal Defect: Chasing Killer Computer Bugs. New York: Random House.
Sewell, Marc T, & Sewell, Laura M. (2002). The Software Architect’s Profession. Upper Saddle River: Prentice Hall.
Thibodeau, Patrick, & Rosencrance, Linda. (2002, July). Users Losing Billions Due to Bugs. Computerworld, 1-3.
Thompson, Nathanael. Interview. October 29, 2002.
--- and in the paper itself--------
"...in order to assuage those fears” (Thompson Interview, 2002).
“the risks of the traditional computer business must be revisited by each new industry, usually through failures” (Norman, 2002, p.120).
“Pilots will no longer fly the aircraft via direct electrical and mechanical controls” (Peterson, 1991, p 388).
----end help----
I got an A on the paper. And you are lazy.
Eat Meat.
try this site Sam http://owl.english.purdue.edu/handouts/ ... r_apa.html#
keep on rockin in the free world