Value-Based Requirements Traceability: Lessons Learned

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

doi:10.1007/978-3-540-92966-6_14

Value-Based Requirements Traceability: Lessons Learned

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

Abstract:

Traceability from requirements to code is mandated by numerous software development standards. These standards, however, are not explicit about the appropriate level of quality of trace links. From a technical perspective, trace quality should meet the needs of the intended trace utilizations. Unfortunately, long-term trace utilizations are typically unknown at the time of trace acquisition which represents a dilemma for many companies. This chapter suggests ways to balance the cost and benefits of requirements traceability. We present data from three case studies demonstrating that trace acquisition requires broad coverage but can tolerate imprecision. With this trade-off our lessons learned suggest a traceability strategy that (1) provides trace links more quickly, (2) refines trace links according to user-defined value considerations, and (3) supports the later refinement of trace links in case the initial value consideration has changed over time. The scope of our work considers the entire life cycle of traceability instead of just the creation of trace links.

Reference:

Alexander Egyed, Paul GrÃ¼nbacher, Matthias Heindl, Stefan Biffl, "Value-Based Requirements Traceability: Lessons Learned", Springer Berlin Heidelberg, vol. 14, pp. 240-257, 2009.

Bibtex Entry:

@InBook{Egyed2009,
  Title                    = {Value-Based Requirements Traceability: Lessons Learned},
  Author                   = {Alexander Egyed and Paul GrÃ¼nbacher and Matthias Heindl and Stefan Biffl},
  Editor                   = {Kalle Lyytinen and Pericles Loucopoulos and John Mylopoulos and Bill Robinson},
  Pages                    = {240-257},
  Publisher                = {Springer Berlin Heidelberg},
  Year                     = {2009},
  Series                   = {Lecture Notes in Business Information Processing},
  Volume                   = {14},

  Abstract                 = {Traceability from requirements to code is mandated by numerous software development standards. These standards, however, are not explicit about the appropriate level of quality of trace links. From a technical perspective, trace quality should meet the needs of the intended trace utilizations. Unfortunately, long-term trace utilizations are typically unknown at the time of trace acquisition which represents a dilemma for many companies. This chapter suggests ways to balance the cost and benefits of requirements traceability. We present data from three case studies demonstrating that trace acquisition requires broad coverage but can tolerate imprecision. With this trade-off our lessons learned suggest a traceability strategy that (1) provides trace links more quickly, (2) refines trace links according to user-defined value considerations, and (3) supports the later refinement of trace links in case the initial value consideration has changed over time. The scope of our work considers the entire life cycle of traceability instead of just the creation of trace links.},
  Booktitle                = {Design Requirements Engineering: A Ten-Year Perspective},
  Doi                      = {10.1007/978-3-540-92966-6_14},
  ISBN                     = {978-3-540-92966-6},
  Keyword                  = {Computer Science}
}