(Created page with " == 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 fu...") |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 2: | Line 2: | ||
== Abstract == | == 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. | + | 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). |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| Line 15: | Line 10: | ||
* [https://link.springer.com/content/pdf/10.1007%2F978-3-642-21640-4_7.pdf https://link.springer.com/content/pdf/10.1007%2F978-3-642-21640-4_7.pdf] | * [https://link.springer.com/content/pdf/10.1007%2F978-3-642-21640-4_7.pdf https://link.springer.com/content/pdf/10.1007%2F978-3-642-21640-4_7.pdf] | ||
| + | |||
| + | * [http://link.springer.com/content/pdf/10.1007/978-3-642-21640-4_7 http://link.springer.com/content/pdf/10.1007/978-3-642-21640-4_7], | ||
| + | : [http://dx.doi.org/10.1007/978-3-642-21640-4_7 http://dx.doi.org/10.1007/978-3-642-21640-4_7] under the license http://www.springer.com/tdm | ||
| + | |||
| + | * [http://securitylab.disi.unitn.it/lib/exe/fetch.php?media=research_activities:security_requirements_engineering:forcaise-camera.pdf http://securitylab.disi.unitn.it/lib/exe/fetch.php?media=research_activities:security_requirements_engineering:forcaise-camera.pdf], | ||
| + | : [https://link.springer.com/chapter/10.1007%2F978-3-642-21640-4_7 https://link.springer.com/chapter/10.1007%2F978-3-642-21640-4_7], | ||
| + | : [https://www.scipedia.com/public/Tran_Massacci_2011a https://www.scipedia.com/public/Tran_Massacci_2011a], | ||
| + | : [https://dblp.uni-trier.de/db/conf/caise/caise2011.html#TranM11 https://dblp.uni-trier.de/db/conf/caise/caise2011.html#TranM11], | ||
| + | : [https://rd.springer.com/chapter/10.1007%2F978-3-642-21640-4_7 https://rd.springer.com/chapter/10.1007%2F978-3-642-21640-4_7], | ||
| + | : [https://doi.org/10.1007/978-3-642-21640-4_7 https://doi.org/10.1007/978-3-642-21640-4_7], | ||
| + | : [https://academic.microsoft.com/#/detail/200306908 https://academic.microsoft.com/#/detail/200306908] | ||
Latest revision as of 17:00, 21 January 2021
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).
Original document
The different versions of the original document can be found in:
- http://dx.doi.org/10.1007/978-3-642-21640-4_7 under the license http://www.springer.com/tdm
- https://link.springer.com/chapter/10.1007%2F978-3-642-21640-4_7,
- https://www.scipedia.com/public/Tran_Massacci_2011a,
- https://dblp.uni-trier.de/db/conf/caise/caise2011.html#TranM11,
- https://rd.springer.com/chapter/10.1007%2F978-3-642-21640-4_7,
- https://doi.org/10.1007/978-3-642-21640-4_7,
- https://academic.microsoft.com/#/detail/200306908
Document information
Published on 01/01/2011
Volume 2011, 2011
DOI: 10.1007/978-3-642-21640-4_7
Licence: CC BY-NC-SA license
Share this document
Keywords
claim authorship
Are you one of the authors of this document?