Information Technology Reference
In-Depth Information
the problem of inconsistencies due to requirement evolution. This approach is
supported by automated tools [10]. Also relating to inconsistencies, Fabrinni et
al [6] deal with requirement evolution expressed in natural language, which is
challenging to capture precisely requirement changes. Their approach employs
formal concept analysis to enable a systematic and precise verification of consis-
tency among different stages, hence, controls requirement evolution.
Other notable approaches include Brier et al.'s [3] to capture, analyze, and
understand how software systems adapt to changing requirements in an organiza-
tional context; Felici et al [8] concern with the nature of requirements evolving in
the early phase of systems; Stark et al [29] study the information on how change
occurs in the software system and attempt to produce a prediction model of
changes; Lormans et al [21] use a formal requirement management system to
motivate a more structural approach to requirement evolution.
8Conluon
We have discussed a rule-based representation of evolutions on requirement mod-
els. We proposed game-theoretic approach to explain the uncertainty of evolu-
tions. We also introduced two notions of max belief and residual risk to reason
on evolutionary models, in which the higher max belief and lower residual risk
models seem to be more evolution-resilient than others. Together with other
analyses (
e.g.,
cost, risk), these values can help designers in making decision.
During the discussion, we provided many examples taken from a real world
project, SWIM. These examples not only help to explain better our idea, but
also show the promising applicability of our approach.
For future work, we plan to instantiate our approach to a concrete modeling
language (
e.g.,
goal-based language) and apply to a more convincing case study.
We shall interact with stakeholder and designers, show them our approach and
get their feedback to validate the usability of proposed approach.
References
1. Anderson, C.: The long tail. Wired (October 2004)
2. Anton, A., Potts, C.: Functional paleontology: The evolution of user-visible system
services. TSE 29(2), 151-166 (2003)
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)
4. d'Avila Garcez, A., Russo, A., Nuseibeh, B., Kramer, J.: Combining abductive
reasoning and inductive learning to evolve requirements specifications. IEEE Pro-
ceedings - Software 150(1), 25-38 (2003)
5. Elberse, A.: Should you invest in the long tail? Harvard Business Review (2008)
6. Fabbrini, F., Fusani, M., Gnesi, S., Lami, G.: Controlling requirements evolution:
a formal concept analysis-based approach. In: ICSEA 2007 (2007)
7. FAA. System wide information management (SWIM) segment 2 technical review.
Tech. report (2009)
8. Felici, M.: Observational Models of Requirements Evolution. PhD thesis (2004)
