1981
DOI: 10.1109/tse.1981.226474
|View full text |Cite
|
Sign up to set email alerts
|

Application of a Methodology for the Development and Validation of Reliable Process Control Software

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
5
0

Year Published

1984
1984
2019
2019

Publication Types

Select...
6
2
2

Relationship

0
10

Authors

Journals

citations
Cited by 66 publications
(5 citation statements)
references
References 4 publications
0
5
0
Order By: Relevance
“…Some key experimental hands-on studies that have researched NVS are, for example, Avizienis [15] and Chen [37], where they implemented NVS systems using 27 and 16 independently written versions; Ram [171] and Vog [201] have studied real-time software by developing six different implementations (programming languages) from the same requirements. Different from our study, "Diversity" in this context usually refers to the diversity of components (e.g., different compilers, programming languages, versions of the specifications [98], or different algorithms [37]).…”
Section: Software Diversitymentioning
confidence: 99%
“…Some key experimental hands-on studies that have researched NVS are, for example, Avizienis [15] and Chen [37], where they implemented NVS systems using 27 and 16 independently written versions; Ram [171] and Vog [201] have studied real-time software by developing six different implementations (programming languages) from the same requirements. Different from our study, "Diversity" in this context usually refers to the diversity of components (e.g., different compilers, programming languages, versions of the specifications [98], or different algorithms [37]).…”
Section: Software Diversitymentioning
confidence: 99%
“…9 working from different specifications [19]; 9 using different programmers [14]; and 9 using different types of programming language (procedural versus logic programming) [17].…”
Section: Reliability Through Redundancymentioning
confidence: 99%
“…The use of two or more distinct V-specs, derived from the same set of user requirements, can put extensive protection against specification errors. Two cases have been practically explored: a set of three V-specs (formal algebraic OBJ, semi-formal POL, and English) that were derived together [5,15], and a set of two V-specs that were derived by two independent efforts [20]. These approaches provide additional means for the verification of the V-specs, and offer diverse starting points for version implementors.…”
Section: Install Error Detection and Recovery Algorithms In Software mentioning
confidence: 99%