On-Demand Automated Traceability Maintenance and Evolution

  • Muhammad Atif Javed
  • Faiz UL MuramEmail author
  • Uwe Zdun
Conference paper
Part of the Lecture Notes in Computer Science book series (LNCS, volume 10826)


After the painstaking process of traceability construction, a substantial evolution of a software system, such as a new major version leads to the decay of traceability links. To date, however, none of the published studies have considered the on-demand update of traceability links. This paper presents an on-demand automated approach for case-based maintenance and evolution of traceability links in the context of different versions of a software project. The approach focuses on the component-to-component features for identification and prioritization of previous traceability cases, which are then used to perform reuse and adaptation of traceability links based on the matches and mismatches, respectively. The adapted (i.e., newly constructed) traceability links can then be verified by a human analyst and stored in a case base. The approach has been validated using an open-source framework for mobile games, named Soomla Android store.


  1. 1.
    Borg, M., Gotel, O.C.Z., Wnuk, K.: Enabling traceability reuse for impact analyses: a feasibility study in a safety context. In: 7th International Workshop on Traceability in Emerging Forms of Software Engineering, TEFSE 2013, pp. 72–78 (2013)Google Scholar
  2. 2.
    Buchgeher, G., Weinreich, R.: Automatic tracing of decisions to architecture and implementation. In: 9th Working IEEE/IFIP Conference on Software Architecture, WICSA 2011, pp. 46–55 (2011)Google Scholar
  3. 3.
    Cleland-Huang, J., Chang, C.K., Ge, Y.: Supporting event based traceability through high-level recognition of change events. In: 26th International Computer Software and Applications Conference on Prolonging Software Life: Development and Redevelopment, COMPSAC 2002, pp. 595–600 (2002)Google Scholar
  4. 4.
    Cliff, N.: Dominance statistics: ordinal analyses to answer ordinal questions. Psychol. Bull. 114, 494–509 (1993)CrossRefGoogle Scholar
  5. 5.
    Dekhtyar, A., Dekhtyar, O., Holden, J., Hayes, J., Cuddeback, D., Kong, W.-K.: On human analyst performance in assisted requirements tracing: statistical analysis. In: 19th IEEE International Requirements Engineering Conference, RE 2011, pp. 111–120 (2011)Google Scholar
  6. 6.
    Hammad, M., Collard, M.L., Maletic, J.I.: Automatically identifying changes that impact code-to-design traceability during evolution. Softw. Quality Control 19(1), 35–64 (2011)CrossRefGoogle Scholar
  7. 7.
    Javed, M.A., Stevanetic, S., Zdun, U.: Cost-effective traceability links for architecture-level software understanding: a controlled experiment. In: 24th Australasian Software Engineering Conference, ASWEC 2015, vol. 2, pp. 69–73 (2015)Google Scholar
  8. 8.
    Javed, M.A., Stevanetic, S., Zdun, U.: Towards a pattern language for construction and maintenance of software architecture traceability links. In: 21st European Conference on Pattern Languages of Programs, EuroPlop 2016, pp. 24:1–24:20 (2016)Google Scholar
  9. 9.
    Javed, M.A., Zdun, U.: On the effects of traceability links in differently sized software systems. In: 19th International Conference on Evaluation and Assessment in Software Engineering, EASE 2015, pp. 11:1–11:10 (2015)Google Scholar
  10. 10.
    Mäder, P., Gotel, O.: Towards automated traceability maintenance. J. Syst. Softw. 85(10), 2205–2227 (2012)CrossRefGoogle Scholar

Copyright information

© Springer International Publishing AG, part of Springer Nature 2018

Authors and Affiliations

  • Muhammad Atif Javed
    • 1
    • 2
  • Faiz UL Muram
    • 1
    • 2
    Email author
  • Uwe Zdun
    • 2
  1. 1.School of Innovation, Design and EngineeringMälardalen UniversityVästeråsSweden
  2. 2.Faculty of Computer Science, Software Architecture Research GroupUniversity of ViennaViennaAustria

Personalised recommendations