Assessing reliability of modular software
A Markovian model of a modular software system is presented. The software system has M modules, designed for execution of K tasks. Transitions between modules are assumed to follow a Markov process. Assuming known failure rates for modules, the probability of error free execution of a program, and overall failure rate are derived. With the objective of minimizing development/testing cost, a procedure is given for determining module failure rates that enable the system to a function at a prescribed failure tolerance. The procedure is illustrated through the use of an example exhibiting modular software with a single program. The ideas of potential use to project managers and software engineers during software development.
- Optimal software implementation considering reliability and cost.
- Resource allocation during tests for optimally reliable software
- Software development life cycle testing analysis: a reliability approach
- Reliability model of component-based software
- scientific article; zbMATH DE number 125780 (Why is no real title available?)
- scientific article; zbMATH DE number 1902093 (Why is no real title available?)
- A structure-based software reliability allocation using fuzzy analytic hierarchy process
- GENERALIZED RENEWAL PROCESS (GRP) FOR THE ANALYSIS OF SOFTWARE RELIABILITY GROWTH MODEL
- scientific article; zbMATH DE number 2219689 (Why is no real title available?)
- Architecture-based approaches to software reliability prediction
This page was built for publication: Assessing reliability of modular software
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q1124324)