Advertisement

Requirements Traceability Through Information Retrieval Using Dynamic Integration of Structural and Co-change Coupling

  • JyotiEmail author
  • Jitender Kumar Chhabra
Conference paper
Part of the Communications in Computer and Information Science book series (CCIS, volume 712)

Abstract

Requirement Traceability (RT) links correlate requirements to their corresponding source code and helps in better requirement understanding, reusability and other software maintenance activities. Since a major portion of software artifacts is in the form of text, for finding these links Information Retrieval (IR) techniques based on textual similarity are widely adopted for Requirement Traceability. But it is hard to find RT links when artifacts have less textual description. So, for finding these links indirectly non-textual techniques like structural information based, co-change history based, ownership based are used with IR. However, if the results of IR contain false positives, the combined approach may increase them further. So, instead of directly combining, this paper proposes an automatic technique for RT by first improving the IR approach and then combining it with the non-textual based techniques. Also, we present a new non-textual based technique based on weighted integration of structural coupling and change history based coupling of classes for retrieving indirect links. The results show that our proposed approach performs better than the existing methods which use coupling information complementary to IR.

Keywords

Requirement Traceability Dynamic integration Co-change coupling Structural coupling 

References

  1. 1.
    Palmer, D.: Traceability in software requirements engineering. In: Thayer, R.H., Dorfman, M. (eds.), Los Alamitos, CA, pp. 412–422. IEEE Computer Society Press (2000)Google Scholar
  2. 2.
    Wright, S.: Requirements Traceability - What?, Why? and How?. In: Proceedings of the Colloquium by the Institution of Electrical Engineers Professional Group C1 (Software Engineering), London (1991)Google Scholar
  3. 3.
    Antoniol, G., Canfora, G., Casazza, G., Lucia, A.D., Merlo, E.: Recovering traceability links between code and documentation. IEEE Trans. Softw. Eng. 28(10), 970–983 (2002). doi: 10.1109/TSE.2002.1041053 CrossRefGoogle Scholar
  4. 4.
    Harman, D.: Ranking algorithms. In: Information Retrieval: Data Structures and Algorithms. Prentice-Hall, Englewood Cliffs, NJ. pp. 363–392 (1992)Google Scholar
  5. 5.
    Baezayates, R., Ibeironeto, B.: Modern Information Retrieval, pp. 363–392. Prentice-Hall, Addison Wesley (1999)Google Scholar
  6. 6.
    Deerwester, S., Dumais, S.T., Harshman, R.: Indexing by latent semantic analysis. J. Am. Soc. Inf. Sci. 41(6), 391–407 (1990)CrossRefGoogle Scholar
  7. 7.
    Lucia, A.D., Fasano, F., Oliveto, R., Tortora, G.: Recovering traceability links in software artifact management systems using information retrieval methods. ACM Trans. Softw. Eng. Methodol. 16(4), 13–63 (2007). doi: 10.1145/1276933.1276934. Article no. 13CrossRefGoogle Scholar
  8. 8.
    McMillan, C., Poshyvanyk, D., Revelle, M.: Combining textual and structural analysis of software artifacts for traceability link recovery. In: Proceedings of TEFSE, pp. 41–48 (2009). doi: 10.1109/TEFSE.2009.5069582
  9. 9.
    Panichella, A., McMillan, C., Moritz, E., Palmieri, D., Oliveto, R., Poshyvanyk, D., Lucia, A.D.: When and how using structural information to improve IR-based traceability recovery. In: Proceedings of the 17th European Conference on Software Maintenance and Reengineering, Genova, Italy, pp. 199–208. IEEE CS Press (2013). doi: 10.1109/CSMR.2013.29
  10. 10.
    Kagdi, H., Maletic, J.I., Sharif, B.: Mining software repositories for traceability links. In: ICPC, pp. 145–154. IEEE Computer Society (2007). doi: 10.1109/ICPC.2007.28
  11. 11.
    Ali, N., Jaafar, F., Hassan, A.E.: Leveraging historical co-change information for requirements traceability. In: 20th Working Conference on Reverse Engineering (WCRE), pp. 361–370 (2013). doi: 10.1109/WCRE.2013.6671311
  12. 12.
    Diaz, D., Bavota, G., Marcus, A., Oliveto, R., Takahashi, S., Lucia, A.D.: Using code ownership to improve IR-based traceability link recovery. In: ICPC, San Francisco, CA, USA, IEEE, pp. 123–132 (2013). doi: 10.1109/ICPC.2013.6613840
  13. 13.
    Marcus, A., Maletic, J.I.: Recovering documentation-to-source-code traceability links using latent semantic indexing. In: Proceedings of 25th International Conference on Software Engineering, Portland, OR, pp. 125–135 (2003)Google Scholar
  14. 14.
    Lucia, A.D., Fasano, F., Oliveto, R., Tortora, G.: Enhancing an artefact management system with traceability recovery feature. In: Proceedings of the 20th IEEE International Conference on Software Maintenance (ICSM), pp. 306–315 (2004). doi: 10.1109/ICSM.2004.1357816
  15. 15.
    Lucia, A.D., Oliveto, R., Sgueglia, P.: Incremental approach and user feedbacks: a silver bullet for traceability recovery? In: 22nd IEEE International Conference on Software Maintenance (ICSM), pp. 299–309 (2006). doi: 10.1109/ICSM.2006.32
  16. 16.
    Lucia, A.D., Fasano, F., Oliveto, R., Tortora, G.: Can information retrieval techniques effectively support traceability link recovery? In: Proceedings of the 14th IEEE International Conference on Program Comprehension (ICPC), pp. 307–316 (2006). doi: 10.1109/ICPC.2006.15
  17. 17.
    Bavota, G., Lucia, A.D., Oliveto, R., Tortora, G.: Enhancing software artifact traceability recovery processes with link count information. Inf. Softw. Technol. J. Elsevier, pp. 163–182 (2014). doi: 10.1016/j.infsof.2013.08.004
  18. 18.
    Lucia, A.D., Penta, M.D., Oliveto, R., Panichella, A., Panichella, S.: Improving IR-based traceability recovery using smoothing filters. In: Proceedings of the 19th International Conference on Program Comprehension, pp. 21–30. IEEE (2014). doi: 10.1109/ICPC.2011.34
  19. 19.
    Nishikawa, K., Oshima, K., Washizaki, H., Mibe, R., Fukazawa, Y.: Recovering transitive traceability links among software artifacts. In: ICSME, Bremen, Germany, pp. 576–580. IEEE (2015). doi: 10.1109/ICSM.2015.7332517
  20. 20.
    Parashar, A., Chhabra, J.K.: Improving modular structure of software system using structural and lexical dependency. Inf. Softw. Technol. 82, 96–120 (2017). doi: 10.1016/j.infsof.2016.09.011
  21. 21.
    Parashar, A., Chhabra, J.K.: Harmony search based remodularization for object-oriented software systems. Comput. Lang. Syst. Struct. 47(2), 153–169 (2017). doi: 10.1016/j.cl.2016.09.003 Google Scholar
  22. 22.
    Parashar, A., Chhabra, J.K.: Package restructuring based on software change history. Natl. Acad. Sci. Lett. 40, 1–7 (2016). doi: 10.1007/s40009-016-0472-y MathSciNetGoogle Scholar
  23. 23.
    Parashar, A., Chhabra, J.K.: Mining software change data stream to predict changeability of classes of object-oriented software system. Evolv. Syst.- Interdiscip. J. Adv. Sci. Technol. 7(2), 117–128 (2016). doi: 10.1007/s12530-016-9151-y Google Scholar
  24. 24.
    Parashar, A., Chhabra, J.K.: Measurement of package-changeability by mining change-history. In: Procedia Comput. Sci. 46 443–448 (201). doi: 10.1016/j.procs.2015.02.042
  25. 25.
    Parasha, A., Chhabra, J.K.: An approach for clustering class coupling metrics to mine object oriented software components. Int. Arab J. Inf. Technol. 13(3), 239–248 (2016)Google Scholar
  26. 26.
    Parashar, A., Chhabra, J.K.: Assessing impact of class change by mining change associations. In: Int. Arab J. Inf. Technol. (IAJIT) (2016, accepted paper)Google Scholar
  27. 27.
    Abadi, A., Nisenson, M., Simionovici, Y.: A traceability technique for specifications. In: Proceedings of the 16th IEEE International Conference on Program Comprehension, pp. 103–112 (2008). doi: 10.1109/ICPC.2008.30
  28. 28.
    iTrust: Role-Based Healthcare Project. http://agile.csc.ncsu.edu/iTrust/
  29. 29.
    Bavota, G., Colangelo, L., Lucia, A.D., Fusco, S., Oliveto, R., Panichella, A.: TraceME: traceability management in eclipse. In: 28th IEEE (ICSM) (2012). doi: 10.1109/ICSM.2012.6405343
  30. 30.
    Lucia, A.D., Oliveto, R., Tortora, G.: ADAMS Re-Trace: traceability link recovery via latent semantic indexing. In: ICSE, pp. 839–842 (2008). doi: 10.1109/CSMR.2005.7
  31. 31.
    Lormans, M., Deursen, A.V.: Can LSI help reconstructing requirements traceability in design and test? In: CSMR, pp. 45–54 (2006). doi: 10.1109/CSMR.2006.13

Copyright information

© Springer Nature Singapore Pte Ltd. 2017

Authors and Affiliations

  1. 1.National Institute of TechnologyKurukshetraIndia

Personalised recommendations