{'fraction_non_alphanumeric': 0.023508137432188065, 'fraction_numerical': 0.0018083182640144665, 'mean_word_length': 5.511764705882353, '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}}
The non-homogeneous maintenance periods: a case study of software modifications

Software maintenance is often described as the most costly activity relating to software. Understanding software modification distribution could therefore greatly benefit information system (IS) managers. Current models mostly depict this distribution as homogeneous with a decreasing rate of modifications over time. The in-depth case study reported in this paper challenges this view. A detailed analysis of software modification by type, combined with interviews, shows that in the state-of-the-art IS that was examined, there were three distinct periods during the initial 29-month period studied. In the first period, the software was stabilized within the framework of its original specifications. Software modifications during this period centered on corrective modification, similar to software testing. In the second period, the software was improved: new functions were added within the original framework. In the third period, the IS was expanded beyond its original specifications by adding many new applications.