{'fraction_non_alphanumeric': 0.011180124223602485, 'fraction_numerical': 0.0, 'mean_word_length': 5.448, '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 Component Implementation Variations Study

Software components developed for reuse are the result of domain knowledge, design decisions and guesstimates about the future use of the component. The information available when developing components for reuse is interpreted by the individuals, which potentially leads to variations in design and implementation. Third year software engineering students have developed a set of components for reuse and used them to develop an application. In this paper we analyze the components code using metrics and qualitative analysis. We have observed that component implementations do vary, but the size of the variations are small. Also we found that designing a software component to work with unknown components often lead to overlapping design and implementation.