Abstract
Traceability of software artifacts, from requirements to design and through implementation and quality assurance, has long been promoted by the research and expert practitioner communities. However, evidence indicates that, with the exception of those operating in the safety critical domain, few software companies choose to implement traceability processes, in the most part due to cost and complexity issues. This paper presents a review of traceability literature including the implementation of traceability in real organizations. Through both analyzing case studies and research published by leading traceability researchers, this paper synthesizes the motivations of the organizations for implementing traceability. Given the importance of traceability in the regulated domain of safety critical software, the paper compares the motivations and benefits for organizations operating inside and outside of this domain. Finally, based on an analysis of the disparate case studies, the paper re-assesses the value of traceability motivators for more widespread adoption by firms outside of the safety critical sector.
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.
Similar content being viewed by others
References
Gotel, O., et al.: Software and Systems Traceability. Springer, Heidelberg (2011)
Ramesh, B.: Factors influencing requirements traceability practice. Commun. ACM 41, 37–44 (1998)
McCaffery, F., et al.: Medical Device Software Traceability. In: Gotel, O., et al. (eds.) Software and Systems Traceability. Springer (2011)
Dekhtar, A., Hayes, J.H.: Studying the role of Humans in the Traceability Loop. In: Software and Systems Traceability. Springer (2011)
Gotel, O., et al.: The Grand Challenge of Traceability. In: Software and Systems Traceability. Springer (2011)
Neumuller, C., Grunbacher, P.: Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne. In: 21st IEEE/ACM International Conference on Automated Software Engineering, ASE 2006, pp. 145–156 (2006)
Gotel, O., Mader, P.: Acquiring Tool Support for Traceability. In: Software and Systems Traceability. Springer (2011)
Gotel, O.C.Z., Finkelstein, C.W.: An analysis of the requirements traceability problem. In: Proceedings of the First International Conference on Requirements Engineering, pp. 94–101 (1994)
Cleland-Huang, J.: Toward improved traceability of non-functional requirements. Presented at the Proceedings of the 3rd International Workshop on Traceability in Emerging forms of Software Engineering, Long Beach, California (2005)
Gotel, O.: Traceability Fundamentals. In: Gotel, O., et al. (eds.) Software and Systems Traceability. Springer (2011)
Ingram, C., Riddle, S.: Cost Benefits of Traceability. In: Software and Systems Traceability. Springer (2011)
Cleland-Huang, J., et al.: A heterogeneous solution for improving the return on investment of requirements traceability. In: Proceedings of 12th IEEE International Requirements Engineering Conference, pp. 230–239 (2004)
Klimpke, L., Hildenbrand, T.: Towards End-to-End Traceability: Insights and Implications from Five Case Studies. Presented at the Proceedings of the 2009 Fourth International Conference on Software Engineering Advances (2009)
Panis, M.C.: Successful Deployment of Requirements Traceability in a Commercial Engineering Organization...Really. In: 2010 18th IEEE International Requirements Engineering Conference (RE), pp. 303–307 (2010)
Arkley, P., Riddle, S.: Tailoring Traceability Information to Business Needs. In: 14th IEEE International Conference on Requirements Engineering, pp. 239–244 (2006)
McCaffery, F., Casey, V.: Med-Trace. In: O’Connor, R.V., Rout, T., McCaffery, F., Dorling, A. (eds.) SPICE 2011. CCIS, vol. 155, pp. 208–211. Springer, Heidelberg (2011)
Heindl, M., Biffl, S.: A case study on value-based requirements tracing. Presented at the Proceedings of the 10th European Software Engineering Conference Held Jointly with 13th ACM SIGSOFT International Symposium on Foundations of Software Engineering, Lisbon, Portugal (2005)
Born, M., et al.: Application of ISO DIS 26262 in Practice. Presented at the CARS, Valencia, Spain (2010)
Mader, P., et al.: Motivation Matters in the Traceability Trenches. Presented at the Proceedings of the 2009 17th IEEE International Requirements Engineering Conference, RE (2009)
McCaffery, F., Casey, V., McHugh, M.: How Can Software SMEs Become Medical Device Software SMEs. In: O‘Connor, R.V., Pries-Heje, J., Messnarz, R. (eds.) EuroSPI 2011. CCIS, vol. 172, pp. 247–258. Springer, Heidelberg (2011)
Asuncion, H.U., et al.: An end-to-end industrial software traceability tool. Presented at the Proceedings of the the 6th Joint Meeting of the European Software Engineering Conference and the ACM SIGSOFT Symposium on The Foundations of Software Engineering, Dubrovnik, Croatia (2007)
Council, E.: Council Directive 93/42/EEC of 14 June 1993 concerning medical devices. Official Journal of The European Communities (1993)
Council, E.: Directive 2007/47/EC of the European Parliament and of the Council of 5 September 2007. Official Journal of the European Union (2007)
Mason, P.: On Traceability for Safety Critical Systems Engineering. Presented at the Proceedings of the 12th Asia-Pacific Software Engineering Conference (2005)
Cleland-Huang, J.: Traceability in Agile Projects. In: Software and Systems Traceability. Springer (2011)
Hayes, J.H., et al.: REquirements Tracing On target (RETRO): Improving Software Maintenance through Traceability Recovery (2007)
Antoniol, G., et al.: Recovering Traceability Links between Code and Documentation. IEEE Transactions on Software Engineering 28 (2002)
Kazman, R., et al.: ATAM: Method for Architecture Evaluation. Carnegie Mellon Software Engineering Institute, Pittsburgh (2000)
Heider, W., et al.: Evolution-Driven Trace Acquisition in Eclipse-Based Product LineWorkspaces. In: Software and Systems Traceability. Springer (2011)
Arkley, P., Riddle, S.: Overcoming the Traceability Benefit Problem. Presented at the Proceedings of the 13th IEEE International Conference on Requirements Engineering (2005)
Oliveto, R., et al.: Software Artefact Traceability: the Never-Ending Challenge. In: IEEE International Conference on Software Maintenance, ICSM 2007, pp. 485–488 (2007)
Author information
Authors and Affiliations
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2012 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Regan, G., McCaffery, F., McDaid, K., Flood, D. (2012). Traceability-Why Do It?. In: Mas, A., Mesquida, A., Rout, T., O’Connor, R.V., Dorling, A. (eds) Software Process Improvement and Capability Determination. SPICE 2012. Communications in Computer and Information Science, vol 290. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-642-30439-2_15
Download citation
DOI: https://doi.org/10.1007/978-3-642-30439-2_15
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-642-30438-5
Online ISBN: 978-3-642-30439-2
eBook Packages: Computer ScienceComputer Science (R0)