Please use this identifier to cite or link to this item:
https://doi.org/10.21256/zhaw-30590Full metadata record
| DC Field | Value | Language |
|---|---|---|
| dc.contributor.author | Ruiz, Marcela | - |
| dc.contributor.author | Hu, Jin Yang | - |
| dc.contributor.author | Dalpiaz, Fabiano | - |
| dc.date.accessioned | 2024-05-02T13:01:43Z | - |
| dc.date.available | 2024-05-02T13:01:43Z | - |
| dc.date.issued | 2023 | - |
| dc.identifier.issn | 0947-3602 | de_CH |
| dc.identifier.issn | 1432-010X | de_CH |
| dc.identifier.uri | https://digitalcollection.zhaw.ch/handle/11475/30590 | - |
| dc.description.abstract | Researchers have proposed numerous tools, methods, and techniques for establishing and maintaining software traceability. Despite its acknowledged importance, researchers argue that traceability is still “a sought-after, yet often elusive quality in software-intensive systems”. We have little evidence regarding how creating, managing, and using traceability links vary depending on factors such as organizational contexts, software development practices, and project types. We conduct an empirical study where software development practitioners express their perception regarding the value of software traceability. Via an online survey, 55 participants provided information related to their current traceability practices and needs. Furthermore, we interviewed 14 practitioners to gain a more in-depth understanding. Our study investigates the effect of two independent variables: the software development paradigm and the type of developed software system. Among the several identified findings, our analysis reveals that, although the traceability costs are an inhibitor for adopting more mature traceability practices, the respondents believe that the expected benefits still outweigh envisioned costs. Traceability is mainly performed manually: not only are automated trace retrieval tools scarce, but their offered automation is not expected to replace human involvement. | de_CH |
| dc.language.iso | en | de_CH |
| dc.publisher | Springer | de_CH |
| dc.relation.ispartof | Requirements Engineering | de_CH |
| dc.rights | http://creativecommons.org/licenses/by/4.0/ | de_CH |
| dc.subject | Software traceability | de_CH |
| dc.subject | Exploratory study | de_CH |
| dc.subject | Agile development | de_CH |
| dc.subject | Safety-critical systems | de_CH |
| dc.subject.ddc | 005: Computerprogrammierung, Programme und Daten | de_CH |
| dc.title | Why don’t we trace? : a study on the barriers to software traceability in practice | de_CH |
| dc.type | Beitrag in wissenschaftlicher Zeitschrift | de_CH |
| dcterms.type | Text | de_CH |
| zhaw.departement | School of Engineering | de_CH |
| zhaw.organisationalunit | Institut für Informatik (InIT) | de_CH |
| dc.identifier.doi | 10.1007/s00766-023-00408-9 | de_CH |
| dc.identifier.doi | 10.21256/zhaw-30590 | - |
| zhaw.funding.eu | No | de_CH |
| zhaw.issue | 4 | de_CH |
| zhaw.originated.zhaw | Yes | de_CH |
| zhaw.pages.end | 637 | de_CH |
| zhaw.pages.start | 619 | de_CH |
| zhaw.publication.status | publishedVersion | de_CH |
| zhaw.volume | 28 | de_CH |
| zhaw.publication.review | Peer review (Publikation) | de_CH |
| zhaw.webfeed | Software Engineering | de_CH |
| zhaw.author.additional | No | de_CH |
| zhaw.display.portrait | Yes | de_CH |
| Appears in collections: | Publikationen School of Engineering | |
Files in This Item:
| File | Description | Size | Format | |
|---|---|---|---|---|
| 2023_Ruiz-etal_Why-dont-we-trace_RequirementsEngineering.pdf | 2.56 MB | Adobe PDF |  View/Open |
Show simple item record
Ruiz, M., Hu, J. Y., & Dalpiaz, F. (2023). Why don’t we trace? : a study on the barriers to software traceability in practice. Requirements Engineering, 28(4), 619–637. https://doi.org/10.1007/s00766-023-00408-9
Ruiz, M., Hu, J.Y. and Dalpiaz, F. (2023) ‘Why don’t we trace? : a study on the barriers to software traceability in practice’, Requirements Engineering, 28(4), pp. 619–637. Available at: https://doi.org/10.1007/s00766-023-00408-9.
M. Ruiz, J. Y. Hu, and F. Dalpiaz, “Why don’t we trace? : a study on the barriers to software traceability in practice,” Requirements Engineering, vol. 28, no. 4, pp. 619–637, 2023, doi: 10.1007/s00766-023-00408-9.
RUIZ, Marcela, Jin Yang HU und Fabiano DALPIAZ, 2023. Why don’t we trace? : a study on the barriers to software traceability in practice. Requirements Engineering. 2023. Bd. 28, Nr. 4, S. 619–637. DOI 10.1007/s00766-023-00408-9
Ruiz, Marcela, Jin Yang Hu, and Fabiano Dalpiaz. 2023. “Why Don’t We Trace? : A Study on the Barriers to Software Traceability in Practice.” Requirements Engineering 28 (4): 619–37. https://doi.org/10.1007/s00766-023-00408-9.
Ruiz, Marcela, et al. “Why Don’t We Trace? : A Study on the Barriers to Software Traceability in Practice.” Requirements Engineering, vol. 28, no. 4, 2023, pp. 619–37, https://doi.org/10.1007/s00766-023-00408-9.
Items in DSpace are protected by copyright, with all rights reserved, unless otherwise indicated.