It has been well accepted by the software professionals as well as researchers that software systems have to evolve themselves to survive successfully. Software evolution is a crucial activity for software organizations. Software complexity has existed as an important issue ever since the software programs came into existence. Thus, it becomes necessary to visualize and analyze the complexity of requested change before implementation. The goal of this paper is to identify the software complexity after change. The complexity will be used in taking decision about approval or rejection of the requested change, estimating effort for implementing change, estimating effort required in regression testing predicting number of possible faults. We have applied our proposed approach on four case studies. These case studies show some evidence that our approach is reasonably efficient and precise as well as being practical for software change management.

1. Jim Buckley, Tom Mens, Matthias Zenger, Awais Rashid, and Gunter Kniesel. 2005. Towards a taxonomy of software change: Research Articles. J. Softw. Maint. Evol. 17, 5 (September 2005), 309-332.
2. Lefteris Angelis, and Claes Wohlin. 2008. An Empirical Study on Views of Importance of Change Impact Analysis Issues. IEEE Trans. Softw. Eng. 34, 4 (July 2008), 516-530.
3. R. S. Arnold and S. A. Bohner, "Impact Analysis - Towards A Framework for Comparison," Proceedings of the Conference on Software Maintenance, Los Alamitos, CA, September 1993, pp. 292-301
4. Malcom Gethers, Huzefa Kagdi, Bogdan Dit, and Denys Poshyvanyk. , "An adaptive approach to impact analysis from change requests to source code", In Proceedings of the 26th IEEE/ACM International Conference on Automated Software Engineering (ASE '11), IEEE Computer Society, Washington, DC, USA, pp. 540-543, 2011
5. Pfleeger, S. L. and J. M. Atlee (2006). " Software Engineering Theory and Practice Upper Saddle River", New Jersey, USA, Prentice Hall
6. R. D. Banker, S. M. Datar, and D. Zweig. 1989. Software complexity and maintainability. In Proceedings of the tenth international conference on Information Systems (ICIS '89), Janice I. DeGross, John C. Henderson, and Benn R. Konsynski (Eds. ). ACM, New York, NY, USA, 247-255.
7. Ahmed E. Hassan. 2009. Predicting faults using the complexity of code changes. In Proceedings of the 31st International Conference on Software Engineering (ICSE '09). IEEE Computer Society, Washington, DC, USA, 78-88
8. Thomas J Mc Cabe, A Complexity Measure, IEEE Transactions on Software Engineering, Vol. , SE-2, No. 4, December 1976
9. K. Reddy Reddy and A. Ananda Rao. 2009. Dependency oriented complexity metrics to detect rippling related design defects. SIGSOFT Softw. Eng. Notes 34, 4 (July 2009), 1-7.
10. Chidamber, S. R. and Kemerer, C. K. Towards a Metrics Suite for Object Oriented Design. Proceedings of 6th ACM Conference on Object Oriented Programming, Systems, Languages and Applications (OOPSLA'91), (Phoenix, Arizona, 1991), 197-211.
11. Chidamber, S. R. and Kemerer, C. K. A Metrics Suite for Object Oriented Design. IEEE Transactions on Software Engineering, Vol. 20 (June 1994), pp. 476-493.
12. Li, W. and Henry, S. Object-Oriented metrics that predict maintainability. Journal of Systems and Software. 23(2) 1993 111- 122.

Software Change Management Cohesion Coupling And Software Change Complexity