Effective requirements traceability: Models, tools, and practices

The complexity of telecom systems and their production, coupled with today's globalization of markets, customers, and development teams, have made it critical to define and institutionalize an effective strategy for requirements traceability. Being able to trace the life of requirements from their origin, through their allocation to components, to the finished product provides a basis for collaboration and control of functionality, quality, and changes. With the benefits of current software engineering techniques and tools, organizations can cost-effectively implement traceability aligned with the organization's business goals, software engineering maturity, project attributes, and team culture. Within Alcatel-Lucent, several business units have engaged in implementing traceability and our team has developed an automated traceability environment. Based on these experiences we present a framework of guidelines for designing effective traceability strategies and tools.

[1]  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..

[2]  Antje von Knethen,et al.  Change-Oriented Requirements Traceability: Support for Evolution of Embedded Systems , 2002, ICSM.

[3]  Stefan Biffl,et al.  Determining the cost-quality trade-off for automated software traceability , 2005, ASE.

[4]  Sanjiv Augustine,et al.  Managing Agile Projects , 2005 .

[5]  Mary Beth Chrissis,et al.  CMMI: Guidelines for Process Integration and Product Improvement , 2003 .

[6]  Barry W. Boehm,et al.  Get Ready for Agile Methods, with Care , 2002, Computer.

[7]  Barry Boehm,et al.  Balancing Agility and Dis-cipline: A Guide for the Perplexed , 2003 .

[8]  Justin Kelleher.  A reusable traceability framework using patterns , 2005, TEFSE '05.

[9]  Alexander Egyed,et al.  Supporting Software Understanding with Automated Requirements Traceability , 2005, Int. J. Softw. Eng. Knowl. Eng..

[10]  Orlena Cara Zena Gotel,et al.  Contribution structures for requirements traceability , 1995 .

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

[12]  Fadi P. Deek,et al.  Risk Management for Collaborative Software Development , 2006, Inf. Syst. Manag..

[13]  Carl K. Chang,et al.  Event-Based Traceability for Managing Evolutionary Change , 2003, IEEE Trans. Software Eng..

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

[15]  Roger S. Pressman,et al.  Software Engineering: A Practitioner's Approach , 1982 .

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

[17]  Alexander Egyed,et al.  Automating requirements traceability: Beyond the record & replay paradigm , 2002, Proceedings 17th IEEE International Conference on Automated Software Engineering,.

[18]  Fabrice Bouquet,et al.  Requirements traceability in automated test generation: application to smart card software validation , 2005, A-MOST '05.

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