I'm now managing a team at nVidia. These pages are old. To contact me, use david@coppit.org, since I check that account more often.

Collected Papers

My papers are on my publication page.

Classic Papers

C. A. R. Hoare, "An axiomatic basis for computer programming," Communications of the ACM, 12(10):576-580
Fred Brooks, "No silver bullet: Essence and accidents of software engineering," IEEE Computer, 20(4):10-19, April 1987.
Mary Shaw, "Prospects for an engineering discipline of software," IEEE Software, November 1990, pp. 15-24.
D.L. Parnas, "Why Software Jewels are Rare," Computer, 29(2), 1996.
J. N. Buxton, "Software Engineering—20 Years On and 20 Years Back," J. Systems and Software, Vol. 13, 1990, p. 153-155.
Wasserman, Anthony "Toward a Discipline of Software Engineering". IEEE Software 13(6), November 1996.
Edsger W. Dijkstra, "On the reliability of programs", n.d., circulated privately.

Case Studies

John Schwartz, "Computer Program That Analyzed Shuttle Was Misused, Engineer Says," New York Times, August 25, 2003.
United Stated General Accounting Office, "GAO/IMTEC-92-26 Patriot Missile Software Problem." (4)
N.G. Leveson and C.S. Turner, "An Investigation of the Therac-25 Accidents," IEEE Computer, vol. 26, no. 7, pages 18-41, July 1993. (16)
Leveson, Nancy G. "Appendix A, Medical Devices: The Therac-25 Story," Safeware: System Safety and Computers. Reading, MA: Addison-Wesley, 1995, pp. 515-553. (16)
IAEA, August 2001, "Investigation of an Accidental Exposure of Radiotherapy Patients in Panama: Report of a Team of Experts", 26 May-1 June 2001, IAEA (Vienna, Austria).
G.J. Holzmann, Design and Validation of Computer Protocols, Prentice Hall, 1991. (7)
Anthony Hall and Roderick Chapman, "Correctness by Construction: Developing a Commercial Secure System,"IEEE Software Jan/Feb 2002, pp 18-25. (6)
European Space Agency, Ariane 5: Flight 501 failure. Report by the enquiry board. (6)
James Oberg, "Why The Mars Probe Went Off Course", IEEE Spectrum 36:12, December 1999. (For more detailed information, see the official MCO Report). (6)
Mars Program Independent Assessment Team, Summary Report. (For more detailed information, see the full JPL report parts 1, 2, 3, 4, and 5.) (5)
Titan/Centaur/Milstar IVB-32 Report. (10)
Mike Jones, "What really happened on Mars?." (1.5)
Glenn Reeves, "What really happened on Mars? -- Followup." (1.5)
K. Havelund, M. Lowry, S. Park, C. Pecheur, J. Penix, W. Visser, and Jon L. White, "Formal Analysis of the Remote Agent - Before and After Flight," The Fifth NASA Langley Formal Methods Workshop, Virginia, June, 2000 (10)

The Software Crisis

W.W. Gibbs, Software's Chronic Crisis," Scientific American, pages 72-81, September, 1994.
Simson Garfinkel, "History's Worst Bugs," Wired News, November 8, 2005. (2)

General Research

Mary Shaw, "Writing Good Software Engineering Research Papers," Proceedings of the 25th International Conference on Software Engineering, Portland, Oregon, IEEE Computer Society, 2003, pp. 726-736.
Roy Levin and David D. Redell, An Evaluation of the Ninth SOSP Submissions or How (and How Not) to Write a Good Systems Paper," ACM SIGOPS Operating Systems Review, Vol. 17, No. 3 (July, 1983), pages 35-40.

Tools

Sam Owre, Natarajan Shankar, and John Rushby, "PVS: A Prototype Verification System, CADE 11, Saratoga Springs, NY, June 1992. (3)
Daniel Jackson, "Alloy: A Lightweight Object Modelling Notation, ACM Transactions on Software Engineering and Methodology, Volume 11, Issue 2 (April 2002), pp. 256-290. (16)
David L. Detlefs, K. Rustan M. Leino, Greg Nelson, and James B. Saxe, "Extended static checking," Technical Report #159, Compaq Systems Research Center, Palo Alto, CA, December 1998. (20)
K. Havelund and T. Pressburger, "Model Checking Java Programs Using Java PathFinder," International Journal on Software Tools for Technology Transfer, 2(4) April 2000. (13)

Manuals

PVS

