Value-Based Requirements Traceability: Lessons Learned (bibtex)
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:
Value-Based Requirements Traceability: Lessons Learned (Alexander Egyed, Paul Grünbacher, Matthias Heindl, Stefan Biffl), In Proceedings of the 15th IEEE Int'l Requirements Engineering Conference,( RE 2007), New Delhi, India, IEEE Computer Society, 2007.
Bibtex Entry:
@Conference{DBLP:conf/re/EgyedGHB07,
  author    = {Alexander Egyed and Paul Grünbacher and Matthias Heindl and Stefan Biffl},
  title     = {Value-Based Requirements Traceability: Lessons Learned},
  booktitle = {Proceedings of the 15th IEEE Int'l Requirements Engineering Conference,( RE 2007), 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      = {:Conferences\\RE 2007 - Value-Based Requirements Traceability - Lessons Learned\\Value-Based Requirements Traceability - Lessons Learned-preprint.pdf:PDF},
  isbn      = {0-7695-2935-6},
  keywords  = {},
  owner     = {paul},
  timestamp = {2015.09.12},
}
Powered by bibtexbrowser