PLDI '90 Proceedings of the ACM SIGPLAN 1990 conference on Programming language design and implementation
ICSE '94 Proceedings of the 16th international conference on Software engineering
Predicting Fault Incidence Using Software Change History
IEEE Transactions on Software Engineering
Programmers use slices when debugging
Communications of the ACM
Software Change Impact Analysis
Software Change Impact Analysis
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Isolating cause-effect chains from computer programs
Proceedings of the 10th ACM SIGSOFT symposium on Foundations of software engineering
CCFinder: a multilinguistic token-based code clone detection system for large scale source code
IEEE Transactions on Software Engineering
A Model for Change Propagation Based on Graph Rewriting
ICSM '97 Proceedings of the International Conference on Software Maintenance
Impact Analysis - Towards a Framework for Comparison
ICSM '93 Proceedings of the Conference on Software Maintenance
Hipikat: recommending pertinent software development artifacts
Proceedings of the 25th International Conference on Software Engineering
ICSE '81 Proceedings of the 5th international conference on Software engineering
CVSSearch: Searching through Source Code using CVS Comments
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Identifying Reasons for Software Changes Using Historic Databases
ICSM '00 Proceedings of the International Conference on Software Maintenance (ICSM'00)
A Large-Scale Empirical Study of Forward and Backward Static Slice Size and Context Sensitivity
ICSM '03 Proceedings of the International Conference on Software Maintenance
Using Development History Sticky Notes to Understand Software Architecture
IWPC '04 Proceedings of the 12th IEEE International Workshop on Program Comprehension
Using Origin Analysis to Detect Merging and Splitting of Source Code Entities
IEEE Transactions on Software Engineering
Locating causes of program failures
Proceedings of the 27th international conference on Software engineering
HATARI: raising risk awareness
Proceedings of the 10th European software engineering conference held jointly with 13th ACM SIGSOFT international symposium on Foundations of software engineering
A study of the contributors of PostgreSQL
Proceedings of the 2006 international workshop on Mining software repositories
Automatic Identification of Bug-Introducing Changes
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
Identifying Refactorings from Source-Code Changes
ASE '06 Proceedings of the 21st IEEE/ACM International Conference on Automated Software Engineering
An empirical study of static program slice size
ACM Transactions on Software Engineering and Methodology (TOSEM)
A study of effectiveness of dynamic slicing in locating real faults
Empirical Software Engineering
Automatic Inference of Structural Changes for Matching across Program Versions
ICSE '07 Proceedings of the 29th international conference on Software Engineering
Empirical study of optimization techniques for massive slicing
ACM Transactions on Programming Languages and Systems (TOPLAS)
Change Distilling: Tree Differencing for Fine-Grained Source Code Change Extraction
IEEE Transactions on Software Engineering
Visualizing Software Architecture Evolution Using Change-Sets
WCRE '07 Proceedings of the 14th Working Conference on Reverse Engineering
Capturing the long-term impact of changes
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 2
Comparison of different impact analysis methods and programmer's opinion: an empirical study
Proceedings of the 8th International Conference on the Principles and Practice of Programming in Java
Controversy Corner: Preserving knowledge in software projects
Journal of Systems and Software
Visualizing protected variations in evolving software designs
Journal of Systems and Software
Hi-index | 0.00 |
The source code of a software system is in constant change. The impact of these changes spreads out across the software system and may lead to the sudden manifestation of failures in unchanged parts. To help developers fix such failures, we propose a method that, in a pre-processing stage, analyzes prior code changes to determine what functions have been modified. Next, given a particular period of time in the past, the functions changed during that period are propagated throughout the rest of the system using the dependence graph of the system. This information is visualized using Change Impact Graphs (CIGs). Through a case study based on the Apache Web Server, we demonstrate the benefit of using CIGs to investigate several real defects.