{'fraction_non_alphanumeric': 0.02845100105374078, 'fraction_numerical': 0.0, 'mean_word_length': 4.900621118012422, '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}}
A Semi-automated Process for Open Source Code Reuse

It is clear that Free Libre / Open Source Software (FLOSS) has been demonstrating increasing importance continually for some years now. As a result, millions of lines of code are becoming available online. In many cases, this code, is carefully designed, implemented, tested and therefore represents a very good option for reusability. Lately, more and more companies, especially Small and Medium Enterprises (SMEs), are reusing open source code to develop their own software. Source code forges such as SourceForge, Google Code etc., serve as component pools providing plenty of alternatives. In this work we are proposing a semi-automated reuse process model for discovering open source code online, based on the requirements of the system under design. This model illustrates the greedy approach of a reuse engineer, who wishes to reuse as much code as he can and implement the least possible.