Research note - Sell first, fix later: Impact of patching on software quality

Management Science

Volumn 52, Issue 3, 2006, Pages 465-471

  Arora, Ashish ^a   Caulkins, Jonathan P ^a   Telang, Rahul ^a  

^a CARNEGIE MELLON UNIVERSITY   (United States)

Author keywords

Fixed costs; Patching; Software bugs; Software quality; Time of entry

Indexed keywords

PATCHING; SOFTWARE BUGS; SOFTWARE QUALITY;

COMPUTER VIRUSES; COSTS; MARKETING; PROBLEM SOLVING;

COMPUTER SOFTWARE;

EID: 33644916146     PISSN: 00251909     EISSN: 15265501     Source Type: Journal    
DOI: 10.1287/mnsc.1050.0440     Document Type: Article

References (20)

1. Banker, R., S. Slaughter. 1997. A field study of scale economies in software maintenance. Management Sci. 43(12) 1709-1725.
2. Baskerville, R., L. Levine, J. Pries-Heje, B. Ramesh, S. Slaughter. 2001. How Internet software companies negotiate quality. IEEE Comput. 34(5) 51-57.
3. Bessen, James. 2002. Open source software: Free provision of complex public goods. Working paper, Massachusetts Institute of Technology, Cambridge, MA.
4. Brooks, F. R. 1995. The Mythical Man Month, 2nd ed. Addison-Wesley, Reading, MA.
5. Cohen, M. A., J. Eliashberg, Ho Teck-Hua. 1996. New product development: The performance and time-to-market tradeoff. Management Sci. 42(2) 173-186.
6. Davidson, W. L., III, D. L. Worrell. 1992. The effect of product recall announcements on shareholder wealth. Strategic Management J. 13(6) 467-473.
7. Griffin, A. 1993. Metrics for measuring product development cycle times. J. Product Innovation Management 10(2) 112-125.
8. Hendricks, K. B., V. R. Singhal. 1997. Delays in new product introductions and the market value of the firm: The consequences of being late to the market. Management Sci. 43(4) 422-436.
9. Information Week. 2002. Poor software quality: Time to do something about it. (May 20) www.informationweek.com
10. Information Week. 2004. Get ready to patch. (August 30) www.informationweek.com
11. Information Week. 2005. Microsoft: No patch before its time. (March 8) www.informationweek.com
12. Jarrell, G., S. Peltzman. 1985. The impact of product recalls on the wealth of sellers. J. Political Econom. 93(1) 512-536.
13. Krishnan, M. S., C. H. Kriebel, S. Kekre, T. Mukhopadhyay. 2000. An empirical analysis of productivity and quality in software products. Management Sci. 46(6) 745-759.
14. Lilien, G., E. Yoon. 1990. The timing of competitive market entry: An exploratory study of new industrial products. Management Sci. 36(5) 568-585.
15. Moorthy, S. 1988. Product and price competition in a duopoly. Marketing Sci. 7(2) 141-168.
16. NIST Report. 2002. The economic impacts of inadequate infrastructure for software testing. National Institute of Standards and Technology, Gaithersburg, MD.
17. Paulk, M. C., B. Curtis, M. B. Chrissis, C. V. Weber. 1995. The Capability Maturity Model: Guidelines for Improving the Software Process for Software. Addison-Wesley, Reading, MA.
18. Picker, R. 2004. Cyber security: Of heterogeneity and autarky. Olin working paper no. 223, University of Chicago Law and Economics, Chicago, IL.
19. Reddy, B., D. S. Evans. 2002. Government preferences for promoting open-source software: A solution in search of a problem. Working paper, http://ssrn.com.
20. Zirger, B., M. Maidique. 1990. A model of new product development: An empirical test. Management Sci. 36(7) 867-883.