Comparing traceability through information retrieval, commits, interaction logs, and tags
Traceability is used to follow and understand the relationships between various software engineering artifacts such as requirements and source code. Comprehensive traceability of software engineering artifacts is important to ensure that a software can be further developed or maintained. Traceabilit...
Saved in:
| Main Authors: | , , |
|---|---|
| Format: | Article (Journal) Chapter/Article |
| Language: | English |
| Published: |
05 September 2019
|
| In: |
IEEE Xplore digital library
Year: 2019, Pages: 21-28 |
| ISSN: | 2473-2001 |
| DOI: | 10.1109/SST.2019.00015 |
| Online Access: | Resolving-System, Volltext: https://doi.org/10.1109/SST.2019.00015 Verlag: https://ieeexplore.ieee.org/document/8823789 
|
| Author Notes: | Marcus Seiler, Paul Hübner, Barbara Paech |
| Summary: | Traceability is used to follow and understand the relationships between various software engineering artifacts such as requirements and source code. Comprehensive traceability of software engineering artifacts is important to ensure that a software can be further developed or maintained. Traceability links are often created manually by using commit ids or retrospectively by using information retrieval (IR). However, creating traceability links manually is costly and it is error-prone in retrospect. As part of our ongoing research on feature management where traceability is also of interest, we use a lightweight tagging approach to relate artifacts. We want to investigate how such a tag-based approach compares to approaches using commit ids, interaction logs (IL), and IR for creating traceability links. |
|---|---|
| Item Description: | Gesehen am 13.01.2020 |
| Physical Description: | Online Resource |
| ISSN: | 2473-2001 |
| DOI: | 10.1109/SST.2019.00015 |