Alloy Analyzer

Alloy Reference Manual

Requirements

Nuseibeh, Kramer, Finkelstein, "A Framework for Expressing the Relationships Between Multiple Views in Requirements Specification", in Transactions on Software Engineering, October 2004, pages 760-773. (12)
John Rushby, "Calculating with Requirements", in Proceedings of the 3rd IEEE International Symposium on Requirements Engineering, Annapolis, MD, Jan 1997, pages 144-146. (2)
Kathryn L. Heninger, "Specifying Software Requirements for Complex Systems: New Techniques and Their Application," IEEE Transactions Software Engineering 6(1), Jan. 1980, p. 2-13. p28-carroll.pdf
J.M. Carroll, "Making Use a Design Representation," Communications of the ACM, vol. 37, no. 12, pp. 28-35, Dec. 1994.

Design

Parnas, D., "On the criteria to be used in decomposing systems into modules," Communications of the ACM 15(2), 1053-1058, 1972.
David L. Parnas, "Designing Software for Ease of Extension and Contraction," IEEE Transactions on Software Engineering, 5(2), March 1979, p. 128-138. [ICSE]
D. Parnas, "On the Design and Development of Program Families," IEEE Transations on Software Engineering, SE-2, March, 1976.
F. DeRemer and H.H. Kron, "Programming-in-the-Large Versus Programming-in-the-Small," IEEE Transations on Software Engineering, SE-2, 1976, p. 80-86. [Dagstuhl]
David Garlan and Mary Shaw, "An Introduction to Software Architecture," Tech. Report CMU-CS-94-166 (Also appeared in Advances in Software Engineering and Knowledge Engineering, ed. by V.Ambriola and G.Tortora, World Scientific Publishing Company, New Jersey, 1993.)

Formal Methods Practice

Peter Amey, Praxis High Integrity Systems, "Yours faithfully: an everyday story of formality," Invited keynote address, in "Practical Elements of Safety", Proceedings of the Twelfth Safety-critical Systems Symposium, Birmingham, UK, February 2004. Copyright Spinger-Verlag 2004. (6)
Nancy G. Leveson, "The Role of Software in Spacecraft Accidents," Journal of Spacecraft and Rockets, July-August 2004 vol.41 no.4, pp 564-575. (8)
Axel van Lamsweerde. Formal specification: a roadmap. In Proceedings of the 22nd International Conference on Software Engineering--The Future of Software Engineering, pages 149-59, Limerick, Ireland, 4-11 June 2000. IEEE. (7)
Anthony Hall, "Seven Myths of Formal Methods," IEEE Software, Sept. 1990, p. 11-19. (8)
Jonathan P. Bowen and Michael G. Hinchey, "Seven More Myths of Formal Methods," IEEE Software 12:4, July 1995, p. 34-41. (7)

Formal Modeling

Jeannette M. Wing, "Hints to Specifiers," CMU technical report CMU-CS-95-118R. (10)
Jeannette M. Wing, "A Specifier's Introduction to Formal Methods," IEEE Computer, Sept. 1990, p. 8-22. (12)

Programming

Harlan D. Mills, "Structured Programming: Retrospect and Prospect," IEEE Software, 3(4), Nov. 1986, p. 58-66.
N. Wirth, "Program Development by Stepwise Refinement," Communications of the ACM, 14(4):221-227, April 1971.
David L. Parnas, Paul C. Clements, David M. Weiss, "The Modular Structure of Complex Systems," ICSE-7, 1984.

New Abstraction Methods and Cross-Cutting Concerns

Apel, et al., "Aspectual mixin layers: aspects and features in concert", , In Proceedings of the 28th International Conference on Software Engineering, 2006.
Chu-Carroll, Wright, and Ying, "Visual separation of concerns through multidimensional program storage," In Proceedings of the 2nd International Conference on Aspect-Oriented Software Development, IEEE, 2003. (10)
Rajan and Sullivan, "Classpects: Unifying Aspect- and Object-Oriented Language Design," In Proceedings of the 20th International Conference on Automated Software Engineering, IEEE, 2005. (10)
Sullivan, et. al, "Information hiding interfaces for aspect-oriented design," In Proc. of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering , ACM Press, 2005. (10)
Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Videira Lopes, C., Loingtier, J.-M., and Irwin, J., "Aspect-Oriented Programming," In Proc. of ECOOP, Springer-Verlag (1997).
Martin P. Robillard and Gail C. Murphy, "Automatically Inferring Concern Code from Program Investigation Activities," In Proceedings of the 18th International Conference on Automated Software Engineering, pages 225-234, October 2003.
E. Baniassad and S. Clarke, "Theme: an approach for aspect-oriented analysis and design," ICSE 2004, p 158-167.
S. Clarke, W. Harrison, H. Ossher and P. Tarr, "Subject-oriented Design: Towards Improved Alignment of Requirements, Design and Code," OOPSLA '99, p. 325-337.
W. G. Griswold, J.J. Yuan, and Y. Kato, "Exploiting the Map Metaphor in a Tool for Software Evolution," ICSE 2001.
Martin P. Robillard and Gail C. Murphy, "Concern Graphs: Finding and Describing Concerns Using Structural Program Dependencies," In Proceedings of the 24th International Conference on Software Engineering, pages 406-416, May 2002.

