UML models change impact analysis using a text similarity technique

Given the inevitable software evolution, change impact analysis (CIA) is a vital activity in the software development life cycle. Existing CIA methods either focus on one model produced during one development phase or ignore the semantic dependencies among the various models produced throughout the development phases. The herein proposed CIA method overcomes this limit by exploiting the structural and semantic dependencies within and inter-UML diagrams. It uses a graph technique to model the structural dependencies and an information retrieval (IR) technique to handle the semantic traceability between the use case documentation and the sequence diagrams. To identify the most appropriate IR technique to the CIA context, the authors present a quantitative experimentation of term frequency-inverse document frequency and latent semantic indexing (LSI), two widely used IR techniques. In addition, to evaluate the overall performance of their method, they present an evaluation performed on changes in the open source system JHotDraw 7.4.1 compared with its 7.5.1 version and changes performed on a real existing application. Using LSI, their method achieves an average precision of 84% and a recall of 91% in the requirements CIA and management.

[1]  Jaiprakash T. Lallchandani,et al.  Static Slicing of UML Architectural Models , 2009, J. Object Technol..

[2]  Yann-Gaël Guéhéneuc,et al.  MADMatch: Many-to-Many Approximate Diagram Matching for Design Comparison , 2013, IEEE Transactions on Software Engineering.

[3]  Yves Wautelet,et al.  Le "Unified Process" comme méthodologie de gestion de projet informatique. Eléments d'application en milieu sidérurgique , 2004 .

[4]  Rick Salay,et al.  Relationship-based change propagation: A case study , 2009, 2009 ICSE Workshop on Modeling in Software Engineering.

[5]  Ivan Porres,et al.  Difference and Union of Models , 2003, UML.

[6]  Nadia Bouassida,et al.  Managing the Impact of UML Design Changes on Their Consistency and Quality , 2016, Arabian Journal for Science and Engineering.

[7]  Genny Tortora,et al.  Recovering traceability links in software artifact management systems using information retrieval methods , 2007, TSEM.

[8]  Hareton K. N. Leung,et al.  A survey of code‐based change impact analysis techniques , 2013, Softw. Test. Verification Reliab..

[9]  Andrian Marcus,et al.  Recovering documentation-to-source-code traceability links using latent semantic indexing , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[10]  Ivan Kurtev,et al.  Change Impact Analysis based on Formalization of Trace Relations for Requirements , 2008 .

[11]  Bogdan Dit,et al.  Integrated impact analysis for managing software changes , 2012, 2012 34th International Conference on Software Engineering (ICSE).

[12]  Chris F. Kemerer,et al.  Towards a metrics suite for object oriented design , 2017, OOPSLA '91.

[13]  Václav Rajlich,et al.  Variable granularity for improving precision of impact analysis , 2009, 2009 IEEE 17th International Conference on Program Comprehension.

[14]  Lionel C. Briand,et al.  Automated impact analysis of UML models , 2006, J. Syst. Softw..

[15]  Jane Huffman Hayes,et al.  Advancing candidate link generation for requirements tracing: the study of methods , 2006, IEEE Transactions on Software Engineering.

[16]  Faiez Gargouri,et al.  UML MODEL VERIFICATION THROUGH DEPENDENCY RELATIONSHIPS , 2017, ICEIS 2017.