Quality Validation of Software Design before Change Implementation
Change in any software application seems to be very simple when someone demands it, but the complexity of the task appears during implementation phase. Change implementation is acceptable when it includes the requested functionality as well as improves and preserves the quality of software. Complexity is an important issue for software development as it affects the cost, effort and quality of the product. Change complexity could be helpful in analyzing the impact of change. This paper focuses on measuring the software complexity that analyzes the quality of software design. To measure the complexity, UML class diagram is considered. Additionally, the goal of this paper is to identify the best possible design among various possible solutions to implement requested change in the existing system that does not adversely affects the software design of the existing software. Here, the change type considered is only new requests made by user or client.
KeywordsSoftware change management cohesion coupling complexity and software quality
Unable to display preview. Download preview PDF.
- 3.Arnold, R.S., Bohner, S.A.: Impact Analysis - Towards A Framework for Comparison. In: Proceedings of the Conference on Software Maintenance, Los Alamitos, CA, pp. 292–301 (September 1993)Google Scholar
- 4.Gethers, M., Kagdi, H., Dit, B., Poshyvanyk, D.: 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 2011), pp. 540–543. IEEE Computer Society, Washington, DC (2011)Google Scholar
- 5.Pfleeger, S.L., Atlee, J.M.: Software Engineering Theory and Practice Upper Saddle River. Prentice-Hall, New Jersey (2006)Google Scholar
- 7.Hassan, A.E.: Predicting faults using the complexity of code changes. In: Proceedings of the 31st International Conference on Software Engineering (ICSE 2009), pp. 78–88. IEEE Computer Society, Washington, DC (2009)Google Scholar
- 8.McCabe, T.J.: A Complexity Measure. IEEE Transactions on Software Engineering SE-2(4) (December 1976)Google Scholar
- 10.Chidamber, S.R., Kemerer, C.K.: Towards a Metrics Suite for Object Oriented Design. In: Proceedings of 6th ACM Conference on Object Oriented Programming, Systems, Languages and Applications (OOPSLA 1991), Phoenix, Arizona, pp. 197–211 (1991)Google Scholar
- 12.Ghosh, S.M., Sharma, H.R., Mohabay, V.: Analysis and Modeling of Change Management Process Model. International Journal of Software Engineering and Its Applications 5(2) (April 2011)Google Scholar
- 13.Olsen, N.: The software rush hour. IEEE Software Magazine, 29–37 (September 1993)Google Scholar