The Barriers to Traceability and their Potential Solutions: Towards a Reference Framework

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, often due to associated 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 barriers faced by organizations while implementing traceability, along with proposed solutions to the barriers. Additionally, given the importance of traceability in the regulated domain of safety critical software, the paper compares the barriers for organizations operating inside and outside of this domain.

[1]  Olly Gotel,et al.  An analysis of the requirements traceability problem , 1994, Proceedings of IEEE International Conference on Requirements Engineering.

[2]  Balasubramaniam Ramesh,et al.  Factors influencing requirements traceability practice , 1998, CACM.

[3]  Matthias Jarke,et al.  Requirements tracing , 1998, CACM.

[4]  Kenneth M. Anderson,et al.  Towards large-scale information integration , 2002, ICSE '02.

[5]  Jane Cleland-Huang,et al.  A heterogeneous solution for improving the return on investment of requirements traceability , 2004, Proceedings. 12th IEEE International Requirements Engineering Conference, 2004..

[6]  Steve Riddle,et al.  Overcoming the traceability benefit problem , 2005, 13th IEEE International Conference on Requirements Engineering (RE'05).

[7]  Stefan Biffl,et al.  A case study on value-based requirements tracing , 2005, ESEC/FSE-13.

[8]  Paul Grünbacher,et al.  Automating Software Traceability in Very Small Companies: A Case Study and Lessons Learne , 2006, 21st IEEE/ACM International Conference on Automated Software Engineering (ASE'06).

[9]  Steve Riddle,et al.  Tailoring Traceability Information to Business Needs , 2006 .

[10]  Richard N. Taylor,et al.  An end-to-end industrial software traceability tool , 2007, ESEC-FSE '07.

[11]  Stephen Clark,et al.  Best Practices for Automated Traceability , 2007, Computer.

[12]  Tobias Hildenbrand,et al.  Towards End-to-End Traceability: Insights and Implications from Five Case Studies , 2009, 2009 Fourth International Conference on Software Engineering Advances.

[13]  Ilka Philippow,et al.  Motivation Matters in the Traceability Trenches , 2009, 2009 17th IEEE International Requirements Engineering Conference.

[14]  Marc Born,et al.  Application of ISO DIS 26262 in practice , 2010, EDCC-CARS.

[15]  Michael C. Panis,et al.  Successful Deployment of Requirements Traceability in a Commercial Engineering Organization...Really , 2010, 2010 18th IEEE International Requirements Engineering Conference.

[16]  Jane Cleland-Huang,et al.  Tracing architectural concerns in high assurance systems: (NIER track) , 2011, 2011 33rd International Conference on Software Engineering (ICSE).

[17]  Patrick Mäder,et al.  Acquiring Tool Support for Traceability , 2012, Software and Systems Traceability.

[18]  Giuliano Antoniol,et al.  The Grand Challenge of Traceability (v1.0) , 2012, Software and Systems Traceability.

[19]  Jane Huffman Hayes,et al.  Studying the Role of Humans in the Traceability Loop , 2012, Software and Systems Traceability.

[20]  Fergal McCaffery,et al.  Medical Device Software Traceability , 2012, Software and Systems Traceability.

[21]  Claire Ingram,et al.  Cost-Benefits of Traceability , 2012, Software and Systems Traceability.

[22]  Patrick Mäder,et al.  Ready-to-Use Traceability on Evolving Projects , 2012, Software and Systems Traceability.

[23]  Andrea Zisman,et al.  Software and Systems Traceability , 2012, Springer London.