by Alexander Egyed, Paul Grünbacher
Abstract:
Requirements traceability (RT) aims at defining and utilizing relationships between stakeholder requirements and artifacts produced during the software development life-cycle and provides an important means to foster software understanding. Although techniques for generating and validating traceability information are available, RT in practice often suffers from the enormous effort and complexity of creating and maintaining traces. This results in invalid or incomplete trace information which cannot support engineers in real-world problems. In this paper we present a tool-supported approach that requires the designer to specify some trace dependencies but eases trace acquisition by generating others automatically. We illustrate the approach using a video-on-demand system and show how the generated traces can be used in various engineering scenarios to improve software understanding. In a case study using an open source software application we demonstrate that the approach is capable of dealing with large-scale systems and delivers valid results.
Reference:
Supporting Software Understanding with Automated Requirements Traceability (Alexander Egyed, Paul Grünbacher), In Int'l Journal of Software Engineering and Knowledge Engineering, volume 15, 2005.
Bibtex Entry:
@Article{dblp:journals/ijseke/EgyedG05,
author = {Alexander Egyed and Paul Grünbacher},
title = {Supporting Software Understanding with Automated Requirements Traceability},
journal = {Int'l Journal of Software Engineering and Knowledge Engineering},
year = {2005},
volume = {15},
number = {5},
pages = {783-810},
abstract = {Requirements traceability (RT) aims at defining and utilizing relationships
between stakeholder requirements and artifacts produced during the
software development life-cycle and provides an important means to
foster software understanding. Although techniques for generating
and validating traceability information are available, RT in practice
often suffers from the enormous effort and complexity of creating
and maintaining traces. This results in invalid or incomplete trace
information which cannot support engineers in real-world problems.
In this paper we present a tool-supported approach that requires
the designer to specify some trace dependencies but eases trace acquisition
by generating others automatically. We illustrate the approach using
a video-on-demand system and show how the generated traces can be
used in various engineering scenarios to improve software understanding.
In a case study using an open source software application we demonstrate
that the approach is capable of dealing with large-scale systems
and delivers valid results.},
bibsource = {dblp computer science bibliography, https://dblp.org},
biburl = {https://dblp.org/rec/bib/journals/ijseke/EgyedG05},
doi = {10.1142/S0218194005002464},
file = {:Journals\\JSEKE 2005 - Supporting Software Understanding with Automated Requirements Traceability\\Supporting Software Understanding with Automated Requirements Traceability-preprint.pdf:PDF},
keywords = {},
owner = {paul},
timestamp = {2015.09.12},
}