Automatically generating refactorings to support API evolution
PASTE '05 Proceedings of the 6th ACM SIGPLAN-SIGSOFT workshop on Program analysis for software tools and engineering
Informing Eclipse API production and consumption
Proceedings of the 2007 OOPSLA workshop on eclipse technology eXchange
SpotWeb: detecting framework hotspots via mining open source repositories on the web
Proceedings of the 2008 international working conference on Mining software repositories
Mining usage expertise from version archives
Proceedings of the 2008 international working conference on Mining software repositories
Mining trends of library usage
Proceedings of the joint international and annual ERCIM workshops on Principles of software evolution (IWPSE) and software evolution (Evol) workshops
MAPO: Mining and Recommending API Usage Patterns
Genoa Proceedings of the 23rd European Conference on ECOOP 2009 --- Object-Oriented Programming
Temporal analysis of API usage concepts
Proceedings of the 34th International Conference on Software Engineering
Hi-index | 0.00 |
When designing a piece of software, one frequently must choose between multiple external libraries that provide similar services. Which library is the best one to use? We mined hundreds of open source projects and their external dependencies in order to observe the popularity of their APIs and to give recommendations of the kind: "Projects are moving away from this API element. Consider a change." Such wisdom of the crowds can provide valuable information to both the API users and the API producers.