A Systematic Review of Tracing Solutions in Software Product Lines


  • Zineb Mcharfi IMS Team, SIME Laboratory, ENSIAS, Mohammed V University, Rabat, Morocco
  • Bouchra El Asri IMS Team, SIME Laboratory, ENSIAS, Mohammed V University, Rabat, Morocco
  • Abdelaziz Kriouile IMS Team, SIME Laboratory, ENSIAS, Mohammed V University, Rabat, Morocco


Traceability, Software Product Line, Systematic Review.


Software Product Lines are large-scale, multi-unit systems that enable massive, customized production. They consist of a base of reusable artifacts and points of variation that provide the system with flexibility, allowing generating customized products. However, maintaining a system with such complexity and flexibility could be error prone and time consuming. Indeed, any modification (addition, deletion or update) at the level of a product or an artifact would impact other elements. It would therefore be interesting to adopt an efficient and organized traceability solution to maintain the Software Product Line. Still, traceability is not systematically implemented. It is usually set up for specific constraints (e.g. certification requirements), but abandoned in other situations. In order to draw a picture of the actual conditions of traceability solutions in Software Product Lines context, we decided to address a literature review. This review as well as its findings is detailed in the present article.


[1] Center of Excellence for Software Traceability, “What is Traceability? | Traceability.” [Online]. Available: http://www.coest.org/index.php/what-is-traceability. [Accessed: 06-Jun-2014].
[2] J. Cleland-Huang, O. Gotel, and A. Zisman, Eds., Software and Systems Traceability. London: Springer London, 2012.
[3] J. Cleland-Huang, O. Gotel, J. H. Hayes, P. Mäder, and A. Zisman, “Software Traceability: Trends and Future Directions,” in 36th International Conference on Software Engineering (ICSE), 2014.
[4] M. Lindvall and K. Sandahl, “Practical Implications of Traceability,” Softw. Pract. Exp., vol. 26, no. 10, pp. 1161–1180, Oct. 1996.
[5] N. Anquetil, U. Kulesza, R. Mitschke, A. Moreira, J.-C. Royer, A. Rummler, and A. Sousa, “A model-driven traceability framework for software product lines,” Softw. Syst. Model., vol. 9, pp. 427–451, 2010.
[6] Y. C. Cavalcanti, I. do Carmo Machado, P. A. da Mota, S. Neto, L. L. Lobato, E. S. de Almeida, and S. R. de Lemos Meira, “Towards metamodel support for variability and traceability in software product lines,” in Proceedings of the 5th Workshop on Variability Modeling of Software-Intensive Systems - VaMoS ’11, 2011, pp. 49–57.
[7] B. Ramesh and M. Jarke, “Towards Reference Models for Requirements Traceability,” Softw. Eng. IEEE Trans., vol. 27, no. 1, pp. 58–93, 2001.
[8] G. Spanoudakis and A. Zisman, “Software Traceability: A Roadmap,” in Handbook Of Software Engineering And Knowledge Engineering, vol. III, WORLD SCIENTIFIC, 2005, pp. 395–428.
[9] W. Jirapanthong and A. Zisman, “Supporting product line development through traceability,” in Proceedings - Asia-Pacific Software Engineering Conference, APSEC, 2005, vol. 2005, pp. 506–514.
[10] N. Anquetil, B. Grammel, I. Galvão, J. Noppen, S. Khan, H. Arboleda, A. Rashid, and A. Garcia, “Traceability for Model Driven, Software Product Line Engineering,” in ECMDA Traceability Workshop Proceedings, 2008, vol. 12, pp. 77–86.
[11] K. Berg, J. Bishop, and D. Muthig, “Tracing Software Product Line Variability - From Problem to Solution Space,” Proc. 2005 Annu. Res. Conf. South Africain Inst. Comput. Sci. Inf. Technol. IT Res. Dev. Ctries., pp. 182–191, 2005.
[12] W. Jirapanthong and A. Zisman, “XTraQue: traceability for product line systems,” Softw. Syst. Model., vol. 8, no. 1, pp. 117–144, Feb. 2009.
[13] B. Kitchenham, “Procedures for Performing Systematic Reviews,” Keele, UK, 2004.
[14] I. Hajri, A. Goknil, L. C. Briand, and T. Stephany, “Change impact analysis for evolving configuration decisions in product line use case models,” J. Syst. Softw., vol. 139, pp. 211–237, 2018.
[15] J. Diaz, J. Perez, J. Garbajosa, and C. Fernandez-Sanchez, “Modeling product-line architectural knowledge,” Proc. Annu. Hawaii Int. Conf. Syst. Sci., vol. 2015-March, pp. 5383–5392, 2015.
[16] S. Mohalik, S. Ramesh, J.-V. Millo, S. N. Krishna, and G. K. Narwane, “Tracing SPLs precisely and efficiently,” in Proceedings of the 16th International Software Product Line Conference on - SPLC ’12 -volume 1, 2012, pp. 186–195.
[17] A. Espinoza, G. Botterweck, and J. Garbajosa, “A formal approach to reuse successful traceability practices in SPL projects,” in Proceedings of the 2010 ACM Symposium on Applied Computing - SAC ’10, 2010, pp. 2352–2359.
[18] C. K. F. Corrêa, “Towards automatic consistency preservation for model-driven software product lines,” Proc. 15th Int. Softw. Prod. Line Conf. - SPLC ’11, p. 1, 2011.
[19] S. H. Ripon, “A Unified Tabular Method for Modeling Variants of Software Product Line,” ACM SIGSOFT Softw. Eng. Notes, vol. 37, no. 3, pp. 1–7, 2012.
[20] P. Lago, H. Muccini, and H. van Vliet, “A scoped approach to traceability management,” J. Syst. Softw., vol. 82, no. 1, pp. 168–182, 2009.
[21] L. Linsbauer, R. E. Lopez-Herrejon, and A. Egyed, “Variability extraction and modeling for product variants,” Softw. Syst. Model., vol. 16, no. 4, pp. 1179–1199, 2017.
[22] D. Weyns, B. Michalik, A. Helleboogh, and N. Boucke, “An Architectural Approach to Support Online Updates of Software Product Lines,” 2011 Ninth Work. IEEE/IFIP Conf. Softw. Archit., pp. 204–213, 2011.
[23] H. Eyal-Salman, A. D. Seriai, and C. Dony, “Feature-to-code traceability in a collection of software variants: Combining formal concept analysis and information retrieval,” Proc. 2013 IEEE 14th Int. Conf. Inf. Reuse Integr. IEEE IRI 2013, pp. 209–216, 2013.
[24] L. Linsbauer, E. R. Lopez-Herrejon, and A. Egyed, “Recovering traceability between features and code in product variants,” Proc. 17th Int. Softw. Prod. Line Conf. - SPLC ’13, p. 131, 2013.
[25] X. Tërnava and P. Collet, “Early Consistency Checking between Specification and Implementation Variabilities,” Proc. 21st Int. Syst. Softw. Prod. Line Conf. - Vol. A - SPLC ’17, pp. 29–38, 2017.
[26] “XQuery.” [Online]. Available: https://www.w3.org/TR/xquery/all/.
[27] M. Cadoli, A. Giovanardi, and M. Schaerf, “An Algorithm to Evaluate Quantified {Boolean} Formulae,” in AAAI/IAAI, 1998, pp. 262–267.
[28] “DSL-Scala.” [Online]. Available: https://github.com/ternava/variability-cchecking.
[29] H. U. Asuncion, F. François, and R. N. Taylor, “An end-to-end industrial software traceability tool,” in Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering - ESEC-FSE ’07, 2007, pp. 115–124.
[30] A. Egyed, “A scenario-driven approach to trace dependency analysis,” IEEE Trans. Softw. Eng., vol. 29, no. 2, pp. 116–132, 2003.
[31] J. Cleland-Huang, R. Settimi, O. BenKhadra, E. Berezhanskaya, and S. Christina, “Goal-centric traceability for managing non-functional requirements,” Proc. 27th Int. Conf. Softw. Eng. - ICSE ’05, p. 362, 2005.




How to Cite

Mcharfi, Z., El Asri, B., & Kriouile, A. (2018). A Systematic Review of Tracing Solutions in Software Product Lines. American Scientific Research Journal for Engineering, Technology, and Sciences, 49(1), 226–247. Retrieved from https://www.asrjetsjournal.org/index.php/American_Scientific_Journal/article/view/4540