Design of Change Impact Analysis Model for Object Oriented Software

Abstract

newlineChanges in software are necessary for its shelf life and evolution. However, it demands huge newlineinvestments in terms of time and efforts to understand and analyze various software artifacts and newlinetheir relationships. The changes in software may occur when software is under development as newlinewell as post its delivery to client. In implementation of changes it is essential to ensure that the newlinesoftware remains in a consistent state even after making modifications as per change request. These newlinemodifications can be the result of the updated requirements from client, transfer of software to newlinedifferent platform, introduction of some new features in the software and so on. Any change in newlineone part of the software may cause changes in other related parts of the software, which, if not newlinehandled properly, may have serious consequences. Therefore, there is a need of a systematic newlineprocess of change management. Formally, such a process is referred as Change Impact Analysis newline(CIA). Various definitions of CIA exist in literature, but the most popular definition explains CIA newlineas a process of identifying the potential consequences of a change or estimate what needs to be newlinemodified to accomplish a change . To implement CIA process majorly three CIA approaches- newlineTraceability based CIA, Dependency based CIA and Experiential based CIA, are available in newlineliterature.