Evaluating the recovery-oriented approach through the systematic development of real complex applications
Recovery-oriented software is built with the perspective that hardware or software failures and operation mistakes are facts to he coped with, as they are problems that cannot be fully solved while developing real complex applications. Consequently, any software will always have a non-zero chance or failure. Some of these failures may be caused by defects that may be removed or encapsulated. From the point of view of removing or encapsulating defects, a failure is considered to be trivial, when (i) the required effort to identify and eliminate or encapsulate the causing defect is small, (ii) the risk of making mistakes in these steps is also small and (iii) the consequences of the failure are tolerable. It is highly important to design systems in such a way that most (ideally all) of the failures are trivial. Such systems are called 'debuggable systems'. In this study, we present the results of systematic applying techniques that focus on creating debuggable software for real embedded applications. Copyright (c) 2008 John Wiley & Sons, Ltd.
software engineering recovery-oriented systems reliable software