Skip to main content
SpringerLink
Log in

REquirements TRacing On target (RETRO): improving software maintenance through traceability recovery

  • Original Paper
  • Published:
Innovations in Systems and Software Engineering Aims and scope Submit manuscript

Abstract

A number of important tasks in software maintenance require an up-to-date requirements traceability matrix (RTM): change impact analysis, determination of test cases to execute for regression testing, etc. The generation and maintenance of RTMs are tedious and error-prone, and they are hence often not done. In this paper, we present REquirements TRacing On-target (RETRO), a special- purpose requirements tracing tool. We discuss how RETRO automates the generation of RTMs and present the results of a study comparing manual RTM generation to RTM generation using RETRO. The study showed that RETRO found significantly more correct links than manual tracing and took only one third of the time to do so.

This is a preview of subscription content, log in via an institution to check access.

Access this article

Log in via an institution

Price excludes VAT (USA)
Tax calculation will be finalised during checkout.

Instant access to the full article PDF.

Institutional subscriptions

Similar content being viewed by others

References

  1. Huffman Hayes J, Dekhtyar A, Osborne J (2003) Improving requirements tracing via information retrieval. In: Proceedings, international requirements engineering conference (RE’2003), September 2003, Monterey, pp 151–161

  2. Huffman Hayes J, Dekhtyar A, Sundaram KS, Howard S (2004) Helping analysts trace requirements: an objective look. In: Proceedings, international requirements engineering conference (RE’2004), September 2004, Kyoto, Japan, pp 249–261

  3. Huffman Hayes J, Dekhtyar A and Sundaram KS (2006). Advancing candidate link generation for requirements tracing: the study of methods. IEEE Trans Softw Eng 32(1): 4–19

    Article  Google Scholar 

  4. Yadla S, Huffman Hayes J and Dekhtyar A (2005). Tracing requirements to defect reports. Innov Syst Softw Eng A NASA J 1(2): 116–124

    Article  Google Scholar 

  5. Huffman Hayes J, Dekhtyar A, Sundaram S (2005) Text mining for software engineering: how analyst feedback impacts final results. In: Proceedings of workshop on mining of software repositories (MSR), associated with ICSE 2005, St. Louis, MO, May 2005, pp 58–62

  6. Huffman Hayes J, Dekhtyar A, Sundaram S (2006) Advances in dynamic generation of traceability links: two steps closer to full automation? Proceedings of IEEE International conference on Requirements Engineering, October 2007, New Delhi

  7. Baeza-Yates R, Ribeiro-Neto B (1999) Modern information retrieval. Addison-Wesley, Reading

  8. Huffman Hayes J, Dekhtyar A and Sundaram KS (2005). Improving after the fact tracing and mapping to support software quality predictions. IEEE Softw 22(6): 30–37

    Article  Google Scholar 

  9. McGill K, Deadrick W, Hayes J, Dekhtyar A (2006) Houston, we have a success story: technology transfer at the NASA IV&V facility. In: Proceedings, international workshop on technology transfer in software engineering (WOTTSE’2006), Shanghai, China, May 2006

  10. Ramesh B (1998). Factors influencing requirements traceability practice. Commun ACM 41(12): 37–44

    Article  Google Scholar 

  11. Spanoudakis G (2002) Plausible and adaptive requirement traceability structures. In: Proceedings 14th international conference on software engineering and knowledge engineering. Ischia, Italy, July 2002, pp 135–142

  12. Cleland-Huang J, Chang CK, Sethi G, Javvaji K, Hu H, Xia J (2002) Automating speculative queries through event-based requirements traceability. In: Proceedings of the IEEE joint international requirements engineering conference (RE’02). Essex, Germany, 9–13 September, 2002, pp 289–296

  13. Zisman A, Spanoudakis G, Pérez-Miñana E, Krause P (2003) Tracing software requirements artefacts. In: Proceedings 2003 international conference on software engineering research and practice (SERP 2003), Las Vegas, June 2003

  14. Schneidewind NF (1987). The state of software maintenance. IEEE Trans Softw Eng 13(3): 303–310

    Article  Google Scholar 

  15. Bubel F, Balser M (2005) Tracing cross-cutting requirements via context-based constraints. In: Proceedings ninth European conference on software maintenance and reengineering (CSMR’05), pp 80–90

  16. Ivkovic I, Kontogiannis K (2004) Tracing evolution changes of software artifacts through model synchronization. In: Proceedings 20th IEEE international conference on software maintenance (ICSM’04), pp 252–26

  17. Rountev A (2004) Precise identification of side-effect-free methods in Java. In: Proceedings 20th IEEE international conference on software maintenance (ICSM’04), pp 82–91

  18. Ryder BG, Landi W, Stocks P, Zhang S and Altucher R (2001). A schema for interprocedural modification side-effect analysis with pointer aliasing. ACM Trans Program Lang Syst 23(2): 105–186

    Article  Google Scholar 

  19. David Eisenberg A, De Volder K (2005) Dynamic feature traces: finding features in unfamiliar code. In: Proceedings international conference on software maintenance (ICSM’05), pp 337–346

  20. Greevy O, Ducasse S Girba T (2005) Analyzing feature traces to incorporate the semantics of change in software evolution analysis. In: Proceedings international conference on software maintenance (ICSM’05)

  21. De Lucia A, Fasano F, Francese R, Oliveto R (2004) Recovering Traceability links between requirement artefacts: a case study. In: Proceedings 16th international conference on software engineering and knowledge engineering—workshop on knowledge oriented maintenance, Banff, Alberta, Canada, Knowledge Systems Institute, USA, pp 453–456

  22. MDP Website, CM-1 Project, http://mdp.ivv.nasa.gov/mdp_glossary.html#CM1

  23. Schach SR, Jin B, Yu L, Heller GZ and Offutt J (2003). Determining the distribution of maintenance categories: survey versus management. Empir Softw Eng 8: 351–366

    Article  Google Scholar 

  24. Antoniol G, Canfora G, Casazza G, De Lucia A and Merlo E (2002). Recovering traceability links between code and documentation. IEEE Trans Softw Eng 28(10): 970–983

    Article  Google Scholar 

  25. Antoniol G, Caprile B, Potrich A and Tonella P (1999). Design-code traceability for object oriented systems. Ann Softw Eng 9: 35–58

    Article  Google Scholar 

  26. Høst M, Regnell B and Wohlin C (2000). Using students as subjects—a comparative study of students and professionals in lead-time impact assessment. Empir Softw Eng 5(3): 210–214

    Article  Google Scholar 

  27. Marcus A, Maletic J (2003) Recovering documentation-to-source code traceability links using latent semantic indexing. In: Proceedings of the twenty-fifth international conference on software engineering (ICSE), pp 125–135

Download references

Author information

Authors and Affiliations

  1. Computer Science Department, University of Kentucky, Lexington, USA

    Jane Huffman Hayes, Senthil Karthikeyan Sundaram, E. Ashlee Holbrook & Sravanthi Vadlamudi

  2. Center of Excellence in Traceability, Lexington, USA

    Alex Dekhtyar

  3. Department of Software Engineering Université du Québec, École de Technologie Supérieure, Montreal, Canada

    Alain April

Authors
  1. Jane Huffman Hayes
    View author publications

    You can also search for this author in PubMed Google Scholar

  2. Alex Dekhtyar
    View author publications

    You can also search for this author in PubMed Google Scholar

  3. Senthil Karthikeyan Sundaram
    View author publications

    You can also search for this author in PubMed Google Scholar

  4. E. Ashlee Holbrook
    View author publications

    You can also search for this author in PubMed Google Scholar

  5. Sravanthi Vadlamudi
    View author publications

    You can also search for this author in PubMed Google Scholar

  6. Alain April
    View author publications

    You can also search for this author in PubMed Google Scholar

Corresponding author

Correspondence to Jane Huffman Hayes.

Additional information

Work performed while A. Dekhtyar was on the faculty at the University of Kentucky.

Rights and permissions

Reprints and permissions

About this article

Cite this article

Hayes, J.H., Dekhtyar, A., Sundaram, S.K. et al. REquirements TRacing On target (RETRO): improving software maintenance through traceability recovery. Innovations Syst Softw Eng 3, 193–202 (2007). https://doi.org/10.1007/s11334-007-0024-1

Download citation

  • Received:

  • Accepted:

  • Published:

  • Issue Date:

  • DOI: https://doi.org/10.1007/s11334-007-0024-1

Keywords

Search

Navigation