The DOI matches its Crossref record; 9 of the 9 references it cites were found in a registry or an index.
Improving requirements tracing via information retrieval
Abstract
We present an approach for improving requirements tracing based on framing it as an information retrieval (IR) problem. Specifically, we focus on improving recall and precision in order to reduce the number of missed traceability links as well as to reduce the number of irrelevant potential links that an analyst has to examine when performing requirements tracing. Several IR algorithms were adapted and implemented to address this problem. We evaluated our algorithms by comparing their results and performance to those of a senior analyst who traced manually as well as with an existing requirements tracing tool. Initial results suggest that we can retrieve a significantly higher percentage of the links than analysts, even when using existing tools, and do so in much less time while achieving comparable signal-to-noise levels.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Baeza-Yates, R. A., & Ribeiro-Neto, B. A. (1999) · Cited by 11,505
Information Retrieval: Data Structures and Algorithms
Frakes, W. B., & Baeza-Yates, R. A. (1992) · Cited by 2,393
Recovering traceability links between code and documentation
Antoniol, G., Canfora, G., Casazza, G., De Lucia, A., & Merlo, E. (2002) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2002.1041053 · Cited by 967
Toward reference models for requirements traceability
Ramesh, B., & Jarke, M. (2001) · IEEE Transactions on Software Engineering · doi:10.1109/32.895989 · Cited by 912
Factors influencing requirements traceability practice
Ramesh, B. (1998) · Communications of the ACM · doi:10.1145/290133.290147 · Cited by 196
Heckman, K. E., Stech, F. J., Thomas, R. K., Schmoker, B., & Tsow, A. W. (2015) · Advances in information security · doi:10.1007/978-3-319-25133-2_8 · Cited by 179
Why and how of requirements tracing
Watkins, R., & Neal, M. (1994) · IEEE Software · doi:10.1109/52.300100 · Cited by 110
Automating speculative queries through event-based requirements traceability
Cleland‐Huang, J., Chang, C. K., Sethi, G., Javvaji, K., Hu, H., & Xia, J. (2003) · IEEE International Requirements Engineering Conference (RE) · doi:10.1109/icre.2002.1048540 · Cited by 63
A process for use of multimedia information in requirements identification and traceability
Brouse, P. S. (1992) · Cited by 9
Cited by
Advancing candidate link generation for requirements tracing: the study of methods
Hayes, J. H., Dekhtyar, A., & Sundaram, S. K. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.3 · Cited by 481
Self-citationImproving automated documentation to code traceability by combining retrieval techniques
Chen, X., & Grundy, J. (2011) · 2011 26th IEEE/ACM International Conference on Automated Software Engineering (ASE 2011) · doi:10.1109/ase.2011.6100057 · Cited by 50
Metadata
- Authors
- Hayes, J. H., Dekhtyar, A., & Osborne, J.
- Venue
- Journal of Lightwave Technology
- Publisher
- IEEE Comput. Soc
- Published
- 2004-04-23
- Pages
- 138-147
- ISSN
- 0733-8724 (ISSN-L)
- OpenAlex
- W2153258502
- Cited by
- 287
- References
- 9
- FWCI
- 15.73
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Improving requirements tracing via information retrieval. https://app.cochat.ai/papers/10.1109/icre.2003.1232745
- The paper
- Hayes, J. H., Dekhtyar, A., & Osborne, J. (2004). Improving requirements tracing via information retrieval. Journal of Lightwave Technology. https://doi.org/10.1109/icre.2003.1232745
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.