Continuous Integration and Delivery Traceability in Industry: Needs and Practices

The importance of traceability in software development has long been recognized, not only for reasons of legality and certification, but also to enable the development itself. At the same time, organizations are known to struggle to live up to traceability requirements, and there is an identified lack of studies on traceability practices in the industry, not least in the area of tooling and infrastructure. This paper identifies traceability as a key challenge in achieving continuous integration and delivery and documents an industry developed framework -- Eiffel -- designed to provide real time traceability in continuous integration and delivery. The efficacy of the Eiffel framework is then investigated through comparison with previous traceability methods.

[1]  Roelf J. Wieringa,et al.  An Introduction to Requirements Traceability , 1995 .

[2]  Patrick Mäder,et al.  Software traceability: trends and future directions , 2014, FOSE.

[3]  Jez Humble,et al.  Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation , 2010 .

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

[5]  Paul Clements,et al.  Software product lines - practices and patterns , 2001, SEI series in software engineering.

[6]  Mike Roberts.  Enterprise Continuous Integration Using Binary Dependencies , 2004, XP.

[7]  Klaus Schmid,et al.  Software product lines in action - the best industrial practice in product line engineering , 2007 .

[8]  Bertrand Meyer,et al.  Eiffel: A language and environment for software engineering , 1988, J. Syst. Softw..

[9]  Matthias Jarke,et al.  Toward Reference Models of Requirements Traceability , 2001, IEEE Trans. Software Eng..

[10]  George Mangalaraj,et al.  Challenges of migrating to agile methodologies , 2005, CACM.

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

[12]  Fred P. Brooks,et al.  The Mythical Man-Month , 1975, Reliable Software.

[13]  Richard N. Taylor,et al.  Software traceability with topic modeling , 2010, 2010 ACM/IEEE 32nd International Conference on Software Engineering.

[14]  Patrick Mäder,et al.  An empirical study on project-specific traceability strategies , 2013, 2013 21st IEEE International Requirements Engineering Conference (RE).

[15]  Klaus Pohl,et al.  Adapting traceability environments to project-specific needs , 1998, CACM.

[16]  Ilka Philippow,et al.  A Survey on Usage Scenarios for Requirements Traceability in Practice , 2013, REFSQ.

[17]  Richard N. Taylor,et al.  Capturing custom link semantics among heterogeneous artifacts and tools , 2009, 2009 ICSE Workshop on Traceability in Emerging Forms of Software Engineering.

[18]  Sue J. Waite,et al.  Real world research: a resource for users of social research methods in applied settings (3rd ed.) , 2012 .

[19]  Giuliano Antoniol,et al.  Recovering Traceability Links between Code and Documentation , 2002, IEEE Trans. Software Eng..