Software fault avoidance issues

Saha, Goutam Kumar

doi:10.1145/1195937.1195938

Cited by 17 publications

(3 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In order to prevent failures in the application, three techniques can be used at different levels of the fault-error-failure chain: fault avoidance, fault removal, fault tolerance. Fault avoidance and fault removal both refer to the fact that faults should be dealt with as soon as possible and not allow them to develop into errors, as errors are harder to handle and can easily lead to failures [12], [14].…”

Section: B Faults Errors and Failuresmentioning

confidence: 99%

Cloud simulation under fault constraints

Bosilca

Nita

Pop

et al. 2014

2014 IEEE 10th International Conference on Intelligent Computer Communication and Processing (ICCP)

View full text Add to dashboard Cite

As Cloud Computing offers support to more and more complex applications, the need to verify and validate computing models under fault constraints becomes more important, aiming to ensure applications performance. Doing this experimental validation in the early development phase and with small costs require a cloud simulation tool. An extensible framework for Cloud simulation and modeling is CloudSim. This paper proposes a new module for CloudSim consisting of a fault injector based on a specification language. The aim is to assist simulation to be more realistic and includes concrete conditions and constraints. The impact is on testing Cloud applications and help test fault tolerant applications by specifying defect patterns and failing components. The evaluation of the fault injection module is done by measuring the behavior and performance of a tool based on CloudSim, named CloudAnalyst. Several metrics are determined and measured for experimental validation, and conclusions are drawn.

show abstract

Section: B Faults Errors and Failuresmentioning

confidence: 99%

Cloud simulation under fault constraints

Bosilca

Nita

Pop

et al. 2014

2014 IEEE 10th International Conference on Intelligent Computer Communication and Processing (ICCP)

View full text Add to dashboard Cite

show abstract

“…Indeed, on one an hand, they represent the most effective tool to specify requirements in an unambiguous way [4]; that is, they improve fault prevention, which is ane the fault avoidance techniques [14]. On another hand, they provide means to verify and validate formally the specifications so that designers are able to detect and remove faults (i.e., apply fault removal techniques) in the early design phases and, contrary to test techniques, without having already realized a prototype of the system [19].…”

Section: Related Workmentioning

confidence: 99%

Formal design and implementation of constraints in software components

Coronato¹,

Pietro²

2010

Advances in Engineering Software

View full text Add to dashboard Cite

“…Whereas, the ESVP inherits its own generality, wide-applicability and simplicity. Both the ABFT [2,11,12,13] and CFC [3,12,13] are intended to detect errors only and, they are intended to complement the intrinsic hardware error detection mechanisms (e.g., microprocessor exceptions) in a microprocessor system. The so-called ESVP also inherits similar time and space redundancy as that of with the conventional fault tolerance schemes: RBS [4], ABFT and CFC.…”

Section: Introductionmentioning

confidence: 99%

Software Based Fault Tolerance Against Byzantine Failures

Saha¹

2006

CLEIej

View full text Add to dashboard Cite

The proposed software technique is a very low cost and an effective solution towards designing Byzantine fault tolerant computing application systems that are not so safety critical. It does not rely on multiple versions of software running simultaneously on multiple machines. The proposed software approach is to mask various hardware random errors on adopting the so-called, ESVP (an enhanced single -version program) scheme, while an application is being executed. It is not intended to eliminate software design bugs. In other words, it is assumed that code is correct and the faulty behavior is only due to transient or Byzantine faults affecting an application system. Implementation of this approach is also easy. A test program's present state is compared with its pre-computed state also in order to detect state transition - fault also. ESVP is intended to be suitable for a computer- based process monitoring system.

show abstract

Software fault avoidance issues

Abstract: This article aims to discuss various issues of software fault avoidance. Software fault avoidance aims to produce fault free software through various approaches having the common objective of reducing the number of latent defects in software programs.

Cited by 17 publications

References 14 publications

Cloud simulation under fault constraints

Cloud simulation under fault constraints

Formal design and implementation of constraints in software components

Software Based Fault Tolerance Against Byzantine Failures

Contact Info

Product

Resources

About