Change impact analysis for requirement evolution using use case maps

Changing customer needs and computer technology are the driving factors influencing software evolution. There is a need to assess the impact of these changes on existing software systems. Requirement specification is gaining increasingly attention as a critical phase of software systems development process. In particular for larger systems, it quickly becomes difficult to comprehend what impact a requirement change might have on the overall system or parts of the system. Thus, the development of techniques and tools to support the evolution of requirement specifications becomes an important issue. In this paper we present a novel approach to change impact analysis at the requirement level. We apply both slicing and dependency analysis at the use case map specification level to identify the potential impact of requirement changes on the overall system. We illustrate our approach and its applicability with a case study conducted on a simple telephony system.

[1]  Jun Gu,et al.  Algorithms for the satisfiability (SAT) problem: A survey , 1996, Satisfiability Problem: Theory and Applications.

[2]  David W. Binkley,et al.  A large-scale empirical study of forward and backward static slice size and context sensitivity , 2003, International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings..

[3]  Daniel Amyot,et al.  Use case maps for the capture and validation of distributed systems requirements , 1999, Proceedings IEEE International Symposium on Requirements Engineering (Cat. No.PR00188).

[4]  Mikael Lindvall,et al.  How well do experienced software developers predict software change? , 1998, J. Syst. Softw..

[5]  Lois M. L. Delcambre,et al.  Change cases: use cases that identify future requirements , 1996, OOPSLA '96.

[6]  Shawn A. Bohner,et al.  Impact analysis-Towards a framework for comparison , 1993, 1993 Conference on Software Maintenance.

[7]  Jameleddine Hassine,et al.  Feature Interaction Filtering with Use Case Maps at Requirements Stage , 2000, FIW.

[8]  Li Li,et al.  Algorithmic analysis of the impact of changes to object-oriented software , 1996, 1996 Proceedings of International Conference on Software Maintenance.

[9]  Antje von Knethen.  A trace model for system requirements changes on embedded systems , 2001, IWPSE '01.

[10]  Jameleddine Hassine,et al.  Applying Reduction Techniques to Software Functional Requirement Specifications , 2004, SAM.

[11]  Lionel C. Briand,et al.  Impact analysis and change management of UML models , 2003, International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings..

[12]  David W. Binkley,et al.  Program slicing , 2008, 2008 Frontiers of Software Maintenance.

[13]  Gregg Rothermel,et al.  Whole program path-based dynamic impact analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[14]  S.A. Bohner,et al.  Software change impacts-an evolving perspective , 2002, International Conference on Software Maintenance, 2002. Proceedings..

[15]  Joseph Robert Horgan,et al.  Dynamic program slicing , 1990, PLDI '90.

[16]  Daniel Amyot,et al.  Deriving Message Sequence Charts from Use Case Maps Scenario Specifications , 2001, SDL Forum.

[17]  Raymond A. Paul,et al.  Scenario-based modeling and its applications , 2002, Proceedings of the Seventh IEEE International Workshop on Object-Oriented Real-Time Dependable Systems. (WORDS 2002).

[18]  Paolo Tonella,et al.  Using a Concept Lattice of Decomposition Slices for Program Understanding and Impact Analysis , 2003, IEEE Trans. Software Eng..

[19]  Frank Tip,et al.  Change impact analysis for object-oriented programs , 2001, PASTE '01.

[20]  M. R. Strens,et al.  Change analysis: a step towards meeting the challenge of changing requirements , 1996, Proceedings IEEE Symposium and Workshop on Engineering of Computer-Based Systems.

[21]  Tarak Goradia.  Dynamic impact analysis: a cost-effective technique to enforce error-propagation , 1993, ISSTA '93.

[22]  Meir M. Lehman,et al.  Evolution in software and related areas , 2001, IWPSE '01.

[23]  Robert S. Arnold,et al.  Software Change Impact Analysis , 1996 .

[24]  Lori A. Clarke,et al.  A Formal Model of Program Dependences and Its Implications for Software Testing, Debugging, and Maintenance , 1990, IEEE Trans. Software Eng..

[25]  Raymond A. Paul,et al.  Scenario-based functional regression testing , 2001, 25th Annual International Computer Software and Applications Conference. COMPSAC 2001.

[26]  Will Venters,et al.  Software engineering: theory and practice , 2006 .

[27]  Raffaella Settimi,et al.  Supporting software evolution through dynamically retrieving traces to UML artifacts , 2004, Proceedings. 7th International Workshop on Principles of Software Evolution, 2004..