Abstract
This paper develops a plausible software availability model considering two types of failures during the operation phase. The first type is caused by the faults that could not be detected/corrected during the testing phase and the second type caused by those introduced by deviating from the specification during the operation phase. The former and the latter types of software failure-occurrence phenomena are described by a geometrically decreasing and a constant hazard rate, respectively. This model also describes the imperfect debugging environment in which a debugging activity does not always remove a fault perfectly. Taking notice of the cumulative number of faults corrected during the operation phase, we use a Markov process to describe the time-dependent behavior of the software system. Several quantitative measures of software system performance are derived from this model. Finally, numerical examples are presented for illustration of software availability measurement.
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 callMore From: International Journal of Reliability, Quality and Safety Engineering
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.
