Cited 13 time in
A Systematic Literature Review of Issue-Based Requirement Traceability
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.author | Lyu, Y. | - |
| dc.contributor.author | Cho, Heetae | - |
| dc.contributor.author | Jung, Pil su | - |
| dc.contributor.author | Lee, Seon ah | - |
| dc.date.accessioned | 2023-03-24T09:43:05Z | - |
| dc.date.available | 2023-03-24T09:43:05Z | - |
| dc.date.issued | 2023-02 | - |
| dc.identifier.issn | 2169-3536 | - |
| dc.identifier.uri | https://scholarworks.gnu.ac.kr/handle/sw.gnu/30468 | - |
| dc.description.abstract | Issue reports are software artifacts that often specify the changed requirements of software systems. As software systems evolve according to these changed requirements, issue reports have become the essential artifacts that should be covered by requirement traceability. While researchers have developed automatic approaches for establishing the traceability links of issue reports, no papers have surveyed these approaches. In this paper, we conduct a systematic literature review of issue-based requirement traceability. We searched for articles published in renowned conferences and journals in the software engineering field from 2011 to 2022. From 1,347 initial articles, we identified 40 relevant articles. We investigated four aspects of issue-based traceability: problems, artifact pairs, techniques, and evaluation targets. Our findings are as follows. First, the challenges of issue-based requirement traceability are relevant to accuracy, effort, support, information, and trustworthiness. Second, issue reports are linked to commits, source code, user reviews, and test cases. Third, the studies mainly adopted machine learning and information retrieval techniques to generate and recover trace links. Finally, the main evaluation targets were open-source projects, but open datasets were also provided. Author | - |
| dc.format.extent | 15 | - |
| dc.language | 영어 | - |
| dc.language.iso | ENG | - |
| dc.publisher | Institute of Electrical and Electronics Engineers Inc. | - |
| dc.title | A Systematic Literature Review of Issue-Based Requirement Traceability | - |
| dc.type | Article | - |
| dc.publisher.location | 미국 | - |
| dc.identifier.doi | 10.1109/ACCESS.2023.3242294 | - |
| dc.identifier.scopusid | 2-s2.0-85148461788 | - |
| dc.identifier.wosid | 000933691800001 | - |
| dc.identifier.bibliographicCitation | IEEE Access, v.11, pp 13334 - 13348 | - |
| dc.citation.title | IEEE Access | - |
| dc.citation.volume | 11 | - |
| dc.citation.startPage | 13334 | - |
| dc.citation.endPage | 13348 | - |
| dc.type.docType | Review | - |
| dc.description.isOpenAccess | Y | - |
| dc.description.journalRegisteredClass | scie | - |
| dc.description.journalRegisteredClass | scopus | - |
| dc.relation.journalResearchArea | Computer Science | - |
| dc.relation.journalResearchArea | Engineering | - |
| dc.relation.journalResearchArea | Telecommunications | - |
| dc.relation.journalWebOfScienceCategory | Computer Science, Information Systems | - |
| dc.relation.journalWebOfScienceCategory | Engineering, Electrical & Electronic | - |
| dc.relation.journalWebOfScienceCategory | Telecommunications | - |
| dc.subject.keywordPlus | LOCALIZATION | - |
| dc.subject.keywordPlus | LINKS | - |
| dc.subject.keywordPlus | CODE | - |
| dc.subject.keywordAuthor | Software Issue Reports | - |
| dc.subject.keywordAuthor | Software Requirement Traceability | - |
| dc.subject.keywordAuthor | Systematic Literature Review | - |
| dc.subject.keywordAuthor | Traceability Links | - |
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-0532
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.
