Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

R. Keith Scott

dblp:22/5559 · DBLP profile ↗
← Back
2ranked-venue papers
2as first author
0since 2021 · last 1996
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 1 · 1 first-authorApplied, interdisciplinary, general and emerging computing · 1 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
1 paper
Software testing · 100%

Topics — the 1 heaviest of 2, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Software testing › software reliability
software reliability modeling
0.011987
Fault-Tolerant Software Reliability Modeling · IEEE Trans. Software Eng. 1987

Methods — techniques the papers use, named apart from their topics

recovery block · 0.0n-version programming · 0.0consensus recovery block · 0.0
YearPublicationVenuePosition
1996 Cost modeling of N-version fault-tolerant software systems for large N
abstract
A cost model determines system costs for fault-tolerant software systems. The model finds the optimal number of program versions to achieve minimum system cost of the fault-tolerant software techniques: N-version programming, recovery block, and consensus recovery block. In this case, all versions, the voter, and the acceptance test have the same reliability. When the parameters for the versions, acceptance test, and voter in the cost function are all equal, the cost of a 3-version system is always optimal, Cost(CRB)/spl Lt/Cost(RB)/spl Lt/Cost(NVP) for each target reliability differing by as much as two orders of magnitude in some cases. The cost functions were increasing functions of N. When the parameters are not equal, optimality occurred for other values of N. This was especially the case when the cost exponent for version-1 was larger than the exponents for the other versions and the acceptance test or voter. As the values of the cost exponents for the version reliabilities become larger, a smaller difference was required between the version-1 exponent and the others to produce alternate optima.
R. Keith Scott, David F. McAllister
IEEE Trans. Reliab.1
1987 Fault-Tolerant Software Reliability Modeling
abstract
In situations in which computers are used to manage life-critical situations, software errors that could arise due to inadequate or incomplete testing cannot be tolerated. This paper examines three methods of creating fault-tolerant software systems, Recovery Block, N-Version Programming, and Consensus Recovery Block, and it presents reliability models for each. The models are used to show that one method, the Consensus Recovery Block, is more reliable than the other two.
R. Keith Scott, James W. Gault, David F. McAllister
IEEE Trans. Software Eng.1