Abstract
Almost all existing studies consider that product release results in the end of testing phase. However, the modern practices in software industry perceive a post release testing during which organization treats the remaining bugs present in the software to improve product experience for customer and at the same time trying to lower down the possibilities of software failure before testing ends. However, continuing testing after software release is not considered cost-effective for firms. Hence, it is essential to decide the optimal testing stop time under the budget. We comprehend this scenario to design a framework for optimal scheduling policy by considering cost and reliability as two attribute using multi-attribute utility theory. Validation of the obtained results is done on real-life software failure data set of tandem computers.
Published Version
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 call