Advertisement

Dealing with Known Unknowns: Towards a Game-Theoretic Foundation for Software Requirement Evolution

  • Le Minh Sang Tran
  • Fabio Massacci
Part of the Lecture Notes in Computer Science book series (LNCS, volume 6741)

Abstract

Requirement evolution has drawn a lot of attention from the community with a major focus on management and consistency of requirements. Here, we tackle the fundamental, albeit less explored, alternative of modeling the future evolution of requirements.

Our approach is based on the explicit representation of controllable evolutions vs observable evolutions, which can only be estimated with a certain probability. Since classical interpretations of probability do not suit well the characteristics of software design, we introduce a game-theoretic approach to give an explanation to the semantic behind probabilities. Based on this approach we also introduce quantitative metrics to support the choice among evolution-resilient solutions for the system-to-be.

To illustrate and show the applicability of our work, we present and discuss examples taken from a concrete case study (the security of the SWIM system in Air Traffic Management).

Keywords

software engineering requirement evolution observable and controllable rules game-theoretic 

References

  1. 1.
    Anderson, C.: The long tail. Wired (October 2004)Google Scholar
  2. 2.
    Anton, A., Potts, C.: Functional paleontology: The evolution of user-visible system services. TSE 29(2), 151–166 (2003)Google Scholar
  3. 3.
    Brier, J., Rapanotti, L., Hall, J.: Problem-based analysis of organisational change: a real-world example. In: Proc. of IWAAPF 2006. ACM, New York (2006)Google Scholar
  4. 4.
    d’Avila Garcez, A., Russo, A., Nuseibeh, B., Kramer, J.: Combining abductive reasoning and inductive learning to evolve requirements specifications. IEEE Proceedings - Software 150(1), 25–38 (2003)CrossRefGoogle Scholar
  5. 5.
    Elberse, A.: Should you invest in the long tail? Harvard Business Review (2008)Google Scholar
  6. 6.
    Fabbrini, F., Fusani, M., Gnesi, S., Lami, G.: Controlling requirements evolution: a formal concept analysis-based approach. In: ICSEA 2007 (2007)Google Scholar
  7. 7.
    FAA. System wide information management (SWIM) segment 2 technical review. Tech. report (2009)Google Scholar
  8. 8.
    Felici, M.: Observational Models of Requirements Evolution. PhD thesis (2004)Google Scholar
  9. 9.
    Ghose, A.: A formal basis for consistency, evolution and rationale management in requirements engineering. In: ICTAI 1999 (1999)Google Scholar
  10. 10.
    Ghose, A.: Formal tools for managing inconsistency and change in re. In: IWSSD 2000. IEEE Computer Society, Washington, DC, USA (2000)Google Scholar
  11. 11.
    Harker, S., Eason, K., Dobson, J.: The change and evolution of requirements as a challenge to the practice of software engineering. In: RE 2001 (1993)Google Scholar
  12. 12.
    Hassine, J., Rilling, J., Hewitt, J., Dssouli, R.: Change impact analysis for requirement evolution using use case maps. In: IWPSE 2005 (2005)Google Scholar
  13. 13.
    Jackson, M.: Problem Frames: Analysing & Structuring Software Development Problems. Addison-Wesley, Reading (2001)Google Scholar
  14. 14.
    Kemerer, C.F., Slaughter, S.: An empirical approach to studying software evolution. TSE 25(4), 493–509 (1999)Google Scholar
  15. 15.
    Lam, W., Loomes, M.: Requirements evolution in the midst of environmental change: a managed approach. In: CSMR 1998 (1998)Google Scholar
  16. 16.
    LaMantia, M., Cai, Y., MacCormack, A., Rusnak, J.: Analyzing the evolution of large-scale software systems using design structure matrices and design rule theory: Two exploratory cases. In: Proc. of WICSA 2008, pp. 83–92 (2008)Google Scholar
  17. 17.
    Lehman, M.: On understanding laws, evolution and conservation in the large program life cycle. J. of Sys. and Soft. 1(3), 213–221 (1980)Google Scholar
  18. 18.
    Lehman, M.: Programs, life cycles, and laws of software evolution. Proc. IEEE 68(9), 1060–1076 (1980)Google Scholar
  19. 19.
    Lin, L., Prowell, S., Poore, J.: The impact of requirements changes on specifications and state machines. SPE 39(6), 573–610 (2009)Google Scholar
  20. 20.
    Liu, L., Eric Yu, E.: Designing information systems in social context: A goal and scenario modelling approach. Info. Syst. 29, 187–203 (2003)CrossRefGoogle Scholar
  21. 21.
    Lormans, M., van Dijk, H., van Deursen, A., Nocker, E., de Zeeuw, A.: Managing evolving requirements in an outsourcing context: an industrial experience report. In: IWPSE 2004, pp. 149–158 (2004)Google Scholar
  22. 22.
    Mens, T., Ramil, J., Godfrey, M.: Analyzing the evolution of large-scale software. J. of Soft. Maintenance and Evolution: Research and Practice 16(6), 363–365 (2004)CrossRefGoogle Scholar
  23. 23.
    Program SWIM-SUIT. D1.5.1 Overall SWIM users requirements. Tech. report, 2008.Google Scholar
  24. 24.
    Project PROTEUS. Deliverable 1.3: Meeting the challenge of chainging requirements. Tech. report, Centre for Soft. Reliab., Univ. of Newcastle upon Tyne (1996)Google Scholar
  25. 25.
    Ravichandar, R., Arthur, J., Bohner, S., Tegarden, D.: Improving change tolerance through capabilities-based design: an empirical analysis. J. of Soft. Maintenance and Evolution: Research and Practice 20(2), 135–170 (2008)CrossRefGoogle Scholar
  26. 26.
    Russo, A., Nuseibeh, B., Kramer, J.: Restructuring requirements specifications. IEEE Proceedings: Software 146, 44–53 (1999)CrossRefGoogle Scholar
  27. 27.
    Shafer, G., Vovk, V., Chychyla, R.: How to base probability theory on perfect-information games. BEATCS 100, 115–148 (2010)MathSciNetzbMATHGoogle Scholar
  28. 28.
    Soffer, P.: Scope analysis: identifying the impact of changes in business process models. J. of Soft. Process: Improvement and Practice 10(4), 393–402 (2005)MathSciNetCrossRefGoogle Scholar
  29. 29.
    Stark, G., Oman, P., Skillicorn, A., Ameele, A.: An examination of the effects of requirements changes on software maintenance releases. J. of Soft. Maintenance: Research and Practice, 293–309 (1999)Google Scholar
  30. 30.
    Zave, P., Jackson, M.: Four dark corners of req. eng. TSEM 6(1), 1–30 (1997)Google Scholar
  31. 31.
    Zowghi, D., Offen, R.: A logical framework for modeling and reasoning about the evolution of requirements. In: ICRE 1997 (1997)Google Scholar

Copyright information

© Springer-Verlag Berlin Heidelberg 2011

Authors and Affiliations

  • Le Minh Sang Tran
    • 1
  • Fabio Massacci
    • 1
  1. 1.Università degli Studi di TrentoTrentoItaly

Personalised recommendations