[Back]

M. Heindl, S. Biffl, A. Egyed:
"The Impact of Trace Correctness on Requirements Tracing Cost-Benefit - An Evaluation Concept";
Talk: ACM-IEEE International Symposium on Empirical Software Engineering, Rio de Janeiro; 2006-09-21 - 2006-09-22; in: "5th ACM-IEEE International Symposium on Empirical Software Engineering", ACM Press, Vol 2, NY (2006), ISBN: 1-59593-218-6; 51 - 53.

For assessing the impact of requirements changes, project
managers have several options to trace requirements to other
artifacts in a software engineering project: no tracing, ad-hoctracing,
and several levels of systematic tracing. The costs and
benefits of these options can depend on context parameters, such
as the correctness of traces, and on the effort to generate and
maintain traces. Some empirical concepts and studies on the costbenefit
of requirements tracing have been reported; however,
these studies assumed fully correct traces, which is not realistic in
practice, particularly if traces are generated with tool support. In
this paper we sketch a revised cost-benefit model, discuss the
impact of trace correctness, and provide a concept for empirical
evaluation of the revised cost-benefit model.