1992
DOI: 10.1007/978-3-7091-9198-9_10
|View full text |Cite
|
Sign up to set email alerts
|

Assuring Design Diversity in N-Version Software: A Design Paradigm for N-Version Programming

Abstract: The N-Version Programming (NVP) appr~ach achieves fault-tolerant software units, called N-version Software (NVS) units, through the development and use of software diversity. To maximize the effectiveness of the NVP approach, the probability of similar errors that coincide at the NVS decision points should be reduced to the lowest possible value. Design diversity is potentially an effective method to get this result. It has been the major concern of this paper to formulate a set of rigorous guidelines, or a de… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
11
0

Year Published

1994
1994
2019
2019

Publication Types

Select...
4
3
3

Relationship

1
9

Authors

Journals

citations
Cited by 28 publications
(11 citation statements)
references
References 21 publications
0
11
0
Order By: Relevance
“…Design diversity has been applied to both software and hardware systems. -version programming [3], [13] is an example of diversity in software systems. In [12], a good historical overview of fault-tolerant design methodologies and architectures for safety-critical real-time applications is provided.…”
Section: A Past Workmentioning
confidence: 99%
“…Design diversity has been applied to both software and hardware systems. -version programming [3], [13] is an example of diversity in software systems. In [12], a good historical overview of fault-tolerant design methodologies and architectures for safety-critical real-time applications is provided.…”
Section: A Past Workmentioning
confidence: 99%
“…First, coincident failures are the result of unwanted commonalties between different instances, and various strategies are employed to minimize and eliminate these commonalities (see for e.g. [11], [12]). Falsepositives, however, result from the desired divergence between instances and we believe that, in general, the approach grows stronger as these differences increase.…”
Section: A General Frameworkmentioning
confidence: 99%
“…Both of the two kinds can be seen as diversity in different phases of a piece of software. For example, N-variant programming [3], which belongs to the managed diversity, produces functionequivalent versions of software in the software designing phase, while ASLR (Address Space Layout Randomization) [4], which belongs to the automated diversity [5], produces different executions for the same program in the software executing phase. The core of the software diversity for the security purpose is to make differences in the lifecycle of the software so as to increase the attacking difficulty.…”
Section: Introductionmentioning
confidence: 99%