Automatic Detection and Update Suggestion for Outdated API Names in Documentation
DC Field | Value | Language |
---|---|---|
dc.contributor.author | Lee, Seonah | - |
dc.contributor.author | Wu, Rongxin | - |
dc.contributor.author | Cheung, Shing-Chi | - |
dc.contributor.author | Kang, Sungwon | - |
dc.date.accessioned | 2022-12-26T10:30:55Z | - |
dc.date.available | 2022-12-26T10:30:55Z | - |
dc.date.issued | 2021-04-01 | - |
dc.identifier.issn | 0098-5589 | - |
dc.identifier.issn | 1939-3520 | - |
dc.identifier.uri | https://scholarworks.gnu.ac.kr/handle/sw.gnu/3864 | - |
dc.description.abstract | Application programming interfaces (APIs) continually evolve to meet ever-changing user needs, and documentation provides an authoritative reference for their usage. However, API documentation is commonly outdated because nearly all of the associated updates are performed manually. Such outdated documentation, especially with regard to API names, causes major software development issues. In this paper, we propose a method for automatically updating outdated API names in API documentation. Our insight is that API updates in documentation can be derived from API implementation changes between code revisions. To evaluate the proposed method, we applied it to four open source projects. Our evaluation results show that our method, FreshDoc, detects outdated API names in API documentation with 48 percent higher accuracy than the existing state-of-the-art methods do. Moreover, when we checked the updates suggested by FreshDoc against the developers' manual updates in the revised documentation, FreshDoc detected 82 percent of the outdated names. When we reported 40 outdated API names found by FreshDoc via issue tracking systems, developers accepted 75 percent of the suggestions. These evaluation results indicate that FreshDoc can be used as a practical method for the detection and updating of API names in the associated documentation. | - |
dc.format.extent | 23 | - |
dc.language | 영어 | - |
dc.language.iso | ENG | - |
dc.publisher | Institute of Electrical and Electronics Engineers | - |
dc.title | Automatic Detection and Update Suggestion for Outdated API Names in Documentation | - |
dc.type | Article | - |
dc.publisher.location | 미국 | - |
dc.identifier.doi | 10.1109/TSE.2019.2901459 | - |
dc.identifier.scopusid | 2-s2.0-85062153013 | - |
dc.identifier.wosid | 000641961100001 | - |
dc.identifier.bibliographicCitation | IEEE Transactions on Software Engineering, v.47, no.4, pp 653 - 675 | - |
dc.citation.title | IEEE Transactions on Software Engineering | - |
dc.citation.volume | 47 | - |
dc.citation.number | 4 | - |
dc.citation.startPage | 653 | - |
dc.citation.endPage | 675 | - |
dc.type.docType | Article | - |
dc.description.isOpenAccess | N | - |
dc.description.journalRegisteredClass | scie | - |
dc.description.journalRegisteredClass | scopus | - |
dc.relation.journalResearchArea | Computer Science | - |
dc.relation.journalResearchArea | Engineering | - |
dc.relation.journalWebOfScienceCategory | Computer Science, Software Engineering | - |
dc.relation.journalWebOfScienceCategory | Engineering, Electrical & Electronic | - |
dc.subject.keywordAuthor | Documentation | - |
dc.subject.keywordAuthor | Computer bugs | - |
dc.subject.keywordAuthor | Tools | - |
dc.subject.keywordAuthor | History | - |
dc.subject.keywordAuthor | Libraries | - |
dc.subject.keywordAuthor | Software systems | - |
dc.subject.keywordAuthor | Application programming interfaces | - |
dc.subject.keywordAuthor | documentation | - |
dc.subject.keywordAuthor | history | - |
dc.subject.keywordAuthor | software maintenance | - |
Items in ScholarWorks are protected by copyright, with all rights reserved, unless otherwise indicated.
Gyeongsang National University Central Library, 501, Jinju-daero, Jinju-si, Gyeongsangnam-do, 52828, Republic of Korea+82-55-772-0533
COPYRIGHT 2022 GYEONGSANG NATIONAL UNIVERSITY LIBRARY. ALL RIGHTS RESERVED.
Certain data included herein are derived from the © Web of Science of Clarivate Analytics. All rights reserved.
You may not copy or re-distribute this material in whole or in part without the prior written consent of Clarivate Analytics.