Behavior-Driven Requirements Traceability via Automated Acceptance Tests

Although information retrieval advances significantly improved automated traceability tools, their accuracy is still far from 100% and therefore they still need human intervention. Furthermore, despite the demonstrated benefits of traceability, many practitioners find the overhead for its creation and maintenance too high. We propose the Behavior Driven Traceability Method (BDT) that takes a different standpoint on automated traceability: we establish ubiquitous traceability between user story requirements and source code by taking advantage of the automated acceptance tests that are created as part of the Behavior Driven Development process.

[1]  Patrick Mäder,et al.  Achieving lightweight trustworthy traceability , 2014, SIGSOFT FSE.

[2]  Rogério Atem de Carvalho,et al.  Mapping Business Process Modeling constructs to Behavior Driven Development Ubiquitous Language , 2010, ArXiv.

[3]  Mohamad Kassab,et al.  The changing landscape of requirements engineering practices over the past decade , 2015, 2015 IEEE Fifth International Workshop on Empirical Requirements Engineering (EmpiRE).

[4]  Matt Wynne,et al.  The Cucumber Book: Behaviour-Driven Development for Testers and Developers , 2012 .

[5]  Alexander Egyed,et al.  Do developers benefit from requirements traceability when evolving and maintaining a software system? , 2014, Empirical Software Engineering.

[6]  Troels Mørch.  Test Driven Development , 2005 .

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

[8]  Xiaoping Jia,et al.  An Agile Approach to Captur ing Requirements and Traceability , 2003 .

[9]  Yuchen Zhang,et al.  An empirical study on recovering requirement-to-code links , 2016, 2016 17th IEEE/ACIS International Conference on Software Engineering, Artificial Intelligence, Networking and Parallel/Distributed Computing (SNPD).

[10]  Jane Cleland-Huang.  Traceability in Agile Projects , 2012, Software and Systems Traceability.

[11]  Zhi Li,et al.  Generating Testing Codes for Behavior-Driven Development from Problem Diagrams: A Tool-Based Approach , 2016, 2016 IEEE 24th International Requirements Engineering Conference (RE).

[12]  Tammo van Lessen,et al.  Modeling Test Cases in BPMN for Behavior-Driven Development , 2016, IEEE Software.

[13]  Sjaak Brinkkemper,et al.  The Use and Effectiveness of User Stories in Practice , 2016, REFSQ.

[14]  B F Skinner,et al.  Behavior modification. , 1974, Science.

[15]  Barbara Paech,et al.  Do Information Retrieval Algorithms for Automated Traceability Perform Effectively on Issue Tracking System Data? , 2016, REFSQ.

[16]  Uirá Kulesza,et al.  Software product lines traceability: A systematic mapping study , 2017, Inf. Softw. Technol..

[17]  Bogdan Dit,et al.  Feature location in source code: a taxonomy and survey , 2013, J. Softw. Evol. Process..

[18]  Per Runeson,et al.  Recovering from a decade: a systematic mapping of information retrieval approaches to software traceability , 2013, Empirical Software Engineering.

[19]  Jane Cleland-Huang,et al.  Evolving Requirements-to-Code Trace Links across Versions of a Software System , 2016, 2016 IEEE International Conference on Software Maintenance and Evolution (ICSME).

[20]  Kent L. Beck,et al.  Test-driven Development - by example , 2002, The Addison-Wesley signature series.

[21]  Robert Wille,et al.  Assisted Behavior Driven Development Using Natural Language Processing , 2012, TOOLS.

[22]  Michal Antkiewicz,et al.  The Problem of the Lack of Benefit of a Document to Its Producer (PotLoBoaDtiP) , 2016, 2016 IEEE International Conference on Software Science, Technology and Engineering (SWSTE).

[23]  Lech Madeyski,et al.  Test-Driven Development - An Empirical Evaluation of Agile Practice , 2009 .

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

[25]  Marcello Thiry,et al.  TraceBoK: Toward a Software Requirements Traceability Body of Knowledge , 2016, 2016 IEEE 24th International Requirements Engineering Conference (RE).

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

[27]  Neil A. Ernst,et al.  Case studies in just-in-time requirements analysis , 2012, 2012 Second IEEE International Workshop on Empirical Requirements Engineering (EmpiRE).

[28]  Norman Wilde,et al.  Software reconnaissance: Mapping program features to code , 1995, J. Softw. Maintenance Res. Pract..

[29]  Klaas Sikkel,et al.  Deciding to Adopt Requirements Traceability in Practice , 2007, CAiSE.