Software Requirement Engineering: Traceability Techniques and Tools
DOI:
https://doi.org/10.59992/IJCI.2023.v2n4p1Keywords:
Requirements Traceability, Agile Software System, Requirements Traceability ToolsAbstract
Requirement Traceability is one of the activities in managing requirements. It is important for software projects and is affecting the quality of software products. Requirement Traceability is a method to analyze the effect of changes among various software development lifecycle parts. Agile methodologies have been presented as an alternative to traditional software engineering methodologies. The transformation between traditional and agile methodologies is a hard task so the need for traceability grows. This paper introduces traceability research at the requirement engineering on the traceability literature published during the last years. It also investigates and discusses the requirements for traceability issues. It finally presents several requirement traceability techniques and tools to support traceability.
References
[1] O. Gotel & Anthony” An Analysis of the Requirements Traceability Problem”, C. W. Finkelstein,1993.
[2] O. Gotel and A. Finkelstein, "An Analysis of the Requirements Traceability Problem,” in Proceedings Of 1st International Conference on Requirement Engineering, 1994, pp. 94-101.
[3] G. Spanoudakis and A. Zisman, “Software traceability: a roadmap”, in Handbook of Software Eng. and Knowledge Engineering, 2005.
[4] R. Torkar, et al., “Requirements traceability: a systematic literature review and industry case study”, International Journal of Software Engineering and Knowledge Engineering, vol. 22, no. 3, pp. 1-49, 2012.
[5] O. Gotel, et al., “The Quest for Ubiquity: A Roadmap for Software and Systems Traceability Research”, RE 2012, pp.71-80.
[6] M. Narmanli, “A Business Rule Approach to Requirements Traceability”, Sept. 2010.
[7] F. Pinheiro and J. Goguen, "An Object-Oriented Tool for Tracing Requirements," IEEE Software, vol. 13, no. 2, pp. 52-64, March 1996.
[8] R.J. Wieringa, "An Introduction to Requirements Traceability," Faculty of Mathematics and Computer Science, University of Vrije, Amsterdam, September 1995.
[9] Francisco A. C. Pinheiro, "Requirements Traceability” in Perspectives on software requirements, Jorge Horacio Doorn, Ed.: Springer, 2003, Ch. 5, pp. 91-113.
[10] M. Lindval and K. Sandahl, "Practical Implications of Traceability," Software Practice and Experience, vol. 26, no. 10, pp. 1161-1180, 1996.
[11] B. Ramesh and M. Jarke, "Towards Reference Models for Requirements Traceability," IEEE Transactions in Software Engineering, vol. 27, no. 1, pp. 58-93, 2001.
[12] A. Ghazarian, 2008, “Traceability Patterns: An Approach to Requirement-Component Traceability in Agile Software Development", Proceedings of the 8th WSEAS International Conference on Applied Computer Science, pg.: 236-241.
[13] M. Jacobsson “Implementing Traceability in Agile Software Development”, 2009-02-02.
[14] J. Cleland-Huang, O. Gotel, and A. Zisman, “Software and systems traceability”. Springer,2012, vol. 2, no. 3.
[15] M. Taromirad and R. F. Paige, “Agile requirements traceability using domain-specific modelling languages,” in Proceedings of the 2012 Extreme Modeling Workshop, 2012, pp.45-50.
[16] O. Badreddin, A. Sturm, and T. C. Lethbridge, “Requirement traceability: A model-based approach," in Model-Driven Requirements Engineering Workshop (MoDRE), 2014 IEEE 4th International. IEEE, 2014, pp. 87-91.
[17] S. Ratanotayanon, S. E. Sim, and R. Gallardo-Valencia, “Supporting program comprehension in agile with links to user stories," in Agile Conference, 2009. AGILE'09. IEEE, 2009, pp.26-32.
[18] B. Arbain, A. Firdaus, I. Ghani, W. Kadir, and W. M. Nasir, “Agile non-functional requirements (NFR) traceability metamodel," in Software Engineering Conference (MySEC),2014 8th Malaysian. IEEE, 2014, pp. 228-233.
[19] J. Cleland-Huang, B. Berenbach, S. Clark, R. Settimi, and E. Romanova, “Best practices for automated traceability," Computer, no. 6, pp. 27-35, 2007.
[20] G. Duraisamy and R. Atan,” Requirement traceability matrix through documentation for scrum methodology." Journal of Theoretical & Applied Information Technology, vol. 52, no. 2, pp. 154-159, 2013.
[21] M. Omar and J. Dhar,” A Systematic Literature review of traceability Practices for Managing Software Requirements”, Journal of Engineering and Applied Science 12 (Special Issue 4), Medwell Journals 2017
[22] J. Cleland-Huang, O. Gotel, P. Mäder, A. Zisman, and J. Huffman Hayes “Software Traceability: Trends and Future Directions, ICSE ’14 Hyderabad, India Copyright 2014 ACM 978-1-4503-2865-4/14/05.
[23] O. Gotel, J. Cleland-Huang, J. Huffman Hayes, A. Zisman, A. Egyed, P. Grunbacher, and G. Antoniol. The quest for ubiquity: A roadmap for software and systems traceability research. In 21st IEEE International Requirements Engineering Conference (RE), pages 71 -80, 2012.
[24] O. Gotel, J. Cleland-Huang, J. Huffman Hayes, A. Zisman, A. Egyed, P. Grunbacher, A. Dekhtyar, G. Antoniol, and J. Maletic. The grand challenge of traceability (v1.0). In J. Cleland-Huang, O. Gotel, and A. Zisman, editors, Software and Systems Traceability, pages 343{409. Springer, 2012.
[25] E. Keenan, A. Czauderna, G. Leach, J. Cleland-Huang, Y. Shin, E. Moritz, M. Gethers, D. Poshyvanyk, J. Maletic, J. Huffman Hayes, A. Dekhtyar, D. Manukian, S. Hossein, and D. Hearn. Trace lab: An experimental workbench for equipping researchers to innovate, synthesize, and comparatively evaluate traceability solutions. In Tool Demo,34th International Conference on Software Engineering (ICSE), pages 1375-1378, 2012.
[26] M. Taromirad, and R. F. Paige. “Agile Requirements Traceability Using Domain-Specific Modelling Languages”. Proceedings of the 2012 Extreme Modeling Workshop on –XM '12 (2012).
[27] Satish C J, Anand M, and Thendral Puyalnithi,” A Review of Tools for Traceability Management in Software Projects “, International Journal for Research in Emerging Science and Technology, Volume-3, Issue-3, Mar-2016.
[28] Mäder, Patrick, Orlena Gotel, and Ilka Philippow.“Enabling automated traceability maintenance through the upkeep of traceability relations." Model Driven Architecture-Foundations and Applications. Springer Berlin Heidelberg, 2009.
[29] Mäder, Patrick, et al. "trace Maintainer-Automated Traceability Maintenance." International Requirements Engineering, 2008. RE'08. 16th IEEE. IEEE, 2008.
[30] Lucia, Andrea D., et al. "Adams re-trace: A traceability recovery tool. “Software Maintenance and Reengineering, 2005. CSMR 2005. Ninth European Conference on. IEEE, 2005.
[31] Alexander E. “scenario-driven approach to traceability." Proceedingsof the 23rd international conference on Software engineering. IEEE Computer Society, 2001.
[32] Sherba, Susanne A., Kenneth M. Anderson, and Maha Faisal."A framework for mapping traceability relationships." Proceedings of the 2nd International Workshop on Traceability in Emerging Forms of Software Engineering. 2003.
[33] Sundaram, Senthil Karthikeyan, et al. "Assessing Traceability of software engineering artifacts." Requirements engineering 15.3 (2010): 313-335.
[34] Ali, Nawazish, Yann-Gael Gueneuc, and Giuliano Antoniol. "Trustrace: Mining software repositories to improve the accuracy of requirement traceability links." Software Engineering, IEEE Transactions on 39.5 (2013):725-741.
[35] Asuncion, Hazeline U., Frédéric François, and Richard N. Taylor. "An end-to-end industrial software traceability tool." Proceedings of the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on the foundations of software engineering. ACM, 2007.
[36] Appleton, B. ACME Blog: Traceability and TRUST-ability. http://bradapp.blogspot.com/2005/03/traceability-and-trust-ability.html (2005, Tuesday, 15 March). Accessed June 2011.
[37] G. Antonio, J. Cleland- Huang, J. Hayes, M. Vierhauser,” Grand Challenges of Traceability 2017”, Cornel University.
[38] K. Beck and C. Andres. Extreme programming explained: embrace change. Addison-Wesley, Boston, MA, USA, 2nd edition, 2004.
