Practical change impact analysis based on static program slicing for industrial software systems

Authors:
Mithun Acharya;Brian Robinson
Affiliations:
ABB Corporate Research, Raleigh NC;ABB Corporate Research, Raleigh NC
Venue:
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
Year:
2012

Citing 3
Cited 0

Interprocedural slicing using dependence graphs

ACM Transactions on Programming Languages and Systems (TOPLAS)
An empirical study of static program slice size

ACM Transactions on Software Engineering and Methodology (TOSEM)
Practical change impact analysis based on static program slicing for industrial software systems

Proceedings of the 33rd International Conference on Software Engineering

Quantified Score

Hi-index	0.00

Visualization

Abstract

Change impact analysis, i.e., knowing the potential consequences of a software change, is critical for the risk analysis, developer effort estimation, and regression testing of evolving software. Static program slicing is an attractive option for enabling routine change impact analysis for newly committed changesets during daily software build. However, static program slicing faces accuracy and scalability problems when applied routinely on large and evolving industrial software systems. In this paper, we present a tool called Imp, used within ABB, to address these problems. Imp transparently integrates with the version control and the daily build environments and is also available as a Visual Studio plugin for quick what-if analysis by developers for potential changes in software written in C/C++.