Abstract
[Context and motivation] Requirements traceability is known as an important part of development projects. Studies showed that traceability is applied in practice, but insufficient tool- and method-support hinders its practical use. [Question/problem] We conducted a survey to understand which traceability usage scenarios are most relevant for practitioners. Gaining this information is a required step for providing better traceability support to practitioners. [Principal ideas/results] We identified a list of 29 regularly cited usage scenarios and asked practitioners to assess the frequency of use for each in a typical development project. Our analysis is restricted to those 56 participants that were actively using traceability in order to ensure comparable results. Subjects held various roles in the development and reported about diverse projects. [Contribution] This study provides not only an initial catalog of usage scenarios and their relevance, but also provides insights on practitioner’s traceability practices. In result, we found all scenarios to be used by practitioners. Participants use traceability especially for: finding origin and rationale of requirements, documenting a requirement’s history, and tracking requirement or task implementation state. Furthermore, we highlight topics for ongoing evaluation and better method and tool support in the area of requirements traceability.
This is a preview of subscription content, log in via an institution to check access.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Ahmad, A., Ghazali, M.A.: Documenting requirements traceability information for small projects. In: IEEE International Multitopic Conference, INMIC 2007, pp. 1–5 (2007)
Aizenbud-Reshef, N., Nolan, B.T., Rubin, J., Shaham-Gafni, Y.: Model traceability. IBM Systems Journal 45(3), 515–526 (2006)
Appleton, B.: The trouble with tracing (2005), http://www.cmcrossroads.com/agile-scm/6685-the-trouble-with-tracing-traceability-dissected
Arkley, P., Mason, P., Riddle, S.: Enabling traceability. In: Proceedings of 1st International Workshop on Traceability in Emerging Forms of Software Engineering, pp. 61–65 (2002)
Bouillon, E.: Fragebogen: Nutzerszenarien für den Einsatz von Traceability, http://www.tu-ilmenau.de/fileadmin/media/sspi/Forschung/UmfrageFormatiert.pdf
Cleland-Huang, J.: Just enough requirements traceability. In: Computer Software and Applications Conference, COMPSAC 2006, vol. 1, pp. 41–42 (2006)
Cleland-Huang, J., Gotel, O., Zisman, A.: Software and Systems Traceability. Springer (2012)
Gotel, O., Finkelstein, A.C.W.: An analysis of the requirements traceability problem. In: Proceedings of the First International Conference on Requirements Engineering, pp. 94–101. IEEE Computer Society Press, Colorado Springs (1994)
Kannenberg, A., Saiedian, H.: Why Software Requirements Traceability Remains a Challenge. CrossTalk - Journal of Defense Software Engineering, 14–19 (July/August 2009)
Kirova, V., Kirby, N., Kothari, D., Childres, G.: Effective requirements traceability: Models, tools, and practices. Bell Labs Technical Journal 12(4), 143–157 (2008)
Klimpke, L., Hildenbrand, T.: Towards end-to-end traceability: Insights and implications from five case studies. In: Fourth International Conference on Software Engineering Advances, ICSEA 2009, pp. 465–470 (2009)
Mäder, P., Gotel, O., Philippow, I.: Motivation matters in the traceability trenches. In: Proceedings of 17th International Requirements Engineering Conference, pp. 143–148 (2009)
Padberg, F., Tichy, W.F.: Empirische Methodik in der Softwaretechnik im Allgemeinen und bei der Software-Visualisierung im Besonderen. In: Gesellschaft für Informatik, Software Engineering 2007 - Beiträge zu den Workshops, pp. 211–222 (2007)
Punter, T., Ciolkowski, M., Freimut, B., John, I.: Conducting on-line surveys in software engineering. In: Proceedings of the International Symposium on Empirical Software Engineering, ISESE 2003, pp. 80–88 (2003)
Ramesh, B., Jarke, M.: Toward reference models for requirements traceability. IEEE Trans. Softw. Eng. 27(1), 58–93 (2001)
Ramesh, B., Stubbs, C., Powers, T., Edwards, M.: Requirements traceability: Theory and practice. Annals of Software Engineering 3, 397–415 (1997)
Schwarz, H., Ebert, J., Winter, A.: Graph-based traceability: a comprehensive approach. Software and Systems Modeling 9(4), 473–492 (2009)
Singer, J., Sim, S.E., Lethbridge, T.: Software engineering data collection for field studies. In: Shull, F., Singer, J., Sjøberg, D. (eds.) Guide to Advanced Empirical Software Engineering, pp. 9–34. Springer, London (2008)
Spanoudakis, G., Zisman, A.: Software traceability: A roadmap. In: Chang, S.K. (ed.) Handbook of Software Engineering and Knowledge Engineering, vol. III, pp. 395–428. World Scientific Publishing Co., River Edge (2005)
von Knethen, A., Paech, B.: A survey on tracing approaches in practice and research. IESE-Report, Fraunhofer Inst. Experimentelle Software Engineering, Kaiserslautern (2002)
Winkler, S., von Pilgrim, J.: A survey of traceability in requirements engineering and model-driven development. Software and Systems Modeling 9(4), 529–565 (2010)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2013 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Bouillon, E., Mäder, P., Philippow, I. (2013). A Survey on Usage Scenarios for Requirements Traceability in Practice. In: Doerr, J., Opdahl, A.L. (eds) Requirements Engineering: Foundation for Software Quality. REFSQ 2013. Lecture Notes in Computer Science, vol 7830. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-37422-7_12
Download citation
DOI: https://doi.org/10.1007/978-3-642-37422-7_12
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-37421-0
Online ISBN: 978-3-642-37422-7
eBook Packages: Computer ScienceComputer Science (R0)