{'fraction_non_alphanumeric': 0.02032520325203252, 'fraction_numerical': 0.0, 'mean_word_length': 5.042944785276074, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Tracking Code Clone for Software Traceability and Quality

As one of the major problems in software maintenance, code clone, a pair of duplicated code in a source code, is well known. For software improvement, it is valuable to track code clone which has potential risk. This is because to determine how to treat code clones needs deep insight for the code clones. However, such code clone tracking is hard task especially for fresh developer. To support tracking code clones, we have proposed code clone history detection method. Code clone history reflects various manipulations to code clones including introduction, deletion, or just leaving unchanged. It also contains information about creator or modifier of code clones, and time of each manipulation. This means that tracking code clone history reveals many results of developer’s decisions about code clones. Thus, we assume various clues to improve software quality can be retrieved from tracking information of code clones.