IEEE Transactions on Software Engineering
Impact Analysis - Towards a Framework for Comparison
ICSM '93 Proceedings of the Conference on Software Maintenance
An Empirical Comparison of Dynamic Impact Analysis Algorithms
Proceedings of the 26th International Conference on Software Engineering
A Cost Model for Software Maintenance & Evolution
ICSM '04 Proceedings of the 20th IEEE International Conference on Software Maintenance
Impact Analysis by Mining Software and Change Request Repositories
METRICS '05 Proceedings of the 11th IEEE International Software Metrics Symposium
Using dependency models to manage complex software architecture
OOPSLA '05 Proceedings of the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications
Jimpa: An Eclipse Plug-in for Impact Analysis
CSMR '06 Proceedings of the Conference on Software Maintenance and Reengineering
Managing the Complexity of Large Free and Open Source Package-Based Software Distributions
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Proceedings of the 2007 international ACM conference on Supporting group work
Continuous integration: improving software quality and reducing risk
Continuous integration: improving software quality and reducing risk
Modeling continuous integration practice differences in industry software development
Journal of Systems and Software
Hi-index | 0.00 |
Automated testing and continuous integration are established concepts in today’s software engineering landscape, but they work in a kind of isolated environment as they do not fully take into consideration the complexity of dependencies between code artifacts in different projects. In this paper, we demonstrate the Continuous Change Impact Analysis Process (CCIP) that breaks up the isolation by actively taking into account project dependencies. The implemented CCIP approach extends the traditional continuous integration (CI) process by enforcing communication between CI servers whenever new artifact updates are available. We show that the exchange of CI process results contribute to improving effectiveness of automated testing.