Main Article Content
Abstract
Software code cloning is to write the code once and use it wherever required later on by making certain changes as per the requirement of the new/updated module/version. Such practices result in saving time, effort, resources and money, but the inconsistencies may bring in 'bugs or vulnerabilities' in the system which may further lead to decay (degradation) in software architecture. Performing the maintainability index calculations and compliance calculation provides information about the actual architecture decay during software code cloning. In this paper, two different software tools are used. ‘Analyze’ is used for calculating the Maintainability Index and ‘CppDepend’ is to find the Compliance value. To find the relationship between the Maintainability Index and Compliance calculations in software code cloning a case study of software 'DECEIVER' written in C++ is performed. Results obtained show that the inconsistent value of compliance, resulted in architecture decay of software.