Introducing changes in the software during development and post-development is a very frequent activity. Reasons for changes include client's changing requirements, fixing leftover bugs and other security issues, adding new functionality, and so on. Introducing changes in software may bring adverse effects that may degrade its quality or introduce new bugs which in turn will increase the software maintenance cost. Therefore a systematic change management process is required. A systematic process for managing software changes is already in place i.e. Change Impact Analysis (CIA). The current book conducts a systematic study of recent developments, techniques, and tools in the area of CIA