Value-Based Requirements Traceability: Lessons Learned

Egyed, Alexander; GrÃ¼nbacher, Paul; Heindl, Matthias; Biffl, Stefan

doi:10.1109/RE.2007.16

Value-Based Requirements Traceability: Lessons Learned

by Alexander Egyed, Paul GrÃ¼nbacher, Matthias Heindl, Stefan Biffl

Abstract:

Software development standards demand requirements traceability without being explicit about the appropriate level of quality of trace links. Unfortunately, long-term trace utilizations are typically unknown at the time of trace acquisition which represents a dilemma for many companies. This paper suggests ways to balance the cost and benefits of requirements traceability. We present data from 3 case studies. Lessons learned suggest a traceability strategy that (1) provides trace links more quickly, (2) refines trace links according to user-definable value considerations, and (3) supports the later refinement of trace links in case the initial value considerations change.

Reference:

Alexander Egyed, Paul GrÃ¼nbacher, Matthias Heindl, Stefan Biffl, "Value-Based Requirements Traceability: Lessons Learned", IEEE Computer Society, pp. 115-118, 2007.

Bibtex Entry:

@Conference{DBLP:conf/re/EgyedGHB07,
  Title                    = {Value-Based Requirements Traceability: Lessons Learned},
  Author                   = {Alexander Egyed and Paul GrÃ¼nbacher and Matthias Heindl and Stefan Biffl},
  Booktitle                = {Proceedings 15th IEEE Int'l Requirements Engineering Conference, RE 2007, October 15-19, New Delhi, India},
  Year                     = {2007},
  Pages                    = {115-118},
  Publisher                = {IEEE Computer Society},

  Abstract                 = {Software development standards demand requirements traceability without being explicit about the appropriate level of quality of trace links. Unfortunately, long-term trace utilizations are typically unknown at the time of trace acquisition which represents a dilemma for many companies. This paper suggests ways to balance the cost and benefits of requirements traceability. We present data from 3 case studies. Lessons learned suggest a traceability strategy that (1) provides trace links more quickly, (2) refines trace links according to user-definable value considerations, and (3) supports the later refinement of trace links in case the initial value considerations change.},
  Doi                      = {10.1109/RE.2007.16},
  File                     = {Value-Based Requirements Traceability - Lessons Learned:Conferences\\RE 2007 - Value-Based Requirements Traceability - Lessons Learned\\Value-Based Requirements Traceability - Lessons Learned.pdf:PDF},
  ISBN                     = {0-7695-2935-6},
  Keywords                 = {requirements, traceability},
  Owner                    = {paul},
  Timestamp                = {2015.09.12}
}