The first part of the assignment requires each group to identify 3 papers that you would find interesting to present. The papers are to be somehow related to software processes -- e.g. claiming a process is good, describing a process, studying a process, providing a summary of experiences related to using a process etc. The articles are to come from refereed publications associated with a professional society, e.g., IEEE or ACM. The most likely publications are ACM Communications or IEEE Computer or IEEE Software; these tend to be very readable and do not require substantial prior technical knowledge. Papers should be current (e.g., published in 2009 or 2010. If you have questions on what is meant by a software process, read Chapter 2 in Sommerville. Two easy ways to access the IEEE and ACM publications are via the Library's web site and/or actually walking over the bridge to the Library :-) .

I would like each group to email me by Monday, January 17 a list of three papers with full citation and abstract that you are willing to present. I will choose from each group's list one paper for that group to present -- assuming the papers are suitable, etc. and I get enough variety. If there are no acceptable papers on the list of three, I will likely ask for more papers, but may choose to assign a paper myself.

Last year's papers are listed at the end of this description to help you get a sense of the kinds of papers that I am looking for. Please do not select these papers -- you do not want to run the risk of my falling asleep during your presentation :-)


Grading: The grading for this assignment will be as follows:

Initial Selection:	10 points
Quality of Presentation:	20 points
Clarity and Quality of Content:	50 points
Integrity of Presentation:	10 points
Analysis of Material:	10 points

2010 Class-presented Articles

• Krasteva, I. and Ilieva, S. 2008. Adopting an agile methodology: why it did not work. In Proceedings of the 2008 international Workshop on Scrutinizing Agile Practices Or Shoot-Out At the Agile Corral > (Leipzig, Germany, May 10 - 10, 2008). APOS '08. ACM, New York, NY, 33-36. DOI= http://doi.acm.org/10.1145/1370143.1370150
  
  
• Dinakar, K. 2009. Agile development: overcoming a short-term focus in implementing best practices. In Proceeding of the 24th ACM SIGPLAN Conference Companion on Object Oriented Programming Systems Languages and Applications (Orlando, Florida, USA, October 25 - 29, 2009). OOPSLA '09. ACM, New York, NY, 579-588. DOI= http://doi.acm.org/10.1145/1639950.1639952
  
  
• Altarawneh, H. and Shiekh, A. 2008. A Theoretical Agile Process Framework for Web Applications Development in Small Software Firms. Software Engineering Research, Management and Applications, 2008. SERA '08. Sixth International Conference on 20-22 Aug. 2008 Page(s):125 - 132 Digital Object Identifier 10.1109/SERA.2008.14
  
  
• Wray, S. 2010. How does pair programming work? IEEE Software (to appear 2010) http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=5204068&isnumber=5204063
  
  
• Moe, N 2009. Overcomming Barriars to Self-Management in Software Teams. IEEE Software (2009): 20-26. Web. .
  
  
• Gagnon and Nirkula
  Kemerer, C. and Paulk, M. 2009. The Impact of Design and Code Reviews on Software Quality: An Empirical Study Based on PSP Data, IEEE Transactions on Software Engineering, Vol. 35, No. 4, July/August 2009 http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4815279&isnumber=5186358
  
  
• Fahey, Larson, and Sachdev
  Nan, N. and Harter, D. 2009. Impact of Budget and Schedule Pressure on Software Development Cycle Time and Effort. IEEE Transactions on Software Engineering, pp. 624-637. 02 Oct 2009. http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4815275&isnumber=5275149
  
  
• Erdogmus, H. 2009. A Process That Is Not, IEEE Software 26(6), 2009, pp. 4-7 http://www.computer.org/plugins/dl/pdf/mags/so/2009/06/mso2009060004.pdf?template=0&loginState=1&userData=anonymous-IP%253A%253A141.219.69.73
  
  
• Burnett, M. What Is End-User Software Engineering and Why Does It Matter? End-User Development. Journal of Organizational and End-User Computing 22(1), (to appear 2010) Pages 15-28 http://www.springerlink.com/content/58l74632874134u6/fulltext.pdf
  
  
• Bessey, Block, Chelf, Chou, Fulton, Hallem, Henri-Gros, Kamsky, McPeak, and Engler. A Few Billion Lines of Code Later: Using Statistic Analysis to Find Bugs in the Real World. Communications of the ACM, 53(2), 2010, pg 66-75, 2010.