| "Code Clone" is widely used in the software development (especially in Large-scale Software System). The usage of "Code Clone" can improve the efficiency, sometimes also the quality of the software development. Especially during the maintenance stage, due to personnel changes, it is very difficult to find people to understand the whole system’s logic and code, plus other reasons such as long time of the history, neglected documentation, which make it even more difficult to change the code. The maintainer tends to misuse code clone. Because of increased functionalities, process adjustments, bug fix and so on, the maintenance stage takes more time and the misuse of code clone becomes more often. Such misuse of code clone causes the decreasing of software systems’quality (more bugs) and maintainability (more times of modules modification), therefore the usage of "Code Clone" generates a lots of side effects.In order to solve the subject concerning "how to use code clone to ensure software quality and maintainability", this essay summarizes the industrial research of the code clone, finds out the main reason of code clone’s generation, classifies code clone based on its location through relevant research, refer to some measure metrics for software’s quality and maintainability which have been widespread used in the industry; two new measure metrics (Maximum length of code clone and Coverage of code clone) for qualitative analysis of code clone’s effect on software quality and maintainability have been created. Furthermore, develop a tool to collect relevant dates. Based on above research, for a large software system a qualitative analysis about the code clone’s effect on quality and maintainability has been made and the relevant final conclusion(Using code clone must trade off in software quality and maintainability) has also been drawn. At the end a final summary explains how to use the relevant conclusions, and clarifies the shortage and future possible improvements. |
PDF Full Text Request