This Article 
 Bibliographic References 
 Add to: 
Determining the Impact of Software Engineering Research on Practice
March 2008 (vol. 41 no. 3)
pp. 39-49
Leon J. Osterweil, University of Massachusetts, Amherst
Carlo Ghezzi, Politecnico di Milano
Jeff Kramer, Imperial College London
Alexander L. Wolf, Imperial College London
The Impact Project provides a solid and scholarly assessment of the impact software engineering research has had on software engineering practice. The assessment takes the form of a series of studies and briefings, each involving literature searches and, where possible, personal interviews.

1. P. Naur and B. Randell, eds., Software Engineering: Report of a Conference Sponsored by the NATO Science Committee, NATO, Scientific Affairs Division, 1969.
2. S. Redwine and W. Riddle, "Software Technology Maturation," Proc. 8th Int'l Conf. Software Eng., IEEE CS Press, 1985, pp. 189–200.
3. L. Osterweil et al., "Editorial," ACM Trans. Software Eng. and Methodology, vol. 14, no. 4, 2005, pp. 381–382.
4. J. Estublier et al., "Impact of Software Engineering Research on the Practice of Software Configuration Management," ACM Trans. Software Eng. and Methodology, vol. 14, no. 4, 2005, pp. 383–430.
5. B.G. Ryder, M.L. Soffa, and M. Burnett, "The Impact of Software Engineering Research on Modern Programming Languages," ACM Trans. Software Eng. and Methodology, vol. 14, no. 4, 2005, pp. 431–477.
6. W. Emmerich, M. Aoyama, and J. Sventek, "The Impact of Research on Middleware Technology," ACM Trans. Software Eng. and Methodology, to appear Oct. 2008.
7. L. Clarke and D. Rosenblum, "Historical Perspective on Runtime Assertion Checking in Software Development," SIGSOFT Software Eng. Notes, vol. 31, no. 3, 2006, pp. 25–37.
1. J.B. Goodenough, "Language Design for Program Reliability," IEEE Trans. Software Eng., June 1975, pp. 179–191.
2. J.B. Goodenough, "Structured Exception Handling," Proc. ACM SIGPLAN/SIGACT Symp. Principles of Programming Languages, ACM Press, Jan. 1975, pp. 204–224.
3. J.B. Goodenough, "Exception Handling: Issues and a Proposed Notation," Comm. ACM, Dec. 1975, pp. 683–696.
4. B. Liskov and A. Snyder, "Exception Handling in CLU," IEEE Trans. Software Eng., Nov. 1979, pp. 546–558.
5. J.D. Ichbiah et al., "Rationale for the Design of the ADA Programming Language," ACM SIGPLAN Notices, June 1979, pp. 1–261.
6. A. Koenig and B. Stroustrup, "Exception Handling for C+," The Evolution of C++: Language Design in the Marketplace of Ideas, J. Waldo, ed., MIT Press, 1993.
7. G. Gosling, B. Joy, and G.L. Steele Jr.,The Java Language Specification, Addison-Wesley, 1996.
1. M.E. Fagan, "Design and Code Inspections to Reduce Errors in Program Development," IBM Systems J., vol. 15, no. 3, 1976, pp. 182–211.
2. V.R. Basili et al., "The Empirical Investigation of Perspective-Based Reading," J. Empirical Software Eng., vol. 2, no. 1, 1996, pp. 133–164.
3. H.D. Mills, "Stepwise Refinement and Verification in Box-Structured Systems," Computer, June 1988, pp. 23–36.
4. V.R. Basili, G. Caldiera, and H.D. Rombach, "Goal Question Metric Paradigm," J. Marciniac, ed., Encyclopedia of Software Eng., John Wiley &Sons, 1994, pp. 528–532.
5. R. van Solingen and E. Berghout, Goal/Question/Metric Method: A Practical Guide for Quality Improvement of Software Development, McGraw-Hill, 1999.
6. F. McGarry, "What Is a Level 5?" Proc. 26th Ann. NASA Goddard Software Eng. Workshop, IEEE CS Press, 2001, pp. 83–90.
7. H.D. Rombach, V.R. Basili, and R.W. Selby, eds., Experimental Software Engineering Issues: A Critical Assessment and Future Directions, Springer-Verlag, 1993.
8. V.R. Basili and R.W. Selby, "Comparing the Effectiveness of Software Testing Techniques," IEEE Trans. Software Eng., vol. 13, no. 12, 1987, pp. 1278–1296.
9. R.W. Selby, V.R. Basili, and F. Baker, "Cleanroom Software Development Approach: An Empirical Evaluation," IEEE Trans. Software Eng., vol. 13, no. 9, 1987, pp. 1027–1037.
1. J.M. Correira and F. Biscotti, Market Share: AIM and Portal Software, Worldwide, 2005, Gartner market research report, June 2006; www.gartner.comDisplayDocument?ref=g_search&id=492790 .
2. S.T. Redwine and W.E. Riddle, "Software Technology Maturation," Proc. 8th Int'l Conf. Software Eng., IEEE CS Press, 1984, pp. 189–200.
1. K. Zuse, Der Plankalkül, Gesellschaft für Mathematik und Datenverarbeitung, no. 63, BMBW-GMD-63, 1972.
2. H.H. Goldstine and J. Von Neumann, "Planning and Coding Problems for an Electronic Computing Instrument," John von Neumann, Collected Works, A.H. Taub, ed., Pergamon Press, 1963, pp. 80–235.
3. A. Turing, "Checking a Large Routine;"
4. J. McCarthy, "Towards a Mathematical Science of Computation," 1963;
5. R.W. Floyd, "Assigning Meaning to Programs," Proc. Symp. Applied Mathematics, Am. Mathematical Soc., 1967, pp. 19–32.
6. C.A.R. Hoare, "An Axiomatic Basis of Computer Programming," Comm. ACM, Dec. 1969, pp. 576–580.
7. S.S. Yau and R.C. Cheung, "Design of Self-Checking Software," Proc. Int'l Conf. Reliable Software, ACM and IEEE CS Press, 1975, pp. 450–457.
8. D.C. Luckham, Programming with Specifications: An Introduction to Anna, a Language for Specifying Ada Programs, Springer-Verlag, 1990.
9. B. Meyer, Eiffel: The Language, Prentice Hall, 1991.
10. D.S. Rosenblum, "A Practical Approach to Programming with Assertions," IEEE Trans. Software Eng., vol. 21, no. 1, 1995, pp. 19–31.
11. B. Meyer, "Applying 'Design by Contract,'" Computer, Dec. 1992, pp. 40–51.
12. C.A.R. Hoare, "Assertions: A Personal Perspective," IEEE Annals of the History of Computing, vol. 25, no. 2, 2003, pp. 14–25.
13. P. Chalin, Ensuring Continued Mainstream Use of Formal Methods: An Assessment, Roadmap and Issues, D.S.R. Group, ed., Concordia University, 2005.

Index Terms:
software engineering research, Impact Project,
Leon J. Osterweil, Carlo Ghezzi, Jeff Kramer, Alexander L. Wolf, "Determining the Impact of Software Engineering Research on Practice," Computer, vol. 41, no. 3, pp. 39-49, March 2008, doi:10.1109/MC.2008.85
Usage of this product signifies your acceptance of the Terms of Use.