Difference: Schedule (1 vs. 8)

• * Does code decay? Assessing the evidence from change management data. S.G. Eick, T.L. Graves, A.F. Karr, J.S. Marron and A. Mockus. IEEE TSE, 2001. Paper

• * Hipikat: Recommending pertinent software development artifacts. D. Cubranic and G.C. Murphy. Proc. of ICSE 2003. Paper
• * Mining version histories to guide software changes. T. Zimmermann, P. Weisgerber, S. Diehl and A. Zeller. Proc. of ICSE 2004. Paper
• Note there are journal versions of each of these papers. I have selected the conference versions because we will concentrate on the basic ideas.

• What makes good research in software engineering? M. Shaw. Int'l Journal on Software Tools for Technology Transfer. 2002. Paper
• Experimental models for validating technology. M. Zelkowitz and D.R. Wallace. Computer, 1998. Paper

• * Implementing layered designs with mixin layers. Y. Smaragdakis and D. Batory. Proc. of ECOOP, 1998. Paper

• * Extended static checking for Java. Flanagan, K.R.M. Leino, M. Lillibridge, G. Nelson, J.B. Saxe, and R. Stata. Proc. of PLDI, 2002.Paper
• Houdini: An Annotation Assistant for ESC/Java C. Flanagan and K.R.M. Leino. Proc. of FME 2001. Paper

• * Dynamically Discovering Likely Program Invariants to Support Program Evolution. M.D. Ernst, J. Cockrell, W.G. Griswold and D. Notkin. Proc. of ICSE 1999. Paper
• Invariant Inference for Static Checking: An Empirical Evaluation. J.W. Nimmer and M.D. Ernst. Proc of FSE, 2002. Paper

• On the criteria to be used in decomposing systems into modules. D. Parnas. CACM, Dec. 1972. Paper
• Decoupling change from design. M. VanHilst and D. Notkin. Proc. of Foundations of SE, 1996. Paper

Papers marked with a * are suitable for writing a critical evaluation.

• From object-orientation to goal orientation: A paradigm shift for requirements engineeringA. van Lamsweerde and E. Lettier. 2004. 9th Int'l Workshop on Radical Innovations of Software and Systems Engineering in the Future. Paper
• * Scenario-based requirements engineering. A. Sutcliffe. Location coming. 2004. 11th IEEE Int'l RE Conference. Paper

• Dependable software by design. D. Jackson. Scientific American. June 2006. Paper
• Modeling the active badge system. S. Xu.Paper

• Introduction to the special issue on software architecture. D. Garlan and D. Perry. 1995. IEEE Transactions on Software Engineering. Paper
• * ArchJava: Connecting software architecture to implementation. J. Aldrich, C. Chambers and D. Notkin. 2002. Proc. of Int'l Conf. on SE. Paper
• Software reflexion models: Bridging the gap between source and high-level models. G.C. Murphy, D. Notkin and K. Sullivan. 1995. Proc. of Foundations of SE. Paper

• From object-orientation to goal orientation: A paradigm shift for requirements engineering. A. van Lamsweerde and E. Lettier. Location coming. 2004. Link coming.
• Scenario-based requirements engineering. A. Sutcliffe. Location coming. 2004. Link coming.

Week of Jan 28 (Alloy)

• Dependable software by design. D. Jackson. Scientific American. 2006. Link coming.
• Modeling the active badge system. S. Xu. Link/location coming.

Week of Jan 28 (Software Architecture) Include capture/analysis/conformance?

Week of Feb 4 (Software Design/Modularization)

• On the criteria to be used in decomposing systems into modules. D. Parnas...
• Decoupling change from design.

Week of Feb 11 (Reading week)

• No papers due to reading week

Week of Feb 18 (Composing Modules)

Week of Feb 25 (Advanced Static Analysis)

Week of Mar 3 (Advanced Dynamic Analysis)

Week of Mar 10 (Software Evolution)

Week of Mar 17 (no class)

Week of Mar 24 (Tools I - Recommenders)

Week of Mar 31 (Tools II - Bug Finders?)

Week of Apr 7 (Evaluation Methods)

-- Main.murphy - 16 Jan 2008