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.

-- DanielAmyot - 03 Aug 2006


  • Please feel free to discuss this article directly on this page. Constructive comments are welcomed! Please sign your TWiki name.

FormForVirtualLibrary edit

Title Change Impact Analysis for Requirement Evolution using Use Case Maps
Authors J. Hassine, J. Rilling, J.Hewitt, and R. Dssouli
Type Conference
Conference/Journal Title 8th International Workshop on Principles of Software Evolution (IWPSE 2005)
Publisher IEEE CS Press
Month September
Year 2005
Pages 81-90
DOI 10.1109/IWPSE.2005.8
Keywords Dependency Analysis, Impact Analysis, Requirements Evolution, Slicing, Use Case Map
Topic attachments
I Attachment Action Size Date Who Comment
Iwpse05CiaUcm.pdfpdf Iwpse05CiaUcm.pdf manage 289 K 03 Aug 2006 - 14:40 DanielAmyot Pre-publication paper
Topic revision: r2 - 12 Nov 2009, SaeedBehnam
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback