Traceability Fundamentals

  • Orlena Gotel
  • Jane Cleland-Huang
  • Jane Huffman Hayes
  • Andrea Zisman
  • Alexander Egyed
  • Paul Grünbacher
  • Alex Dekhtyar
  • Giuliano Antoniol
  • Jonathan Maletic
  • Patrick Mäder

Abstract

This chapter seeks to provide a reference resource on traceability fundamentals. It defines the essential traceability terminology of trace, trace artifact, trace link, traceability and tracing, and is supplemented by an extensive glossary that has been developed and endorsed by members of the traceability community. This chapter also offers a model of a generic traceability process and describes the essential activities involved in the life cycle of a trace. This model has been used as a frame of reference for articulating the grand challenge of traceability, as reported in the chapter by Gotel et al. of this book. The chapter also describes the basic types of traceability and explains a number of key associated concepts.

References

  1. Aizenbud-Reshef, N., Nolan, B.T., Rubin, J., Shaham-Gafni, Y.: Model traceability. IBM Syst. J. 45(3), 515–526 (2006, July)CrossRefGoogle Scholar
  2. Boehm, B.W.: Software engineering. IEEE Trans. Comput. c-25(12), 1226–1241 (1976, December)CrossRefGoogle Scholar
  3. Cleland-Huang, J., Settimi, R., Romanova, E., Berenbach, B., Clark, S.: Best practices for automated traceability. IEEE Comput. 40(6), 27–35 (2007, June)CrossRefGoogle Scholar
  4. Dorfman, M., Flynn, R.F.: ARTS – An automated requirements traceability system. J. Syst. Softw. 4(1), 63–74 (1984, April)CrossRefGoogle Scholar
  5. Dorfman, M., Thayer, R.H.: Standards, Guidelines, and Examples on System and Software Requirements Engineering: IEEE Computer Society Press Tutorial. IEEE Computer Society Press, Los Alamitos, CA (1990)Google Scholar
  6. Galvao, I., Goknil, A.: Survey of traceability approaches in model-driven engineering. In: Proceedings of the 11th IEEE International Enterprise Distributed Object Computing Conference, Annapolis, MD, USA, 15–19 Oct, 2007, pp. 313–324.Google Scholar
  7. Gotel, O., Finkelstein, A.: An analysis of the requirements traceability problem. In: Proceedings of the 1st IEEE International Conference on Requirements Engineering, Colorado Springs, CO, USA, 18–22 Apr, 1994, pp. 94–101.Google Scholar
  8. Huffman Hayes, J., Dekhtyar, A., Sundaram, S.: Advancing candidate link generation for requirements tracing: The study of methods. IEEE Trans. Softw. Eng. 32(1), pp. 4–19 (2006, January)CrossRefGoogle Scholar
  9. Lindvall, M., Sandahl, K.: Practical implications of traceability. Softw. Pract. Exp. 26(10), 1161–1180 (1996, October)CrossRefGoogle Scholar
  10. Mäder, P., Gotel, O., Philippow, I.: Getting back to basics: Promoting the use of a traceability information model in practice. In: Proceedings of the 5th International Workshop on Traceability in Emerging Forms of Software Engineering, Vancouver, BC, Canada, 18 May, 2009a.Google Scholar
  11. Mäder, P., Gotel, O., Philippow, I.: Motivation matters in the traceability trenches. In: Proceedings of 17th IEEE International Requirements Engineering Conference, Atlanta, GA, USA, 31 Aug–4 Sept, 2009b, pp. 143–148.Google Scholar
  12. Naur, P., Randell, B. (eds.): Software engineering: Report of a conference sponsored by the NATO Science Committee, Garmisch, Germany, 7–11 October 1968, Brussels, Scientific Affairs Division, NATO (Published 1969)Google Scholar
  13. The Oxford English Dictionary: Online Version, Oxford University Press, Oxford. http://www.oed.com. Accessed on January 2007
  14. Pierce, R.: A requirements tracing tool. ACM SIGSOFT Softw. Eng. Notes. 3(5), pp. 53–60 (1978, November)CrossRefGoogle Scholar
  15. Ramesh, B., Edwards, M.: Issues in the development of a requirements traceability model. In: Proceedings of the IEEE International Symposium on Requirements Engineering, San Diego, CA, USA, 4–6 Jan 1993, pp. 256–259.Google Scholar
  16. Ramesh B., Jarke M.: Towards reference models for requirements traceability. IEEE Trans. Softw. Eng. 27(1), 58–93 (2001, January)CrossRefGoogle Scholar
  17. Randell, B.: Towards a methodology of computing system design. In: Naur, P., Randell, B. (eds.) NATO Software Engineering Conference, 1968, Report on a Conference Sponsored by the NATO Science Committee, Garmisch, Germany, pp. 204–208 (7–11 October 1968). Brussels, Scientific Affairs Division, NATO (Published 1969)Google Scholar
  18. Winkler, S., von Pilgrim, J.: A survey of traceability in requirements engineering and model-driven development. Softw. Syst. Model. 9(4), pp. 529–565 (2010, September). Springer (Published on line December 22, 2009)CrossRefGoogle Scholar

Copyright information

© Springer-Verlag London Limited 2012

Authors and Affiliations

  • Orlena Gotel
    • 1
  • Jane Cleland-Huang
    • 2
  • Jane Huffman Hayes
    • 3
  • Andrea Zisman
    • 4
  • Alexander Egyed
    • 5
  • Paul Grünbacher
    • 6
  • Alex Dekhtyar
    • 7
  • Giuliano Antoniol
    • 8
  • Jonathan Maletic
    • 9
  • Patrick Mäder
    • 10
  1. 1.New YorkUSA
  2. 2.DePaul University, School of ComputingChicagoUSA
  3. 3.University of KentuckyLexingtonUSA
  4. 4.School of Informatics, City University LondonLondonUK
  5. 5.Johannes Kepler UniversityLinzAustria
  6. 6.Systems Engineering and AutomationJohannes Kepler UniversityLinzAustria
  7. 7.California Polytechnic State UniversitySan Luis ObispoUSA
  8. 8.École Polytechnique de MontréalMontréalCanada
  9. 9.Kent State UniversityKentUSA
  10. 10.Institute for Systems Engineering and Automation (SEA), Johannes Kepler UniversityLinzAustria

Personalised recommendations