Mining Version Histories to Guide Software Changes
IEEE Transactions on Software Engineering
Mining Aspects from Version History
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
JDiff: A differencing technique and tool for object-oriented programs
Automated Software Engineering
Change Distilling: Tree Differencing for Fine-Grained Source Code Change Extraction
IEEE Transactions on Software Engineering
Recommending adaptive changes for framework evolution
Proceedings of the 30th international conference on Software engineering
Reusing Program Investigation Knowledge for Code Understanding
ICPC '08 Proceedings of the 2008 The 16th IEEE International Conference on Program Comprehension
Retrieving Task-Related Clusters from Change History
WCRE '08 Proceedings of the 2008 15th Working Conference on Reverse Engineering
Enabling static analysis for partial java programs
Proceedings of the 23rd ACM SIGPLAN conference on Object-oriented programming systems languages and applications
Recommending method invocation context changes
Proceedings of the 2008 international workshop on Recommendation systems for software engineering
A multi-view API impact analysis for open SPL platform
ICACT'10 Proceedings of the 12th international conference on Advanced communication technology
Recommending Adaptive Changes for Framework Evolution
ACM Transactions on Software Engineering and Methodology (TOSEM)
Assessing modularity via usage changes
Proceedings of the 10th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools
How do software engineers understand code changes?: an exploratory study in industry
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
| Hi-index | 0.00 |
As a framework evolves, changes in its Application Programming Interface (API) can break client programs that extend the framework. Repairing a client program can be a challenging task because developers need to understand the context surrounding the API change. This paper describes SemDiff, a tool that recommends replacements for framework methods that were accessed by a client program and deleted during the evolution of the framework. SemDiff recommends replacements for non-trivial changes undiscovered by other change-detection techniques and also enables developers to look at the context of the changes that led to the deletion of a framework method.