Abstract
AbstractSoftware has become a household necessity in today's world but little has been done to measure its reliability for the consumer. Since software failure has a different basis than hardware failure, existing reliability theory cannot be applied directly: a new software unique theory needs to be defined. Current software practice relies on software quality measures to describe software reliability but recent work has identified both theory and practice for appropriate software reliability analysis. This paper discusses: the need for software reliability analysis in order to more accurately describe system reliability, the shortcomings of current practice, and both the direction of new work in, and the future roles for, software reliability analysis.
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.
