Requirements traceability: A systematic review and industry case study

International Journal of Software Engineering and Knowledge Engineering

Volumn 22, Issue 3, 2012, Pages 385-433

  Torkar, Richard ^a   Gorschek, Tony ^a   Feldt, Robert ^a   Svahnberg, Mikael ^a   Raja, Uzair Akbar ^a   Kamran, Kashif ^a  

^a BLEKINGE INSTITUTE OF TECHNOLOGY   (Sweden)

Author keywords

case study; Requirements traceability; systematic review

Indexed keywords

EMPIRICAL EVIDENCE; EXHAUSTIVE SEARCH; REQUIREMENTS TRACEABILITY; SOFTWARE ENGINEERS; SYSTEMATIC REVIEW; TOOLS AND TECHNIQUES;

ARTIFICIAL INTELLIGENCE;

SOFTWARE ENGINEERING;

EID: 84863462192     PISSN: 02181940     EISSN: None     Source Type: Journal    
DOI: 10.1142/S021819401250009X     Document Type: Review

References (83)

1. A. Abran, J. W. Moore, P. Bourque and R. Dupuis (editors), Guide to the Software Engineering Body of Knowledge (SWEBOK), (IEEE Computer Society, Los Alamitos, 2004
2. W. Afzal, R. Torkar and R. Feldt, A systematic review of search-based testing for nonfunctional system properties, Information and Software Technology 51(6) (2009) 957-976.
3. S. Ahn and K. Chong, A feature-oriented requirements tracing method: A study of costbene t analysis, in Proc. of 2006 International Conference on Hybrid Information Technology, Washington, DC, USA, 2006, IEEE Computer Society, pp. 611-616.
4. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia and E. Merlo, Recovering traceability links between code and documentation, IEEE Transactions on Software Engineering 28(10) (2002) 970-983.
5. P. Arkley and S. Riddle, Overcoming the traceability benet problem, in Proc. of 13th IEEE International Conference on Requirements Engineering, Washington, DC, 2005, pp. 385-389.
6. A. Aurum and C. Wohlin, Engineering and Managing Software Requirements (Springer- Verlag, New York, 2005
7. S. C. Bailin, A. M. Davis, M. Dorfman, R. E. Fairley, S. R. Faulk, K. Forsberg, L. M. Ippolito, H. Mooz, J. D. Palmer, J. Reilly, H. Saiedian, R. H. Thayer and D. R. Wallace, Software Requirements Engineering, 2nd edition (IEEE Computer Society Press, Los Alamitos, 1997
8. M. F. Bashir and M. A. Qadir, Traceability techniques: A critical study, in IEEE Multitopic Conference, Washington, DC, December 2006, pp. 265-268.
9. F. Blaauboer, K. Sikkel and M. N. Aydin, Deciding to adopt requirements traceability in practice, in J. Krogstie, A. L. Opdahl and G. Sindre (eds.), CAiSE, LNCS (Springer, 2007), pp. 294-308.
10. F. Bouquet, E. Jauel, B. Legeard, F. Peureux and M. Utting, Requirements traceability in automated test generation: Application to smart card software validation, SIGSOFT Software Engineering Notes 30(4) (2005) 1
11. F. Bubl and M. Balser, Tracing cross-cutting requirements via context-based constraints, in Proceedings of the 9th European Conference on Software Maintenance and Reengineering, Washington, DC, USA, 2005, pp. 80-90. (Pubitemid 41462507)
12. P. Carlshamre, K. Sandahl, M. Lindvall, B. Regnell and J. Natt och Dag, An industrial survey of requirements interdependencies in software product release planning, in Proceedings of the Fifth IEEE International Symposium on Requirements Engineering, Washington, DC, 2001, p. 84.
13. L. Chung, B. A. Nixon, E. Yu and J. Mylopoulos, Non-functional Requirements in Software Engineering (The Kluwer International Series in Software Engineering, Volume 5) (Kluwer Academic Publisher, 1999
14. J. Cleland-Huang, Toward improved traceability of non-functional requirements, in Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering (ACM, New York, NY, USA, 2005), pp. 14-19.
15. J. Cleland-Huang, B. Berenbach, S. Clark, R. Settimi and E. Romanova, Best practices for automated traceability, IEEE Computer 40(6) (2007) 27-35.
16. J. Cleland-Huang, C. K. Chang and M. Christensen, Event-based traceability for managing evolutionary change, IEEE Transactions on Software Engineering 29(9) (2003) 796-810.
17. J. Cleland-Huang, C. K. Chang and Y. Ge, Supporting event based traceability through high-level recognition of change events, in Proceedings of the 26th International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopment, Washington, DC, 2002, IEEE Computer Society, pp. 595-602.
18. J. Cleland-Huang, C. K. Chang, G. Sethi, K. Javvaji, H. Hu and J. Xia. Automating speculative queries through event-based requirements traceability, in Proceedings of the 10th Anniversary IEEE Joint International Conference on Requirements Engineering, Washington, DC, 2002, IEEE Computer Society, pp. 289-298.
19. J. Cleland-Huang, C. K. Chang and J. C. Wise, Automating performance-related impact analysis through event based traceability, Requirements Engineering 8(3) (2003) 171-182. (Pubitemid 37142651)
20. J. Cleland-Huang, R. Settimi, O. BenKhadra, E. Berezhanskaya and S. Christina, Goalcentric traceability for managing non-functional requirements, in Proceedings of the 27th International Conference on Software Engineering, ACM, New York, NY, USA, 2005, pp. 362-371.
21. J. Cleland-Huang, R. Settimi, C. Duan and X. Zou, Utilizing supporting evidence to improve dynamic requirements traceability, in Proceedings of the 13th IEEE International Conference on Requirements Engineering, Washington, DC, USA, 2005, IEEE Computer Society, pp. 135-144. (Pubitemid 41563784)
22. J. Cleland-Huang, G. Zemont and W. Lukasik, A heterogeneous solution for improving the return on investment of requirements traceability, in Proceedings of the 12th IEEE International Requirements Engineering Conference, Washington, DC, 2004, IEEE Computer Society, pp. 230-239. (Pubitemid 40498787)
23. Software Engineering Institute j Carnegie Mellon, http://www.sei.cmu.edu/ cmmi/October 2008.
24. L. M. Cysneiros and J. C. S. do Prado Leite, Nonfunctional requirements: From elicitation to conceptual models, IEEE Transactions on Software Engineering 30(5) (2004) 328-350.
25. A. Dekhtyar, J. H. Hayes and S. K. Sundaram, Advancing candidate link generation for requirements tracing: The study of methods, IEEE Transactions on Software Engineering 32(1) (2006) 4-19. (Pubitemid 43193062)
26. Department of Defence, US. Military standard: Defense system software development (DOD-STD-2167A), Technical report, Space and Naval Warfare Systems Command, Washington, DC, February 1988.
27. J. Dick, Design traceability, IEEE Software 22(6) (2005) 14-16. (Pubitemid 41709718)
28. J. C. S. do Prado Leite and K. K. Breitman, Experiences using scenarios to enhance traceability, in 2nd International Workshop on Traceability in Emerging Forms of Software Engineering in Conjunction with the 18th IEEE International Conference on Automated Software Engineering, Montreal, Canada, October 2003, pp. 63-70.
29. T. Dybå, V. B. Kampenes and D. I. Sjøberg, A systematic review of statistical power in software engineering experiments, Information and Software Technology 48(8) (2006) 745-755. (Pubitemid 44218930)
30. M. Edwards and S. L. Howell, A Methodology for system requirements specication and traceability for large real-Time complex systems, Technical report, Naval Surface Warfare Center, 1991.
31. A. Egyed and P. Grünbacher, Automating requirements traceability: Beyond the record and replay paradigm, in Proceedings of the 17th IEEE International Conference on Automated Software Engineering, Washington, DC, USA, 2002, p. 163.
32. E. Engstrcom, P. Runeson and M. Skoglund, A systematic review on regression test selection techniques, Information and Software Technology 52(1) (2010) 14-30.
33. R. Feldt, R. Torkar, T. Gorschek and W. Afzal, Searching for cognitively diverse tests: Towards universal test diversity metrics, in Proceedings of 1st Search-Based Software Testing Workshop (SBST'08), 2008, pp. 178-186.
34. T. Gorschek, Requirements Engineering Supporting Technical Product Management, PhD thesis, Department of Systems and Software Engineering, Blekinge Institute of Technology, May 2006.
35. T. Gorschek, P. Garre, S. Larsson and C. Wohlin, A model for technology transfer in practice, IEEE Software 23(6) (2006) 88-95. (Pubitemid 44824162)
36. T. Gorschek and C. Wohlin, Requirements abstraction model, Requirements Engineering 11(1) (2005) 79-101. (Pubitemid 43118936)
37. O. Gotel and A. Finkelstein, An analysis of the requirements traceability problem, in International Conference on Requirements Engineering, 1994, pp. 94-101.
38. O. Gotel and A. Finkelstein, Extended requirements traceability: Results of an industrial case study, in Proceedings of the 3rd IEEE International Symposium on Requirements Engineering, Washington, DC, 1997, p. 169.
39. O. Gotel and S. J. Morris, Crafting the requirements record with the informed use of media, in Proceedings of the First International Workshop on Multimedia Requirements Engineering, Washington, DC, 2006, p. 5.
40. D. Gross and E. Yu, From non-functional requirements to design through patterns, Requirements Engineering 6(1) (2001) 18-36.
41. V. L. Hamilton and M. L. Beeby, Issues of traceability in integrating tools, in Proceedings of the IEE Colloquium Tools and Techniques for Maintaining Traceability during Design, Piscataway, NJ, USA, 1991, pp. 4/1-4/3.
42. J. Han, TRAM: A tool for requirements and architecture management, Australian Computer Science Communications 23(1) (2001) 60-68.
43. Ø. Hauge, C. Ayala and R. Conradi, Adoption of open source software in softwareintensive organizations-A systematic literature review, Information and Software Technology 52(11) (2010) 1133-1154.
44. J. H. Hayes, A. Dekhtyar and J. Osborne, Improving requirements tracing via information retrieval, in Proceedings of the 11th IEEE International Conference on Requirements Engineering, Washington, DC, 2003, p. 138.
45. J. H. Hayes, A. Dekhtyar and S. K. Sundaram, Improving after-The-fact tracing and mapping: Supporting software quality predictions, IEEE Software 22(6) (2005) 30-37. (Pubitemid 41709722)
46. J. H. Hayes, A. Dekhtyar, S. K. Sundaram, E. A. Holbrook, S. Vadlamudi and A. April, Requirements tracing on target (RETRO): Improving software maintenance through traceability recovery, Innovations in Systems and Software Engineering 3(3) (2007) 193-202. (Pubitemid 47412767)
47. M. Heindl and S. Bil, A case study on value-based requirements tracing, in Proceedings of the 10th European Software Engineering Conference Held Jointly with 13th ACM SIGSOFT International Symposium on Foundations of Software Engineering, New York, NY, USA, 2005, pp. 60-69. (Pubitemid 43218810)
48. R. A. Howard and J. E. Matheson (eds.), Readings on the Principles and Applications of Decision Analysis, Strategic Decision Group, Menlo Park, California, 1984.
49. IEEE Society, IEEE recommended practice for software requirements specications (IEEE Std. 830-1998), Technical report, IEEE Computer Society, 1998.
50. M. Ivarsson and T. Gorschek, Technology transfer decision support in requirements engineering research: A systematic review of REj, Requirements Engineering 14(3) (2009) 155-175.
51. M. Jarke, Requirements tracing, Communications of the ACM 41(12) (1998) 32-36.
52. W. Jirapanthong and A. Zisman, XTraQue: Traceability for product line systems, Software and Systems Modeling, 2007.
53. N. Kececi, J. Garbajosa and P. Bourque, Modeling functional requirements to support traceability analysis, in 2006 IEEE International Symposium on Industrial Electronics, Vol. 4, 2006, pp. 3305-3310.
54. J. Kelleher, A reusable traceability framework using patterns, in Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, New York, NY, USA, 2005, pp. 50-55.
55. B. Kitchenham, Procedures for performing systematic reviews, Technical report, Keele University and NICTA, 2004.
56. M. Lormans and A. van Deursen, Reconstructing requirements coverage views from design and test using traceability recovery via LSI, in Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, New York, NY, USA, 2005, pp. 37-42.
57. A. de Lucia, F. Fasano, R. Oliveto and G. Tortora, Recovering traceability links in software artifact management systems using information retrieval methods, ACM Transactions on Software Engineering and Methodology 16(4) (2007) 13.
58. A. Marcus, J. I. Maletic and A. Sergeyev, Recovery of traceability links between software documentation and source code, International Journal of Software Engineering and Knowledge Engineering 15(5) (2005) 811-836. (Pubitemid 41605519)
59. L. Naslavsky, T. A. Alspaugh, D. J. Richardson and H. Ziv, Using scenarios to support traceability, in Proceedings of the 3rd International Workshop on Traceability in Emerging Forms of Software Engineering, New York, NY, USA, 2005, pp. 25-30.
60. R. P. Noll and M. B. Ribeiro, Enhancing traceability using ontologies, in Proceedings of the 2007 ACM Symposium on Applied Computing, New York, NY, USA, 2007, pp. 1496-1497.
61. I. Ozkaya and O. Akin, Tool support for computer-Aided requirement traceability in architectural design: The case of DesignTrack, Automation in Construction 16 (2007) 674-684. (Pubitemid 46575196)
62. K. Pohl, R. Dcomges and M. Jarke, Towards method-driven trace capture, in Proceedings of the 9th International Conference on Advanced Information Systems Engineering, 1997, pp. 103-116.
63. B. Ramesh, Factors inuencing requirements traceability practice, Communications of the ACM 41(12) (1998) 37-44.
64. B. Ramesh and M. Jarke, Toward reference models for requirements traceability, IEEE Transactions on Software Engineering 27(1) (2001) 58-93. (Pubitemid 32168886)
65. B. Ramesh, C. Stubbs, T. Powers and M. Edwards, Requirements traceability: Theory and practice, Annals of Software Engineering 3 (1997) 397-415. (Pubitemid 127429243)
66. R. Ravichandar, J. D. Arthur and M. Perez-Quinones, Pre-requirement specication traceability: Bridging the complexity gap through capabilities, 2007.
67. M. Riebisch and M. Hubner, Traceability-driven model renement for test case generation, in Proceedings of the 12th IEEE International Conference and Workshops on Engineering of Computer-Based Systems, Washington, DC, USA, 2005, pp. 113-120. (Pubitemid 41718852)
68. S. Rochimah, W. M. N. Wan Kadir and A. H. Abdullah, An evaluation of traceability approaches to support software evolution, in Proceedings of the 2007 International Conference on Software Engineering Advances, Washington, DC, 2007, p. 19.
69. A. M. Salem, Improving software quality through requirements traceability models, in Proceedings of the IEEE International Conference on Computer Systems and Applications, Washington, DC, 2006, pp. 1159-1162. (Pubitemid 44711096)
70. C. B. Seaman, Qualitative methods in empirical studies of software engineering, IEEE Transactions on Software Engineering 25(4) (1999) 557-572.
71. Requirements tracing-An overview, http://www.sei.cmu.edu/str/ descriptions/reqtracing.html, October 2008.
72. S. A. Sherba and K. M. Anderson, A framework for managing traceability relationships between requirements and architectures, in Second International Software Requirements to Architectures Workshop Part of 2003 International Conference on Software Engineering, New York, NY, USA, 2003, pp. 150-156.
73. J. E. Shin, A. G. Sutclie and A. Gregoriades, Scenario advisor tool for requirements engineering, Requirements Engineering 10(2) (2005) 132-145. (Pubitemid 40761111)
74. I. Sommerville and G. Kotonya, Requirements Engineering: Processes and Techniques (John Wiley &Sons, New York, 1998
75. I. Sommerville and P. Sawyer, Requirements Engineering: A Good Practice Guide (John Wiley &Sons, New York, 1997
76. G. Spanoudakis, A. Zisman, E. Perez-Minana and P. Krause, Rule-based generation of requirements traceability relations, Journal of Systems and Software 72 (2004) 105-127.
77. D. Streitferdt, Traceability for system families, in Proceedings of the 23rd International Conference on Software Engineering, Washington, DC, 2001, pp. 803-804. (Pubitemid 32485754)
78. R. Torkar, T. Gorschek, R. Feldt, U. A. Raja and K. Kamran, Questionnaire with answers, http://dl.dropbox.com/u/2437798/questions and answers.pdf, October 2008.
79. R. Torkar, T. Gorschek, R. Feldt, U. A. Raja and K. Kamran, Rejected articles, http://dl.dropbox.com/u/2437798/rej art.pdf, October 2008.
80. B. Tvete, Introducing e±cient requirements management, in Proceedings of the 10th International Workshop on Database and Expert Systems Applications, Washington, DC, 1999, p. 370.
81. T. Verhanneman, F. Piessens, B. De Win and W. Joosen, Requirements traceability to support evolution of access control, in Proceedings of the 2005 Workshop on Software Engineering for Secure Systems-Building Trustworthy Applications, ACM, New York, USA, 2005, pp. 1-7.
82. C. Wohlin, P. Runeson, M. Hcost, M. C. Ohlsson, B. Regnell and A. Wesslen, Experimentation in Software Engineering: An Introduction (Kluwer Academic Publishers, Norwell, 2000
83. S. Yadla, J. H. Hayes and A. Dekhtyar, Tracing requirements to defect reports: An application of information retrieval techniques, Innovations in Systems and Software Engineering 1(2) (2005) 116-124. (Pubitemid 41683837)