Program Analysis

Ramanathan, et al., "Sieve: A Tool for Automatically Detecting Variations Across Program Versions", , In Proceedings of the 21st International Conference on Automated Software Engineering, 2006.
Kim, et. al, "Predicting Faults from Cached History", In Proceedings of the 29th International Conference on Software Engineering, 2007.
Schuler, et al., "A Dynamic Birthmark for Java", , In Proceedings of the 22nd International Conference on Automated Software Engineering, 2007.
Taghdiri, "Inferring Specifications to Detect Errors in Code," In Proceedings of the 19th International Conference on Automated Software Engineering, 2004.
David Evans, "Static Detection of Dynamic Memory Errors," In SIGPLAN Conference on Programming Language Design and Implementation (PLDI '96), Philadelphia, PA, May 1996.
Michael D. Ernst, Jake Cockrell, William G. Griswold, David Notkin, "Dynamically Discovering Likely Program Invariants to Support Program Evolution," IEEE Transactions on Software Engineering, 27(2): 99-123 (2001).
David S. Rosenblum, "A Practical Approach to Programming with Assertions," IEEE Transactions on Software Engineering, vol. 21, no. 1, Jan. 1995, pp. 19-31.
N. Nethercote and J. Seward, "Valgrind: A Program Supervision Framework," Proceedings of the Third Workshop on Runtime Verification (RV'03), Boulder, Colorado, USA, July 2003.

Process Models

R. Linger, "Cleanroom Process Model," IEEE Software, March 1994.
Beck, K., "Embracing Change with Extreme Programming," IEEE Computer. 32(10), p. 70-77, 1999.
Barry W. Boehm, "A Spiral Model of Software Development and Enhancement," IEEE Computer, 21(5), May 1988, p. 61-72. [Dagstuhl]
Eric Raymond, "The Cathedral and the Bazaar"
Victor R. Basili, "Iterative Enhancement: A Practical Technique for Software Development," IEEE Transactions on Software Engineering. v.SE-1, n.4, December 1975, pp.390-396
Leon J. Osterweil, "Software Processes Are Software Too," In Proceedings of the 9th International Conference on Software Engineering, pp. 2-13, Monterey, CA, March 1987. [ICSE]
David L. Parnas, Paul C. Clements, "A Rational Design Process: How and Why to Fake It," IEEE Transactions on Software Engineering, 12(2), February, 1986, p. 251-257.

Reverse Engineering and Restructuring

H. A. Müller, M. A. Orgun, S. R. Tilley, and J. S. Uhl, "A reverse engineering approach to subsystem structure identification," Journal of Software Maintenance: Research and Practice, 5(4):181-204, Dec. 1993.
M. Weiser, "Program Slicing," IEEE Transactions on Software Engineering, vol. 10, no. 4, pp. 352-357, July, 1984. [ICSE]

Formal Methods

Clarke and Wing, "Formal Methods: State of the Art and Future Directions," In Proceedings of Formal Methods 2006.
Jeannette M. Wing, "A Specifier's Introduction to Formal Methods," IEEE Computer, Sept. 1990, p. 8-22.
J.M. Atlee and J.D. Gannon, "State-Based Model Checking of Event-Driven System Requirements," IEEE Transactions on Software Engineering, 19(1):24-40, January 1993.
Daniel Jackson, "Automating First-Order Relational Logic," Proc. ACM SIGSOFT Conf. Foundations of Software Engineering, November 2000.
Robert Vienneau, "A Review of Formal Methods," Kaman Science Corp., 1993, p. 3-15 and 27-33.
Barbara H. Liskov, Stephen N. Zilles, "Specification Techniques for Data Abstractions," IEEE Transactions on Software Engineering, 1(1), March, 1975, p. 7-19.
Anthony Hall, "Seven Myths of Formal Methods," IEEE Software, Sept. 1990, p. 11- 19.
E. Clarke and J. Wing. "Formal methods: State of the art and future directions," ACM Computing Surveys, Vol. 28, No. 4, 1996.
Richard A. De Millo, Richard J. Lipton, Alan J. Perlis, "Social Processes and Proofs of Theorems and Programs," Communications of the ACM, 22(5), May 1979, p. 271-280.

Modularity and Components

K. Sullivan, W. G. Griswold, Y. Cai, B. Hallen, "The Structure and Value of Modularity in Design," 8th European Software Engineering Conference; Held Jointly with 9th ACM SIGSOFT Symposium on the Foundations of Software Engineering (ESEC/FSE 2001), September 2001.
Carliss Y. Baldwin , Kim B. Clark, Design Rules, Vol. 1: The Power of Modularity, 2000.
M.D. McIlroy, "'Mass Produced' Software Components," In Software Engineering: A Report on a Conference Sponsored by the NATO Science Committee, P. Naur and B. Randell (eds.), pp. 138-155, Garmisch, Germany, October 1968.
M. Franz, "Dynamic Linking of Software Components," IEEE Computer, 30:3, pp. 74-81; March 1997.
Weyuker, E.J., "Testing Component-Based Software: A Cautionary Tale," IEEE Software. 15(5), p. 54-59, 1998.

Quality Assurance

M. E. Fagan, "Design and Code Inspections to Reduce Errors in Program Development," IBM Systems Journal, No. 3, 1976, p. 182-211.
W. Richards Adrion, Martha A. Branstad, and John C. Cherniavsky, "Validation, verification, and testing of computer software," ACM Computing Surveys, 14(2):159-192, June 1982.
S.S. Brilliant, J.C. Knight, and N.G. Leveson, "Analysis of faults in an N-version software experiment," IEEE Transactions on Software Engineering, Vol. 16, No. 2, pp. 238-247, 1990.

Testing

Pacheco, et. al, "Feedback-directed Random Test Generation", In Proceedings of the 29th International Conference on Software Engineering, 2007.
Cadar, et. al, "EXE: Automatically Generating Inputs of Death", In Proceedings of 13th ACM Conference on Computer and Communications Security, 2006.
Godefroid, et. al, "DART: Directed Automated Random Testing", In Proceedings of ACM SIGPLAN 2005 Conference on Programming Language Design and Implementation, pages 213-223, Chicago, June 2005.
DeMillo and Offutt, "Constraint-Based Automatic Test Data Generation", IEEE Transactions on Software Engineering, 900-910, September 1991.
Darko Marinov, Alexandr Andoni, Dumitru Daniliuc, Sarfraz Khurshid, and Martin Rinard, "An evaluation of exhaustive testing for data structures," Technical Report MIT-LCS-TR-921, MIT CSAIL, Cambridge, MA, September 2003.
C. Boyapati, S. Khurshid, and D. Marinov, "Korat: Automated Testing Based on Java Predicates," International Symposium on Software Testing and Analysis, Rome, Italy. Jul 2002.
Dawson Engler, David Yu Chen, Seth Hallem, Andy Chou, and Benjamin Chelf, "Bugs as Deviant Behavior: A General Approach to Inferring Errors in Systems Code," SOSP 2001.
Mankefors-Christiernin and Boklund, "Multiple Profile Evaluation Using a Single Test Suite in Random Testing," In Proceedings of the International Symposium on Software Reliability Engineering, pages 283-94, 2004. IEEE.
S. Mankefors, R. Torkar, and A. Boklund, "New quality estimations in random testing," In Proceedings of the International Symposium on Software Reliability Engineering, pages 468-78, Denver, Colorado, 17-20 November 2003. IEEE.
D. Marinov and S. Khurshid, "TestEra: A Novel Framework for Automated Testing of Java Programs," 16th IEEE Conference on Automated Software Engineering, San Diego, CA. Nov 2001.
Gregg Rothermel and Mary Jean Harrold, "Analyzing Regression Test Selection Techniques," IEEE Transactions on Software Engineering, 22(8):529-551, August 1996.
Andreas Zeller and Ralf Hildebrandt, "Simplifying and Isolating Failure-Inducing Input," IEEE Transactions on Software Engineering, 28(2), February 2002, pp. 183-200.

Methodology

V.R. Basili, R.W. Selby, and D.H. Hutchens, "Experimentation in Software Engineering," IEEE Transactions on Software Engineering, SE-12(7):733-743, July 1986.
R. Brooks, "Studying Programmer Behavior Experimentally: The Problems of Proper Methodology," Communications of the ACM, 23(4), 207-213.
Walter F. Tichy, "Should computer scientists experiment more? 16 reasons to avoid experimentation," IEEE Computer, Vol. 31, No. 5, May 1998.
M. Zelkowitz and D. Wallace, "Experimental models for validating technology," IEEE Computer, Vol. 31, No. 5, 1998, pp.23-31.

Reuse

C. W. Krueger, "Software Reuse," ACM Computing Surveys, 24(2):131-184, June 1992.
D. Garlan, R. Allen and J. Ockerbloom, "Architectural Mis-match: Why Reuse is So Hard," Proceedings of the 17th International Conference on Software Engineering (ICSE-17), April 1995.

Safety and Reliability

P.E. Ammann, S. S. Brilliant and J. C. Knight, "The Effect Of Imperfect Error Detection On Reliability Assessment Via Life Testing," IEEE Transactions on Software Engineering, Vol. 20, No. 2, February 1994.
N.G. Leveson, "Software Safety: What, Why, and How," ACM Computing Surveys, 18(2):125-163, June 1986.
NA. L. Goel, "Software Reliability Models: Assumptions, Limitations, and Applicability," IEEE Transactions on Software Engineering, 11(12), December 1985, p. 1411-1423.
W.E. Howden, Y.D. Huang, "Software Trustability Analysis," ACM Transactions on Software Engineering and Methodology, vol. 4, no. 1, pp. 36-64, Jan. 1995.

Proofs of Programs

Allen Tucker and Robert Noonan, "Program Correctness", Chapter 12. (3 math, 5 semantics, 5 JML, 6 DbC)
Brian Cantwell Smith, "The limits of correctness", ACM SIGCAS Computers and Society. NY: ACM Press, 1985. (8)

Testing

P.E. Ammann, S. S. Brilliant and J. C. Knight, "The Effect Of Imperfect Error Detection On Reliability Assessment Via Life Testing," IEEE Transactions on Software Engineering, Vol. 20, No. 2, February 1994. (7)

Maintenance

Anvik, et al., "Who should fix this bug?", In Proceedings of the 28th International Conference on Software Engineering, 2006.
Kim, et. al, "An Empirical Study of Code Clone Genealogies," In Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering (ESEC/FSE-13) , September 2005, pages 187-196. (10)
Robillard and Murphy, "How Effective Developers Investigate Source Code: An Exploratory Study," In Transaction on Software Engineering, December 2004, pages 889-903. (12)
Myers, Aung, and Ko, "Eliciting design requirements for maintenance-oriented IDEs: a detailed study of corrective and perfective maintenance tasks," In Proceedings of the 20th International Conference on Automated Software Engineering, IEEE, 2005. (10)
Ko, A.J., Aung, H.H., Myers, B.A., "Eliciting Design Requirements for Maintenance-oriented IDEs: A Detailed Study of Corrective and Perfective Maintenance Tasks," Proceedings of the 27th International Conference on Software Engineering, St. Louis, MO, May 2005.
W.G. Griswold and D. Notkin, "Automated assistance for program restructuring," ACM TOSEM Vol. 2, (No. 3), 228-69, July 1993.
Parnas, D. "Software Aging," ICSE 16, 1994.
Edsger W. Dijkstra, "Go To Statement Considered Harmful," Letter to the Editor in Communications of the ACM, 11(3), March 1968, p. 147-148.
L.A. Belady and M.M. Lehman, "A Model of Large Program Development," IBM Systems Journal, 15(3), 1976.

Process and Productivity

K. Beck, "Embracing Change with Extreme Programming," IEEE Computer. 32(10), p. 70-77, 1998
Fredrick P. Brooks, The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition, Addison Wesley, Reading, Mass., second edition, 1995.
Tom Demarco, and Timothy Lister, Peopleware: Productive Projects and Teams. Dorset House, 1987.

Back to David Coppit's Homepage.

Last changed September 12 2007 14:27:25. David Coppit, coppit@cs.wm.edu

There have been 1241076 hits since Thu Jun 9 14:49:55 2005