This Article 
 Bibliographic References 
 Add to: 
Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods
January 2006 (vol. 32 no. 1)
pp. 4-19
This paper addresses the issues related to improving the overall quality of the dynamic candidate link generation for the requirements tracing process for Verification and Validation and Independent Verification and Validation analysts. The contribution of the paper is four-fold: We define goals for a tracing tool based on analyst responsibilities in the tracing process, we introduce several new measures for validating that the goals have been satisfied, we implement analyst feedback in the tracing process, and we present a prototype tool that we built, RETRO (REquirements TRacing On-target), to address these goals. We also present the results of a study used to assess RETRO's support of goals and goal elements that can be measured objectively.

[1] M. Abrahams and J. Barkley, “RTL Verification Strategies,” Proc. IEEE WESCON/98, pp. 130-134, Sept. 1998.
[2] D. Anezin, “Process and Methods for Requirements Tracing (Software Development Life Cycle),” dissertation, George Mason Univ., 1994.
[3] G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo, “Recovering Traceability Links between Code and Documentation,” IEEE Trans. Software Eng., vol. 28, no. 10, pp. 970-983, Oct. 2002.
[4] G. Antoniol, B. Caprile, A. Potrich, and P. Tonella, “Design-Code Traceability for Object Oriented Systems,” Annals Software Eng., vol. 9, pp. 35-38, 1999.
[5] R. Baeza-Yates and B. Ribeiro-Neto, Modern Information Retrieval. Addison-Wesley, 1999.
[6] Bandwidth, S2. html, 2005.
[7] S. Bohner, “A Graph Traceability Approach for Software Change Impact Analysis,” dissertation, George Mason Univ., 1995.
[8] P. Brouse, “A Process for Use of Multimedia Information in Requirements Identification and Traceability,” dissertation, George Mason Univ., 1992.
[9] A. Casotto, “Run-Time Requirement Tracing,” Proc. IEEE/ACM Int'l Conf. Computer-Aided Design, pp. 350-355, 1993.
[10] J. Cleland-Huang, C.K. Chang, G. Sethi, K. Javvaji, H. Hu, and J. Xia, “Automating Speculative Queries through Event-Based Requirements Traceability,” Proc. IEEE Joint Int'l Requirements Eng. Conf. (RE '02), pp. 289-296, Sept. 2002.
[11] S. Deerwester, S.T. Dumais, G.W. Furnas, T.K. Landauer, and R. Harshman, “Indexing by Latent Semantic Analysis,” J. Am. Soc. Information Science, vol. 41, no. 6, pp. 391-407, 1990.
[12] A. Dekhtyar, J.H. Hayes, and T. Menzies, “Text Is Software Too,” Proc. Int'l Workshop Mining Sofwtare Repositories (MSR), pp. 22-26, May 2004.
[13] A. Egyed, “A Scenario-Driven Approach to Traceability,” Proc. 23rd Int'l Conf. Software Eng. (ICSE), pp. 123-132, May 2001.
[14] A. Egyed and P. Gruenbacher, “Automatic Requirements Traceability: Beyond the Record and Replay Paradigm,” Proc. 17th IEEE Int'l Conf. Automated Software Eng., pp. 163-171, Sept. 2002.
[15] R.F. Flesch, “A New Readability Yardstick,” J. Applied Psychology, vol. 32, pp. 221-233, 1948.
[16] R.F. Flesch, “Estimating the Comprehension Difficulty of Magazine Articles,” J. General Psychology, vol. 28, pp. 63-80, 1943.
[17] O. Gotel and A. Finkelstein, “An Analysis of the Requirements Traceability Problem,” Proc. First Int'l Conf. Requirements Eng., pp. 94-101, 1994.
[18] J.H. Hayes, “Energizing Software Engineering Education through Real-World Projects as Experimental Studies,” Proc. 15th Conf. Software Eng. Education and Training (CSEET), pp. 192-261, Feb. 2002.
[19] J.H. Hayes, “Risk Reduction through Requirements Tracing,” Proc. Software Quality Week, May 1990.
[20] J.H. Hayes, A. Dekhtyar, and J. Osbourne, “Improving Requirements Tracing via Information Retrieval,” Proc. Int'l Conf. Requirements Eng. (RE), pp. 151-161, Sept. 2003.
[21] J.H. Hayes, A. Dekhtyar, K.S. Sundaram, and S. Howard, “Helping Analysts Trace Requirements: An Objective Look,” Proc. Int'l Conf. Requirements Eng. (RE), pp. 249-261, Sept. 2004.
[22] J.H. Hayes and A. Dekhtyar, “A Framework for Comparing Requirements Tracing Experiments,” Int'l J. Software Eng. and Knowledge Eng. (IJSEKE), vol. 15, no. 5, pp. 185-215, Oct. 2005.
[23] J.H. Hayes, A. Dekhtyar, and S. Sundaram, “Measuring the Effectiveness of Retrieval Techniques in Software Engineering,” Technical Report TR 422-04, Univ. of Kentucky, Oct. 2004.
[24] J.H. Hayes, A. Dekhtyar, and S. Sundaram, “Advancing Requirements Tracing: An Objective Look,” Technical Report TR 423-04, Univ. of Kentucky, Nov. 2004.
[25] J.H. Hayes, A. Dekhtyar, and S. Sundaram, “Text Mining for Software Engineering: How Analyst Feedback Impacts Final Results,” Proc. Second Int'l Workshop Mining Software Repositories (MSR 2005), pp. 58-62, 2005.
[26] J.H. Hayes and A. Dekhtyar, “Humans in the Traceability Loop: Can't Live with 'em, Can't Live without 'em,” Proc. Third Int'l Workshop Traceability in Emerging Forms of Software Eng. (TEFSE '05), pp. 20-23, 2005.
[27] HoLagent Corporation product RDD-100, 2006.
[28] M. Hoffman, N. Kuhn, M. Weber, and M. Bittner, “Requirements for Requirements Management Tools,” Proc. Int'l Conf. Requirements Eng., pp. 301-308, 2004.
[29] INCOSE Requirements Management Tool Survey, http://66.34. 135.97/tools/surveyrtm.html , 19996.
[30] “Level 1A (L1A) and Geolocation Processing Software Requirements Specification,” SDST-059A, GSFC SBRS, 11 Sept. 1997.
[31] A. Marcus and J. Maletic, “Recovering Documentation-to-Source Code Traceability Links using Latent Semantic Indexing,” Proc. 25th Int'l Conf. Software Eng., pp. 125-135, May 2003.
[32] MDP Website, CM-1 Project, http://mdp.ivv.nasa.govmdp_glossary.html#CM1 , 2005.
[33] MODIS Science Data Processing Software, “Requirements Specification Version 2,” SDST-089, GSFC SBRS, 10 Nov. 1997.
[34] T. Mundie and F. Hallsworth, “Requirements Analysis Using SuperTrace PC,” Proc. Am. Soc. Mechanical Engineers (ASME) for the Computers in Eng. Symp. at the Energy & Environmental Expo, 1995.
[35] J. Offutt, Y. Yang, and J.H. Hayes, “SEEWeb: Making Experimental Artifacts Available,” Proc. Workshop Empirical Research in Software Testing (WERST), ACM SIGNOTES, vol. 29, no. 5, pp. 1-3, Sept. 2004.
[36] K. Pohl, “PRO-ART: Enabling Requirements Pre-Traceability,” Proc. IEEE Int'l Conf. Requirements Eng. (RE), pp. 76-85, 1996.
[37] R. Pierce, “A Requirements Tracing Tool,” Proc. Software Quality Assurance Workshop Functional and Performance Issues, 1978.
[38] F. Pinheiro and J. Goguen, “An Object-Oriented Tool for Tracing Requirements,” IEEE Software, pp. 52-64, Mar. 1996.
[39] “Predictor Models in Software Engineering (Promise) Software Engineering Repository,” , 2005.
[40] B. Ramesh, “Factors Influencing Requirements Traceability Practice,” Comm. ACM, vol. 41, no. 12, pp. 37-44, Dec. 1998.
[41] B. Ramesh and M. Jarke, “Toward Reference Models for Requirements Traceability,” IEEE Trans. Software Eng., vol. 27, no. 1, pp. 58-93, Jan. 2001.
[42] B. Ramesh and V. Dhar, “Supporting Systems Development Using Knowledge Captured During Requirements Engineering,” IEEE Trans. Software Eng., vol. 18, no. 6, pp. 498-510, June 1992.
[43] Rational RequisitePro, tools reqpro/, 2006.
[44] J. Rumbaugh, M. Blah, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modeling and Design. Prentice Hall, 1991.
[45] I. Savvidis, “A Multistrategy Framework for Analyzing System Requirements (Software Development),” dissertation, George Mason Univ., 1995.
[46] R. Settimi, J. Cleland-Huang, O. Ben Khadra, J. Mody, W. Lukasik, and C. DePalma, “Supporting Software Evolution through Dynamically Retrieving Traces to UML Artifacts,” Proc. Seventh Int'l Workshop Principles of Software Evolution, pp. 49-54, 2004.
[47] D.I.K. Sjoberg, B. Anda, E. Arisholm, T. Dyba, M. Jorgensen, A. Karahasanovic, E.F. Koren, and M. Vokac, “Conducting Realistic Experiments in Software Engineering,” Proc. Int'l Symp. Empirical Software Eng., pp. 17-26, 2002.
[48] G. Spanoudakis, “Plausible and Adaptive Requirement Traceability Structures,” Proc. 14th Int'l Conf. Software Eng. and Knowledge Eng., pp. 135-142, July 2002.
[49] G. Spanoudakis, A. Zisman, E. Perez-Minana, and P. Krause, “Rule-Based Generation of Requirements Traceability Relations,” J. Systems and Software, pp. 105-127, 2004.
[50] SQL Server Performance, glossary.asp , 2006.
[51] S.K. Sundaram, J.H. Hayes, and A. Dekhtyar, “Baselines in Requirements Tracing,” Proc. Workshop Predictor Models in Software Eng. (PROMISE), May 2005.
[52] Telelogic product DOORS, doorsindex.cfm, 2005.
[53] T. Tsumaki and Y.A. Morisawa, “Framework of Requirements Tracing Using UML,” Proc. Seventh Asia-Pacific Software Eng. Conf., pp. 206-213, Dec. 2000.
[54] R. Watkins and M. Neal, “Why and How of Requirements Tracing,” IEEE Software, vol. 11, no. 4, pp. 104-106, July 1994.
[55] S. Yadla, J.H. Hayes, and A. Dekhtyar, “Tracing Requirements to Defect Reports,” Innovations in Systems and Software Eng.: A NASA J., vol. 1, no. 2, pp. 116-124, Sept. 2005.

Index Terms:
Requirements tracing, dynamic link generation, Verification and Validation (V&V), Independent Validation and Verification (IV&V), information retrieval, TF-IDF, LSI, recall, precision.
Jane Huffman Hayes, Alex Dekhtyar, Senthil Karthikeyan Sundaram, "Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods," IEEE Transactions on Software Engineering, vol. 32, no. 1, pp. 4-19, Jan. 2006, doi:10.1109/TSE.2006.3
Usage of this product signifies your acceptance of the Terms of Use.