Not logged in.
Quick Search - Contribution
Contribution Details
| Type | Conference or Workshop Paper |
| Scope | Discipline-based scholarship |
| Published in Proceedings | Yes |
| Title | Why are Features Deprecated? An Investigation Into the Motivation Behind Deprecation |
| Organization Unit | |
| Authors |
|
| Presentation Type | paper |
| Item Subtype | Original Work |
| Refereed | Yes |
| Status | Published in final form |
| Language |
|
| ISBN | 978-1-5386-7870-1 |
| Page Range | 13 - 24 |
| Event Title | 2018 IEEE International Conference on Software Maintenance and Evolution (ICSME) |
| Event Type | conference |
| Event Location | Madrid |
| Event Start Date | October 23 - 2018 |
| Event End Date | October 29 - 2018 |
| Place of Publication | USA |
| Publisher | IEEE |
| Abstract Text | In this study, we investigate why API producers deprecate features. Previous work has shown us that knowing the rationale behind deprecation of an API aids a consumer in deciding to react, thus hinting at a diversity of deprecation reasons. We manually analyze the Javadoc of 374 deprecated methods pertaining four mainstream Java APIs to see whether the reason behind deprecation is mentioned. We find that understanding the rationale from just the Javadoc is insufficient; hence we add other data sources such as the source code, issue tracker data and commit history. We observe 12 reasons that trigger API producers to deprecate a feature. We evaluate an automated approach to classify these motivations. |
| Digital Object Identifier | 10.1109/ICSME.2018.00011 |
| Other Identification Number | merlin-id:20236 |
| PDF File |
Download from ZORA
|
| Export |
BibTeX
EP3 XML (ZORA)
|