Abstract
Today, when constructing a new software system, many developers build their systems on top of frameworks. Eclipse framework is one such popular and widely adopted framework that has been evolving for over a decade. Like many other evolving software systems, the Eclipse SDK framework has both stable and supported APIs (good interfaces) and unstable, discouraged and unsupported non-APIs (bad interfaces). However, despite being discouraged by Eclipse, in our experience, the usage of bad interfaces is not uncommon. In this thesis, by means of a series of empirical studies, we quantify/qualify some the challenges faced by Eclipse third-party plug-in developers in using the interfaces provided by the Eclipse SDK framework. Furthermore, we propose solutions to the identified challenges, like changes in development strategy to both interface providers and interface users. In particular, the lessons learned from this study can provide valuable information in particular to the interface providers, i.e., Eclipse SDK developers, and the interface uses, i.e., ETP developers, in co-evolving the Eclipse framework. In general, the lessons learned can be transferable to other framework ecosystem.
| Original language | English |
|---|---|
| Title of host publication | Proceedings of the 17th European Conference on Software Maintenance and Reengineering (CSMR, Genova, Italy, March 5-8, 2013) |
| Publisher | Institute of Electrical and Electronics Engineers |
| Pages | 427-430 |
| ISBN (Print) | 978-1-4673-5833-0 |
| DOIs | |
| Publication status | Published - 2013 |