Value-Based Requirements Traceability: Lessons Learned

Alexander Egyed; Matthias Heindl; Paul Grünbacher; Stefan Biffl

doi:10.1109/RE.2007.16

Value-Based Requirements Traceability: Lessons Learned

Alexander Egyed, Matthias Heindl, Paul Grünbacher, Stefan Biffl

Research output: Chapter in Book/Report/Conference proceeding › Conference proceedings › peer-review

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.

Original language	English
Title of host publication	Proceedings of the 15th IEEE International Requirements Engineering Conference
Publisher	IEEE CS
Pages	115-118
Number of pages	4
DOIs	https://doi.org/10.1109/RE.2007.16
Publication status	Published - Oct 2007

Fields of science

102 Computer Sciences
102022 Software development
102009 Computer simulation
102011 Formal languages
102013 Human-computer interaction
102029 Practical computer science
102024 Usability research

Access to Document

10.1109/RE.2007.16

Cite this

@inproceedings{e676255204514971bf41c894a3a31c8d,

title = "Value-Based Requirements Traceability: Lessons Learned",

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.",

author = "Alexander Egyed and Matthias Heindl and Paul Gr{\"u}nbacher and Stefan Biffl",

year = "2007",

month = oct,

doi = "10.1109/RE.2007.16",

language = "English",

pages = "115--118",

booktitle = "Proceedings of the 15th IEEE International Requirements Engineering Conference",

publisher = "IEEE CS",

}

TY - GEN

T1 - Value-Based Requirements Traceability: Lessons Learned

AU - Egyed, Alexander

AU - Heindl, Matthias

AU - Grünbacher, Paul

AU - Biffl, Stefan

PY - 2007/10

Y1 - 2007/10

N2 - 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.

AB - 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.

U2 - 10.1109/RE.2007.16

DO - 10.1109/RE.2007.16

M3 - Conference proceedings

SP - 115

EP - 118

BT - Proceedings of the 15th IEEE International Requirements Engineering Conference

PB - IEEE CS

ER -