Alignment of Requirements and Testing in Agile: An Industrial Experience

  • Alessio Bucaioni
  • Antonio Cicchetti
  • Federico Ciccozzi
  • Manvisha Kodali
  • Mikael Sjödin
Conference paper
Part of the Advances in Intelligent Systems and Computing book series (AISC, volume 738)


Agile development aims at switching the focus from processes to interactions between stakeholders, from heavy to minimalistic documentation, from contract negotiation and detailed plans to customer collaboration and prompt reaction to changes. With these premises, requirements traceability may appear to be an overly exigent activity, with little or no return-of-investment. However, since testing remains crucial even when going agile, the developers need to identify at a glance what to test and how to test it. That is why, even though requirements traceability has historically faced a firm resistance from the agile community, it can provide several benefits when promoting precise alignment of requirements with testing. This paper reports on our experience in promoting traceability of requirements and testing in the data communications for mission-critical systems in an industrial Scrum project. We define a semi-automated requirements tracing mechanism which coordinates four traceability techniques. We evaluate the solution by applying it to an industrial project aiming at enhancing the existing Virtual Router Redundancy Protocol by adding Simple Network Management Protocol support.


Testing Agile development Requirements traceability Scrum 



The authors would like to thank Peter Johansson, Per Erik Strandberg, Jonas Nylander and Jon-Olov Vatn from Westermo Research and Development for their support through the VRRP-MIB project. This research is partially supported by the Knowledge Foundation through the MOMENTUM project (


  1. 1.
    I. Jacobson, G. Booch, J. Rumbaugh, G. Booch, The Unified Software Development Process, vol. 1 (Addison-Wesley, Reading, 1999)Google Scholar
  2. 2.
    O.C.Z. Gotel, A.C.W. Finkelstein, An analysis of the requirements traceability problem, in Proceedings of the First International Conference on Requirements Engineering, 1994 (IEEE, New York, 1994), pp. 94–101Google Scholar
  3. 3.
    A. De Lucia, A. Qusef, Requirements engineering in agile software development. J. Emerg. Technol. Web Intell. 2(3), 212–220 (2010)Google Scholar
  4. 4.
    M. Fowler, J. Highsmith, The agile manifesto. Softw. Dev. 9(8), 28–35 (2001)Google Scholar
  5. 5.
    C. Lee, L. Guadagno, X. Jia, An agile approach to capturing requirements and traceability, in Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering (TEFSE 2003) (Citeseer, 2003)Google Scholar
  6. 6.
    V.E. Jyothi, K.N. Rao, Effective implementation of agile practices. Int. J. Adv. Comput. Sci. Appl. 2(3), 41–48 pp. (2011)Google Scholar
  7. 7.
    J.H. Hayes, A. Dekhtyar, J. Osborne, Improving requirements tracing via information retrieval, in Proceedings. 11th IEEE International Requirements Engineering Conference, 2003 (IEEE, New York, 2003), pp. 138–147Google Scholar
  8. 8.
    E. Bjarnason, P. Runeson, M. Borg, M. Unterkalmsteiner, E. Engström, B. Regnell, G. Sabaliauskaite, A. Loconsole, T. Gorschek, R. Feldt, Challenges and practices in aligning requirements with verification and validation: a case study of six companies. Empir. Softw. Eng. 19(6), 1809–1855 (2014)CrossRefGoogle Scholar
  9. 9.
    E.J. Uusitalo, M. Komssi, M. Kauppinen, A.M. Davis, Linking requirements and testing in practice, in International Requirements Engineering, 2008 RE ’08. 16th IEEE, 2008, pp. 265–270Google Scholar
  10. 10.
    S.L. Pfleeger, S.A. Bohner, A framework for software maintenance metrics, in Conference on Software Maintenance, 1990, Proceedings, 1990, pp. 320–327Google Scholar
  11. 11.
    J. Cleland-Huang, G. Zemont, W. Lukasik, A heterogeneous solution for improving the return on investment of requirements traceability, in Requirements Engineering Conference, 2004. Proceedings. 12th IEEE International, 2004, pp. 230–239Google Scholar
  12. 12.
    G. Regan, F. McCaffery, K. McDaid, D. Flood, The barriers to traceability and their potential solutions: Towards a reference framework, in 2012 38th EUROMICRO Conference on Software Engineering and Advanced Applications (SEAA) (2012), pp. 319–322Google Scholar
  13. 13.
    A. Espinoza, J. Garbajosa, A study to support agile methods more effectively through traceability. Innov. Syst. Softw. Eng. 7(1), 53–69 (2011)CrossRefGoogle Scholar
  14. 14.
    I. Inayat, L. Moraes, M. Daneva, S.S. Salim, A reflection on agile requirements engineering: Solutions brought and challenges posed, in Scientific Workshop Proceedings of the XP2015, XP ‘15 Workshops, New York, NY (ACM, New York, 2015), pp. 6:1–6:7Google Scholar
  15. 15.
    V.H. Duc, Traceability in agile software projects, 2013. Master’s thesis, University of Gothenburg.
  16. 16.
    S.W. Ambler, The agile system development life cycle (sdlc) (2009). Ambysoft Inc., [Online]. Available: Accessed 14 May 2014
  17. 17.
    M. Jakobsson, Implementing traceability in agile software development. Department of Computer Science, Lund University, 2009Google Scholar
  18. 18.
    J.H. Hayes, A. Dekhtyar, J. Osborne, Improving requirements tracing via information retrieval, in Requirements Engineering Conference, 2003. Proceedings. 11th IEEE International (IEEE, New York, 2003), pp. 138–147Google Scholar
  19. 19.
    M. Kolla, M. Banka, Merging functional requirements with test cases, Master Thesis Project, Malmö University, Department of Computer Science (2014)Google Scholar
  20. 20.
    G. Duraisamy, R. Atan, Requirement traceability matrix through documentation for scrum methodology. J. Theor. Appl. Inform. Technol. 52(2), 154–159 (2013)Google Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  • Alessio Bucaioni
    • 1
  • Antonio Cicchetti
    • 1
  • Federico Ciccozzi
    • 1
  • Manvisha Kodali
    • 2
  • Mikael Sjödin
    • 1
  1. 1.Mälardalen UniversityVästeråsSweden
  2. 2.WestermoVästeråsSweden

Personalised recommendations