Abstract
The ever growing consumer's expectations for innovative and reliable software products within no time have driven developers to reframe the whole development process accordingly. To sustain in the stiff market competition, nowadays software firms are releasing their product early and continue testing to fix the remaining number of bugs in the operational phase by providing patches. A patch is a small program to fix the bugs. But continuing testing to provide patches for better product experience to users is also not economical from the firm's point of view. In the existing software reliability literature, few researchers have worked on to determine the optimal release and testing stop time of a software, but no work has been done to determine the optimal time for releasing, patching and to stop testing the software. In this paper, we present a unified framework of optimal policy to determine optimal software release time, patching time and testing stop time, to minimise overall testing cost. The proposed cost model is validated on a real life software failure dataset of tandem computers.
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 callMore From: International Journal of Mathematics in Operational Research
Disclaimer: 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.
