Título: | RECOVERY ORIENTED SOFTWARE | ||||||||||||||||||||||||||||||||||||||||||||
Autor: |
JOAO ALFREDO PINTO DE MAGALHAES |
||||||||||||||||||||||||||||||||||||||||||||
Colaborador(es): |
ARNDT VON STAA - Orientador |
||||||||||||||||||||||||||||||||||||||||||||
Catalogação: | 24/MAR/2010 | Língua(s): | ENGLISH - UNITED STATES |
||||||||||||||||||||||||||||||||||||||||||
Tipo: | TEXT | Subtipo: | THESIS | ||||||||||||||||||||||||||||||||||||||||||
Notas: |
[pt] Todos os dados constantes dos documentos são de inteira responsabilidade de seus autores. Os dados utilizados nas descrições dos documentos estão em conformidade com os sistemas da administração da PUC-Rio. [en] All data contained in the documents are the sole responsibility of the authors. The data used in the descriptions of the documents are in conformity with the systems of the administration of PUC-Rio. |
||||||||||||||||||||||||||||||||||||||||||||
Referência(s): |
[pt] https://www.maxwell.vrac.puc-rio.br/projetosEspeciais/ETDs/consultas/conteudo.php?strSecao=resultado&nrSeq=15420&idi=1 [en] https://www.maxwell.vrac.puc-rio.br/projetosEspeciais/ETDs/consultas/conteudo.php?strSecao=resultado&nrSeq=15420&idi=2 |
||||||||||||||||||||||||||||||||||||||||||||
DOI: | https://doi.org/10.17771/PUCRio.acad.15420 | ||||||||||||||||||||||||||||||||||||||||||||
Resumo: | |||||||||||||||||||||||||||||||||||||||||||||
Recovery oriented software is built with the perspective that hardware or
software failures as well as operation mistakes are facts to be coped with, since
they are problems that cannot be fully solved while developing real complex
applications. Consequently, any software will always have a non-zero chance of
failure. Some of these failures may be caused by defects that could be removed or
encapsulated. A key issue is to increase the detectability of errors, in other words,
increase the self-awareness of the software s behavior. In this work, we present the
results of systematically applying already well known techniques (design by
contract, self-checking software, software components, debuggable software,
design for testability, mock components and patterns) with the intent of creating
recovery oriented software. Measuring the development of five different real-time
and real world applications, we analyzed the effects of the adoption of these
techniques. In particular we observed the balancing of the effort spent in different
development stages and explore the reduncancy of reasoning concept that, as
well as providing a higher detectability and debuggability, also leads to enhancing
quality-by-construction. The results were encouraging since they were
systematically better than those reported in the literature and were achieved at a
feasible cost.
|
|||||||||||||||||||||||||||||||||||||||||||||
|