Abstract
If the components in a component-based software system come from different sources, the characteristics of the components may be different. Therefore, evaluating the reliability of a component-based system with a fixed model for all components will not be reasonable. To solve this problem, this paper combines a single reliability growth model with an architecture-based reliability model, and proposes an optimal selecting approach. First, the most appropriate model of each component is selected according to the historical reliability data of the component, so that the evaluation deviation is the smallest. Then, system reliability is evaluated according to both the relationships among components and the using frequency of each component. As the approach takes into account the historical data and the using frequency of each component, the evaluation and prediction results are more accurate than those of using a single model.
Highlights
Component-based software reliability evaluation relates to the rationality of system design and the success of software systems
This paper proposes a component-based optimal selection model (OSM)
It is a class of component that its reliability-related data is of the type time between failure (TBF)
Summary
Component-based software reliability evaluation relates to the rationality of system design and the success of software systems. White box approaches [1,2,3,4,5] consider the system architecture These approaches disassemble the system into components, establish the relationship among the components, and evaluate the entire system reliability. Component-based white-box approaches consider the using frequency of each component, and no longer have the assumptions that system errors are proportional to the system failure rates. These approaches can be more accurate in the evaluation of system reliability. This approach bases on the system architecture, fully utilizes the historical data of each component, and takes into account the software reliability growth. OSM combines the reliability growth model of every single component with the architecture-based reliability model.
Sign-in/Register to view highlights & summary 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.
