Fault Injection Approach Based on Dependence Analysis

Moraes, Regina; Martins, Eliane; Mendes, Naaliel

doi:10.1109/compsac.2005.78

Cited by 8 publications

(5 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Some of the existing approaches use an architectural model for performing dependency analysis and to guide fault injection [23,24]. Another approach, for the purpose of robustness testing, analyses the software architecture for identifying where each type of fault may occur, for the purpose of selecting the specific testing techniques to be used [22].…”

Section: Related Workmentioning

confidence: 99%

Architectural-Based Validation of Fault-Tolerant Software

Brito

Lemos

Martins

et al. 2009

2009 Fourth Latin-American Symposium on Dependable Computing

View full text Add to dashboard Cite

Many architecture-centred approaches have been proposed for constructing dependable component-based systems. However, few of them provide an integrated solution for their development that combines fault prevention, fault removal, and fault tolerance techniques. This paper proposes a rigorous development approach based on an architectural abstraction, which combines formal methods and robustness testing. The architectural abstraction assumes a crash failure semantics, and when it is instantiated as an architectural element provides the basis for architecting fault tolerant systems. The architecture is formally specified using the B-Method and CSP. Assurances that the software system is indeed dependable are obtained by combining formal specification for removing ambiguities from the architectural representation, and robustness testing for validating the source code against its software architecture. The feasibility of the proposed approach is illustrated in the context of a financial critical system.

show abstract

Section: Related Workmentioning

confidence: 99%

Architectural-Based Validation of Fault-Tolerant Software

Brito

Lemos

Martins

et al. 2009

2009 Fourth Latin-American Symposium on Dependable Computing

View full text Add to dashboard Cite

show abstract

“…In testability verification work on the equipment you want to check the UUT (unit under test) the BIT or ATE test and diagnostic capability using fault injection method [1]. As technology advances, the previously manual fault injection method can not meet the work requirements, fault injection automatically technique emerged, automatic fault injection equipment has been the focus of research in this field [2] [3].…”

Section: Introductionmentioning

confidence: 99%

The Application of Fault Injection Using Circuit Simulation in Testability Verification

Yuan

Shang

Heng

et al. 2013

AMM

View full text Add to dashboard Cite

The fault injection technology is an important aspect in testability verification, because the actual fault injection in equipment can damage itself, so using circuit simulation fault injection method to instead. Research on the simulation method that based on PSPICE, using VC++ software to design a simulated fault injection system, its structure and function to achieve workflow introduced. Finally, taking a circuit for example uses the system to fault injection and analysis to prove the availability and correctness of the system.

show abstract

“…Dependency analysis solutions can also be used to explain post-release failures (Nagappan and Ball 2007) and to deliberately insert faults into source code (Moraes et al 2005) to accelerate errors and failures situations. These activities are useful to observe the system's behavior in the presence of faults and therefore identify the source code elements that should be monitored for debugging during the implementation.…”

Section: Quality Assurance Testing and Debuggingmentioning

confidence: 99%

“…ModelBased Behavioral Dependency Analysis (MBBDA) (Garousi et al 2006) derive behavioral dependency information from UML design models. Chart diagrams are also used to identify chaining in class interfaces from class diagrams and support quality assurance and testing activities (Moraes et al 2005;Ryser and Glinz 2000). A final (Korel et al 2002;Jourdan et al 2006;Liangli et al 2006) set of solutions using diagrammatic representations apply formal concept analysis to cluster objects in business process models that can be considered dependent (Ivkovic and Kontogiannis 2006;Vasilache and Tanaka 2005).…”

Section: Diagrammatic Descriptionsmentioning

confidence: 99%

“…Dependency analysis solution work with various types of diagrammatic representations such as top-down descriptions (McComb et al 2002), component-based models (Vieira and Richardson 2002), matrix models (Khan et al 2008;Mao et al 2007;Xing and Stroulia 2006), chart diagrams (Garousi et al 2006;Moraes et al 2005;Ryser and Glinz 2000), and business process models (Ivkovic and Kontogiannis 2006;Vasilache and Tanaka 2005). Top-down descriptions are used to construct dependency models for application level analysis (McComb et al 2002).…”

Section: Diagrammatic Descriptionsmentioning

confidence: 99%

See 1 more Smart Citation

A practice-driven systematic review of dependency analysis solutions

2011

View full text Add to dashboard Cite

When following architecture-driven strategies to develop large softwareintensive systems, the analysis of the dependencies is not an easy task. In this paper, we report a systematic literature review on dependency analysis solutions. Dependency analysis concerns making dependencies due to interconnections between programs or system components explicit. The review is practice-driven because its research questions, execution, and reporting were influenced by the practice of a group of software architects at Philips Healthcare MRI. The review results in an overview and assessment of the state-of-the-art and applicability of dependency analysis. The overview provides insights about definitions related to dependency analysis, the sort of development activities that need dependency analysis, and the classification and description of a number of dependency analysis solutions. The contribution of this paper is for both practitioners and researchers. They can take it as a reference to learn about dependency analysis, match their own practice to the presented results, and to build similar overviews of other techniques and methods for other domains or types of systems.

show abstract

Fault Injection Approach Based on Dependence Analysis

Cited by 8 publications

References 10 publications

Architectural-Based Validation of Fault-Tolerant Software

Architectural-Based Validation of Fault-Tolerant Software

The Application of Fault Injection Using Circuit Simulation in Testability Verification

A practice-driven systematic review of dependency analysis solutions

Contact Info

Product

Resources

About