Advertisement

Modeling Software Evolution with Game Theory

  • Vibha Sazawal
  • Nikita Sudan
Part of the Lecture Notes in Computer Science book series (LNCS, volume 5543)

Abstract

A wrong design decision at any point in the software lifecycle can lead to cost overruns and competitive disadvantage. We describe how lightweight game theory can help software engineering teams plan for future design and maintenance decisions. To demonstrate our approach, we model the real-world evolution of java.util.Calendar using our lightweight Basic Software Evolution Game. The game expressively models both what actually happened as well as circumstances when alternate design decisions would be optimal.

Keywords

Software evolution game theory software design decisions 

Preview

Unable to display preview. Download preview PDF.

Unable to display preview. Download preview PDF.

References

  1. 1.
    Sullivan, K., Griswold, W., Cai, Y., Hallen, B.: The structure and value of modularity in software design. In: ESEC/FSE (2001)Google Scholar
  2. 2.
    Boehm, B.W.: Software Engineering Economics. Prentice Hall PTR, Englewood Cliffs (1981)zbMATHGoogle Scholar
  3. 3.
    Denne, M., Cleland-Huang, J.: Software By Numbers. Prentice Hall PTR, Englewood Cliffs (2003)Google Scholar
  4. 4.
    Dutta, P.K.: Strategies and Games: theory and practice. MIT Press, Cambridge (1999)Google Scholar
  5. 5.
    Keeney, R.L.: Value-Focused Thinking. Harvard University Press (1996)Google Scholar
  6. 6.
    Boehm, B., Abts, C., Brown, A.W., Chulani, S., Clark, B.K., Horowitz, E., Madachy, R., Reifer, D.J., Steece, B.: Software Cost Estimation with Cocomo II. Prentice Hall PTR, Englewood Cliffs (2000)Google Scholar
  7. 7.
    Parnas, D.: On the criteria to be used in decomposing systems into modules. Communications of the ACM (1972)Google Scholar
  8. 8.
    Garlan, D., Kaiser, G., Notkin, D.: Using tool abstraction to compose systems. IEEE Computer (1992)Google Scholar
  9. 9.
  10. 10.
  11. 11.
    Sun Developer Network: Bug ID: 4609228 (cal) RFE: Provide additional local calendars in Java (2001-2005), http://bugs.sun.com
  12. 12.
    ICU Project: International components for unicode (2000-2008), http://icu-project.org
  13. 13.
    Shor, M.: Extensive form game applet (2001-2006), http://www.gametheory.net/Mike/applets/ExtensiveForm/
  14. 14.
    Boehm, B.W.: Theory-W software project management: Principles and examples. IEEE Transitions on Software Engineering (1989)Google Scholar
  15. 15.
    Boehm, B.W., Bose, P.: A collaborative spiral software process model based on theory W. In: ICSP (1994)Google Scholar
  16. 16.
    Zagal, J.P., Ahués, R.S., Voehl, M.N.: Maintenance-oriented design and development: A case study. IEEE Software (2002)Google Scholar
  17. 17.
    Brandenburger, A.M., Nalebuff, B.J.: The right game: Use game theory to shape strategy. Harvard Business Review (1995)Google Scholar
  18. 18.
    Oza, N.V.: Game theory perspectives on client - vendor relationships in offshore software outsourcing. In: EDSER (2006)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2009

Authors and Affiliations

  • Vibha Sazawal
    • 1
  • Nikita Sudan
    • 1
  1. 1.UM Institute for Advanced Computing Studies (UMIACS)University of MarylandUSA

Personalised recommendations