Software testing techniques (2nd ed.)
Software testing techniques (2nd ed.)
Change impact analysis for object-oriented programs
PASTE '01 Proceedings of the 2001 ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Change impact analysis for aspect-oriented software evolution
Proceedings of the International Workshop on Principles of Software Evolution
Change Impact Identification in Object Oriented Software Maintenance
ICSM '94 Proceedings of the International Conference on Software Maintenance
Algorithmic Analysis of the Impacts of Changes to Object-Oriented Software
TOOLS '00 Proceedings of the Technology of Object-Oriented Languages and Systems (TOOLS 34'00)
Impact Analysis of Weaving in Aspect-Oriented Programming
ICSM '05 Proceedings of the 21st IEEE International Conference on Software Maintenance
Hi-index | 0.01 |
When object-oriented programs evolve to aspect-oriented programs (AOP), the behavior of the evolved programs can become complex and hard to understand because the aspects woven into object-oriented programs can change the original behavior of the programs in an unintended way. To ensure that no additional errors are introduced by the aspects, it is critical to retest the evolved aspect-oriented programs. The testing efforts can be significantly reduced if only the parts of the object-oriented program affected by the changes are retested. In this paper we propose a method to analyze the possible change impacts caused by woven aspects. The types of changes introduced by aspects are identified and specified. The likely impacts caused by the changes are described and computed based on various dependency relations in object-oriented programs. In particular, the influences of pointcut declarations on the locations of changes and ripple effects are addressed. An example is presented to illustrate the usefulness of the proposed method.