A new working formula for the split-half reliability model.

The telecommunications industry has devoted much time over the years to concentrate on developing reliability models for electronic equipment.

It is also very convenient because it is so easy to add failure rates in a reliability model.

This metric, along with software execution time, is key to most software reliability models and estimates.

Provide necessary input to system-level reliability models.

The best reliability model to use is a Markov model (see Andrey Markov).

In each of these systems, the buffers are assumed to be of finite capacity and the machines are unreliable with the following reliability models:

A pioneer in transistor reliability modeling, Hu developed widely used CMOS device reliability models.

The methodology provides Software Engineers with practical tools for measuring and predicting the quality attributes of the software product and also enables them to include software in system reliability models.

Michael R. Lyu cites a DACS implementation of the Goel-Okumoto software reliability model, distributed by the DACS at the time.

System-level reliability models can subsequently be used to predict, for example, frequency of system outages in steady-state, frequency of system outages during early life, expected downtime per year, and system availability.

Among the topics addressed were: Jovian radiation models, the JEO system reliability model, radiation shielding modeling results, and the planned JEO and JGO architectures.

In order to calculate the PFS or PFD value of a safety loop it is necessary to have a reliability model and reliability data for each component in the safety loop.

His first published article, A new working formula for the split-half reliability model appeared in Educational and Psychological Measurement in 1965 and was published with Isaiah Guttman, a colleague from SRA.

Topics include: "software systems, prototyping issues, high-level specification techniques, procedural and functional programming techniques, data-flow concepts, multiprocessing, real-time, distributed, concurrent, and telecommunications systems, software metrics, reliability models for software, performance issues, and management concerns."