<?xml version="1.0" encoding="UTF-8"?>
<article article-type="Research Article">
  <front>
    <journal-meta>
      <journal-id journal-id-type="publisher">journal-of-information-and-optimization-sciences</journal-id>
      <journal-title-group>
        <journal-title>Journal of Information and Optimization Sciences</journal-title>
      </journal-title-group>
      <issn publication-format="electronic">2169-0103</issn>
      <issn publication-format="print">0252-2667</issn>
      <publisher>
        <publisher-name>Taru Publications</publisher-name>
      </publisher>
    </journal-meta>
    <article-meta>
      <article-id pub-id-type="doi">10.47974/JIOS-1497</article-id>
      <title-group>
        <article-title>A methodology for model clone detection using statistics of design metrics</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author" corresp="yes">
          <name>
            <surname>Shobha</surname>
            <given-names>G.</given-names>
          </name>
          <aff>Amity Institute of Information Technology, Amity University, Noida, Uttar Pradesh, India</aff>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Agarwal</surname>
            <given-names>Rekha</given-names>
          </name>
          <aff>Amity Institute of Information Technology, Amity University, Noida, Uttar Pradesh, India</aff>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Kansal</surname>
            <given-names>Vineet</given-names>
          </name>
          <aff>Institute of Engineering and Technology, Dr APJ Abdul Kalam Technical University, Lucknow, Uttar Pradesh, India</aff>
        </contrib>
        <contrib contrib-type="author">
          <name>
            <surname>Tanwar</surname>
            <given-names>Sarvesh</given-names>
          </name>
          <aff>Amity Institute of Information Technology, Amity University, Noida, Uttar Pradesh, India</aff>
        </contrib>
      </contrib-group>
      <volume>44</volume>
      <issue>6</issue>
      <fpage>1251</fpage>
      <lpage>1262</lpage>
      <pub-date date-type="pub">
        <day>11</day>
        <month>11</month>
        <year>2023</year>
      </pub-date>
      <abstract>
        <p>Model clone detection has predominantly gained momentum in the field of software development process and model driven engineering. Reuse and mutations of the existing models will increase the complexity of managing the software’s organisation’s internal repositories. Detecting semantic and structural similarities among the models finds various uses like fault prediction, estimation of maintenance and refactoring. Literature in the domain witnesses very few works focussing on model clone detection. This work proposes a model clone detection technique by leveraging the statistical and lexical properties of the UML diagrams. The primary contribution of the work is the construction of Similarity Measure (SM) by analysing the design metrics from different perspectives namelyi)measuring the statistical variability between the models and ii) estimating the lexical similarity among design metrics. The results of the model indicates that the proposed method was able to detect the semantically similar model clones of the banking use case. Also, the method is very robust and computationally inexpensive, so that it could find its applicability in all fields where model driven engineering is used.</p>
      </abstract>
      <kwd-group>
        <kwd>Model clones</kwd>
        <kwd>Model driven engineering</kwd>
        <kwd>Similarity measure</kwd>
        <kwd>Semantic clone</kwd>
        <kwd>SD metrics</kwd>
        <kwd>UML diagram</kwd>
        <kwd>Jaro-Winkler distance</kwd>
      </kwd-group>
      <custom-meta-group>
        <custom-meta>
          <meta-name>access</meta-name>
          <meta-value>open</meta-value>
        </custom-meta>
        <custom-meta>
          <meta-name>retracted</meta-name>
          <meta-value>no</meta-value>
        </custom-meta>
      </custom-meta-group>
    </article-meta>
  </front>
</article>
