{'fraction_non_alphanumeric': 0.016175071360608945, 'fraction_numerical': 0.003805899143672693, 'mean_word_length': 4.9772727272727275, '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}}
Economic Impact of Software Patching and Optimal Release Scheduling

Because of highly distributed nature of software products, the task of improving software reliability is becoming a complex job. Specialized tools and techniques are being used to isolate the risky software modules. In order to retain in market, firms are required not only to provide the software on time but also to endow with continuous processing. Product updating is the process that comes to safeguard the firm's image at this point of time. And one such attribute of updating is providing software patches. Today, almost all software firms are providing either patching, module exchange or service pack application processes consequent to a release. This paper proposes a scheduling policy for a software product and shows the importance of patching in lowering the system outages and making the system more cost effective. Validation on the proposed policy has been done using real life software failure data set of Tandem Computers. Copyright © 2016 John Wiley & Sons, Ltd.