Abstract
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.
Sign-in/Register to access full text options 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
