Do developers benefit from requirements traceability when evolving and maintaining a software system? (bibtex)
by Mäder, Patrick and Egyed, Alexander
Abstract:
Software traceability is a required component of many software development processes. Advocates of requirements traceability cite advantages like easier program comprehension and support for software maintenance (i.e., software change). However, despite its growing popularity, there exists no published evaluation about the usefulness of requirements traceability. It is important, if not crucial, to investigate whether the use of requirements traceability can significantly support development tasks to eventually justify its costs. We thus conducted a controlled experiment with 71 subjects re-performing real maintenance tasks on two third-party development projects: half of the tasks with and the other half without traceability. Subjects sketched their task solutions on paper to focus on the their ability to solving the problems rather than their programming skills. Our findings show that subjects with traceability performed on average 24 % faster on a given task and created on average 50 % more correct solutions—suggesting that traceability not only saves effort but can profoundly improve software maintenance quality.
Reference:
Do developers benefit from requirements traceability when evolving and maintaining a software system? (Mäder, Patrick and Egyed, Alexander), In Empirical Software Engineering, Springer US, volume 20, 2015.
Bibtex Entry:
@article{Maeder2014,
abstract = {Software traceability is a required component of many software development processes. Advocates of requirements traceability cite advantages like easier program comprehension and support for software maintenance (i.e., software change). However, despite its growing popularity, there exists no published evaluation about the usefulness of requirements traceability. It is important, if not crucial, to investigate whether the use of requirements traceability can significantly support development tasks to eventually justify its costs. We thus conducted a controlled experiment with 71 subjects re-performing real maintenance tasks on two third-party development projects: half of the tasks with and the other half without traceability. Subjects sketched their task solutions on paper to focus on the their ability to solving the problems rather than their programming skills. Our findings show that subjects with traceability performed on average 24 {\%} faster on a given task and created on average 50 {\%} more correct solutions—suggesting that traceability not only saves effort but can profoundly improve software maintenance quality.},
author = {M{\"{a}}der, Patrick and Egyed, Alexander},
doi = {10.1007/s10664-014-9314-z},
isbn = {1382-3256},
issn = {15737616},
journal = {Empirical Software Engineering},
keywords = {Controlled experiment,Empirical software engineering,Requirements traceability,Software evolution,Software maintenance,Software traceability,Study,Traceability benefit,Traceability effect,Traceability usage,cocome_lit-review},
mendeley-tags = {cocome_lit-review},
number = {2},
pages = {413--441},
publisher = {Springer US},
title = {{Do developers benefit from requirements traceability when evolving and maintaining a software system?}},
url = {http://dx.doi.org/10.1007/s10664-014-9314-z},
volume = {20},
year = {2015}
}
Powered by bibtexbrowser