Strategy for Object Oriented Database Test using Software Fault Injection / Estrategia para testes de componentes de banco de dados orientados a objetos utlizando injeção de falhas

AUTOR(ES)
DATA DE PUBLICAÇÃO

2006

RESUMO

The majority of software currently developed - including critical systems - utilize third-party components. Further, a1most all systems use Database Management Systems that are acquired from firms that specialize in this sector. Given the security expected from these components, software fault injection is a useful and efficient validation too1. The process comprises the introduction of faults and observation of system replies when in presence of injected faults. To use this technique it is necessary to have a tool that allows for the injection of faults and the monitoring of the system under test in order to accompany its behavior. To achieve credibility these tests need a strategy that permits the choice of some necessary requirements for the injection. Among these requirements are what faults to inject, where to inject them, how to activate them, how to collect results and how to determine the component s success or failure when trying to solve the problem caused by the injections through the expected manner. For the experiments conducted, Ozone - an object-oriented database management system - was chosen as the third-party component. We have used Wisconsin 007, a benchmark developed for performance tests on these types of components, as the application to activate the injected faults. Jaca, that was developed previously at the Institute of Computing, was the chosen tool to make feasible the injection tests. 1t allowed for software fault injection. One contribution of this work is the proposed validation strategy for 00 components. The other contribution is the injection tool s tests, its corrections and improvements proposed

ASSUNTO(S)

tolerancia a falha (computação) banco de dados orientado a objetos engenharia de software - metodologia

ACESSO AO ARTIGO

Documentos Relacionados