Regression testing involves testing not only the functionality containing a defect but also testing related functionality to check if a change has introduce side effects. In order to check for the above, a change impact model has been developed using the artifacts built for the software during the design phase. Using both static and dynamic diagrams of UML, it is possible to understand the effect of a change. Also, this serves as a mechanism to ensure customer requirements are satisfied. In this paper, a fine-grained assessment of system change is given at the activity, class and functionality(ie. use case) level using design models. When a defect is notified, first the activity or method containing the defect is identified. The impact of the defect on other methods is calculated and risk level assigned. Further, the same is used to calculate risk level at the class level and then at the use case level. An indication of the level of risk the method, class and use case incurs due to the change is indicated aiding in selection of regression tests.

1. OMG. Unified modeling language (UML) Superstructure Specification, version 2. 1. Technical report.
2. Robert V. Binder. Testing Object-Oriented Systems Models, Patterns, and Tools. Addison Wesley, 1999.
3. L. Briand and Y. Labiche. A UML-based approach to system testing. Software Systems Modeling, 1(1), 2002.
4. L. C. Briand, Y. Labiche, G. Soccar. Automating Impact Analysis and Regression Test Selection based on UML Designs. Proceedings of the International Conference on Software Maintenance (ICSM '02), IEEE Computer Soceity, pp. 1-10, 2002.
5. M. J. Harrold, J. A. Jones, T. Li, D. Liang, A. Orso, M. Pennings, S. Sinha and S. A. Spoon, Regression Test Selection for Java Software, Proc. ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA'01), 2001.
6. Abdi, M. K. ; Lounis, H. ; Sahraoui, H. , "Predicting Change Impact in Object-Oriented Applications with Bayesian Networks," Computer Software and Applications Conference, 2009. COMPSAC '09. 33rd Annual IEEE International , vol. 1, no. , pp. 234,239, 20-24 July 2009.
7. M. K. Abdi, H. Lounis, H. Sahraoui: "Analyzing Change Impact in Object-Oriented Systems " In proceedings of the 32nd EUROMICRO Software Engineering and Advanced Applications Conference, Cavtat/Dubrovnik (Croatia), August 29-Sept 1, 2006.
8. Lee, M. ; Offutt, A. J. ; Alexander, R. T. , "Algorithmic analysis of the impacts of changes to object-oriented software," Proceedings. 34th International Conference on Technology of Object-Oriented Languages and Systems, 2000. TOOLS Vol. 34, pp. 61-70, 2000.
9. J. Buckner, J. Buchta, M. Petrenko, and V. Rajlich, JRipples: A tool for program comprehension during incremental change, in Proceedings of the 13th International Workshop on Program Comprehension (IWPC 05), pp. 149151, May 2005.
10. M. Hammad, M. L. Collard, and J. I. Maletic, Automatically identifying changes that impact code-to-design traceability, in Proceedings of the IEEE 17th International Conference on Program Comprehension (ICPC 09), Vancouver, BC, pp. 2029, May 2009.
11. Baradhi, G. , Mansour, N. , "A Comparative Study of Five Regression Testing Algorithms," Proceedings of the IEEE Australian Software Engineering Conference, pp. 174-182, 1997.
12. Beydeda, S. , Gruhn, V. , "An Integrated Testing Technique for Component-Based Software," Proceedings of the ACS/IEEE Computer Systems and Applications International Conference, pp. 328 -334, 2001.
13. Gupta, R. , Harrold, M. , Soffa, M. , "An Approach to Regression Testing Using Slices," Proceedings of the IEEE International Conference on Software Maintenance, pp. 299-308, 1992.
14. Harrold, M. , Soffa, M. , "An Incremental Approach to Unit Testing During Maintenance," Proceedings of the IEEE International Conference on Software Maintenance, pp. 362-367, 1988.

Regression Testing Uml Change Impact Model Risk Ripple Effect