Dealing with known unknowns: Towards a game-theoretic foundation for software requirement evolution

L.M.S. Tran, F. Massacci

Research output: Chapter in Book / Report / Conference proceedingConference contributionAcademicpeer-review

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). © 2011 Springer-Verlag.
Original languageEnglish
Title of host publicationAdvanced Information Systems Engineering - 23rd International Conference, CAiSE 2011, Proceedings
Pages62-76
DOIs
Publication statusPublished - 2011
Externally publishedYes
Event23rd International Conference on Advanced Information Systems Engineering, CAiSE 2011 - , United Kingdom
Duration: 20 Jun 201124 Jun 2011

Publication series

NameLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
ISSN (Print)0302-9743
ISSN (Electronic)1611-3349

Conference

Conference23rd International Conference on Advanced Information Systems Engineering, CAiSE 2011
Country/TerritoryUnited Kingdom
Period20/06/1124/06/11

Fingerprint

Dive into the research topics of 'Dealing with known unknowns: Towards a game-theoretic foundation for software requirement evolution'. Together they form a unique fingerprint.

Cite this