Abstract

Tracing requirements is an essential activity for any type of requirements engineering effort. Given the multifaceted nature of information pieces that help to conceive, refine, verify, and validate requirements during the software life cycle, the success of this activity depends heavily on understanding what information needs to be captured, used, and maintained in what context. The aim of this entry is to expose the reader to the challenging problems that exist for requirements traceability while identifying the state of the art in research and practice.