Optimal COTS selection for fault tolerant software system with mandatory redundancy in critical modules using consensus recovery block scheme under fuzzy environment

2012 ◽  
Author(s):  
P. C. Jha ◽  
S. Bali
Keyword(s):  
Fault Tolerant ◽  
Software System ◽  
Fuzzy Environment ◽  
Block Scheme ◽  
Selection For ◽  
Recovery Block ◽  
Cots Selection

OPTIMAL COMPONENT SELECTION APPROACH FOR FAULT-TOLERANT SOFTWARE SYSTEM UNDER CRB INCORPORATING BUILD-OR-BUY DECISION

2013 ◽  
Vol 20 (06) ◽  
pp. 1350024 ◽  
Author(s):  
P. C. JHA ◽  
RAMANDEEP KAUR ◽  
SHIVANI BALI ◽  
SUSHILA MADAN
Keyword(s):  
Fault Tolerant ◽  
Quality Standards ◽  
Software System ◽  
Critical Systems ◽  
Component Selection ◽  
Proposed Model ◽  
Selection Approach ◽  
Block Scheme ◽  
Commercial Off The Shelf ◽  
Recovery Block

Application Package Software (APS) has emerged as a ready-to-use solution for the software industry. The software system comprises of a number of components which can be either purchased from the vendor in the form of COTS (Commercial Off-the-Shelf) or can be built in-house. Such a decision is known as Build-or-Buy decision. Under the situations wherein the software has the responsibility of supervising life-critical systems, the inception of errors in software due to inadequate or incomplete testing, is not acceptable. Such life-critical systems enforces upon meeting the quality standards of the software as unforbiddenable. This can be achieved by incorporating a fault-tolerant design that enables a system to continue its intended operation rather than failing completely when some part of the system fails. Moreover, while designing a fault-tolerant system, it must be apprehended that 100% fault tolerance can never be achieved and the closer we try to get to 100%, the more costly the system will be. The proposed model shall incorporate consensus recovery block scheme of fault tolerant techniques. Through this paper, we shall focus on build-or-buy decision for an APS in order to facilitate optimal component selection thereby, maximizing the reliability and minimizing the overall cost and source lines of code of the entire system. Further, since the proposed problem has incompleteness and unreliability of input information such as execution time and cost, hence, the environment in the proposed model is taken as fuzzy.

The Study on Software Fault Tolerance

2012 ◽  
Vol 268-270 ◽  
pp. 1790-1793
Author(s):  
Li Qing Li ◽  
Hai Lu ◽  
Xu Dong Li
Keyword(s):  
Fault Tolerance ◽  
Design Pattern ◽  
Fault Tolerant ◽  
Arithmetic Unit ◽  
The Core ◽  
Software Fault Tolerance ◽  
Block Scheme ◽  
Software Fault ◽  
Reliable Design ◽  
Recovery Block

Software Fault -tolerance is an effective and reliable design technique and Recovery Block Scheme is an important Software Fault-tolerant measure. Here is the brief introduction of the implementation of Software Fault-tolerant technique and the design pattern by employing software redundancy and then proposes the implementation of Recovery Block Scheme. Firstly, based on the program block’s fault captured by exception-progressing mechanism, it applies the Command Pattern and Active Objective Pattern to manage and schedule arithmetic unit to achieve rollback, clears the data generated by fault operation block and restores to the state before the operation. The design pattern provides a widely available recovery block schemes design pattern, simplifies the implementation of arithmetic unit and gives the core algorithm through Java.

OPTIMAL VERSION SEQUENCING IN FAULT-TOLERANT PROGRAMS

2005 ◽  
Vol 22 (01) ◽  
pp. 1-18 ◽  
Author(s):  
GREGORY LEVITIN
Keyword(s):  
System Reliability ◽  
Execution Time ◽  
Resource Constraints ◽  
Fault Tolerant ◽  
Optimization Procedure ◽  
Moment Generating Function ◽  
Software Systems ◽  
Block Scheme ◽  
The Moment ◽  
Recovery Block

This paper considers software systems consisting of fault-tolerant components. These components are built from functionally equivalent but independently developed versions characterized by different reliability and execution times. Because of resource constraints, the number of versions that can run simultaneously is limited. The expected system execution time and its reliability (defined as probability of obtaining the correct output within a specified time) strictly depends on the sequence of versions execution. Different sequences can provide either maximal system reliability or minimal expected execution time. An optimization procedure is suggested for finding such sequences. The procedure is based on an algorithm for determining system execution time distribution that uses the moment generating function approach and on the genetic algorithm. Both N-version programming and the recovery block scheme are considered within a universal model. An illustrated example is presented.

Sign in / Sign up

Export Citation Format

Share Document