Abstract
The requirements traceability matrix can successfully predict quality before code is written. However, its tedious development process, requiring analysts to manually discover and vet links between artifact levels, has stymied widespread adoption. The authors' tracing toolkit, called Retro (Requirements Tracing on Target), automates the information retrieval process, making RTM's development easier. Backed by empirical results, the authors describe Retro's advantages over other information retrieval approaches.
Original language | English |
---|---|
Pages (from-to) | 30-37 |
Number of pages | 8 |
Journal | IEEE Software |
Volume | 22 |
Issue number | 6 |
DOIs | |
State | Published - Nov 2005 |
Bibliographical note
Funding Information:NASA funds our work under grant NAG5-11732. We thank Stephanie Ferguson and Ken McGill. We also thank the Metrics Data Program, Mike Chapman, and the MODIS program. We also thank our students who worked on RETRO: James Osborne, Sarah Howard, Ganapathy Chidambaram, and Sravanthi Vadlamudi.
ASJC Scopus subject areas
- Software